problem with mssql3 ?

i am getting an error like this:

Microsoft OLE DB Provider for ODBC Drivers error ‘80004005’

[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

it happens randomly on every page.
is anyone else getting this error?


iolite portable vaporizer

hi,

please create a ticket of that, Also send links where you are getting sql errors.

Thanx

i searched the forum and read about dsn less connection at:

http://support.jodohost.com/showthread.php?postid=431#poststop

i will try it. if the error shows again i ll try the ticket

thanks…

Hi ~

I get the same error on sql server 64.156.222.125

And I make a ticket :48216

Please help us !!

Ted :frowning:

we hav’nt received ticket 48216, create it from your Control Panel, do not send a mail directly.

Thanx

Hi ~ yogesh

I nerver send a mail directly.

I post the message just after making a ticket :48216

Please check it …

The below is the auto response email from jodohost..

Ted


======== CUT HERE =========
This is a receipt that your ticket was successfully received:

Created: Jan 25, 2005 9:03:14 AM
Last Mod: Jan 25, 2005 9:03:14 AM

[Jan 25, 2005 9:03:14 AM]
Q: i am getting an error ,too and the error like this :

Microsoft OLE DB Provider for ODBC Drivers error ‘80004005’

[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

it happens randomly on every page.

Thanks for you ~

hi

create another ticket, also mention ur domain name

thanx

Hi ~yogesh

I make another ticket 48225~~

Please check it ~

Thanks for you ~

hi,

yes, we got your ticket, we will reply your ticket soon.

Thanx

We will be doing a RAM upgrade on MSSQL3 shortly to solve this issue

It seems memory related. It previously appeared network related but we have ruled that out.

Hi ~ Yash & yogesh

Thank you very much ~

You are the best !!

Well I certanly hope this works, Ive been reporting this problem for 2 Months…

Microsoft OLE DB Provider for SQL Server error ‘80004005’
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
/forum/includes/pm_check_inc.asp, line 67

And again…

Microsoft OLE DB Provider for SQL Server error ‘80004005’

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

/forum/includes/pm_check_inc.asp, line 67

or sometimes…

Microsoft OLE DB Provider for SQL Server error ‘80004005’

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

/forum/default.asp, line 347

Or worse, goes completely…

The page cannot be displayed
There is a problem with the page you are trying to reach and it cannot be displayed.


Please try the following:

Open the www.mercilesscreations.net home page, and then look for links to the information you want.
Click the Refresh button, or try again later.

Click Search to look for information on the Internet.
You can also see a list of related sites. “”

:frowning:

Hope this works..

MM

MSSQL2 was having the same isssue, until the RAM was upgraded to 2gb again.

MSSQL3 will be getting that upgrade soon, I was just informed the the datacenter staff that it will be within the next 1-2 hours.

[QUOTE=Stephen]
MSSQL2 was having the same isssue, until the RAM was upgraded to 2gb again.

MSSQL3 will be getting that upgrade soon, I was just informed the the datacenter staff that it will be within the next 1-2 hours.
[/QUOTE]

:slight_smile: Thanks…

MM

It has been upgraded, please inform us of any problems

[QUOTE=Yash]
It has been upgraded, please inform us of any problems
[/QUOTE]

Still happening…

@ 12:19 GMT

Microsoft OLE DB Provider for SQL Server error ‘80004005’
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

/forum/default.asp, line 415

MM

@ 12:22 GMT..

Microsoft OLE DB Provider for SQL Server error ‘80004005’

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

/forum/common.asp, line 260

MM

We are continuing with our investigation …

How long will MSSQL3 be down for?

it is not down, its up

The error is occuring randomly. We have indentified certain parameters when the error is occuring and we are resetting MSSQL (takes 5 seconds) before that error starts occuring till be solve this issue.