Server does not exist or access denied Error

[vamshika]

hi,
I got a serious Problem. I get "Server does not exist or access denied" with 80004005 as the error code. the win2003 server uses all the latest components(like iis6,jet..etc) and is upto date. The Asp website and its database(sql server) are in two different servers.
Can any one help me out. Did enybodyelse come accross such issue??????

I referred the msdn and tried the solutions(like setting permissions..etc) already but none of them works...

the reason for the error is the website is unable to find its database in a remote server. The follwing is displayed in the error page

__________________________________________________ __________
Microsoft OLE DB Provider for ODBC Drivers error '80004005'

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

Any Help????!!???

[merlinds33]

hi,
I got a serious Problem. I get "Server does not exist or access denied" with 80004005 as the error code. the win2003 server uses all the latest components(like iis6,jet..etc) and is upto date. The Asp website and its database(sql server) are in two different servers.
Can any one help me out. Did enybodyelse come accross such issue??????

I referred the msdn and tried the solutions(like setting permissions..etc) already but none of them works...

the reason for the error is the website is unable to find its database in a remote server. The follwing is displayed in the error page

__________________________________________________ __________
Microsoft OLE DB Provider for ODBC Drivers error '80004005'

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

Any Help????!!???

We are running MS SQL 2005 on Windows Server 2003 and experienced a similar issue.

Our connection string was set to port 1045 which worked for all our sites until we installed an MS update and rebooted. We investigated MS SQL Manager and noticed that after the reboot it changed the connection sting default to port 1051 for all our databases. We suspect this was a MS automatic security update. We've now resolved the issue by changing it back to port 1045 in MS SQL Manager.