| Author |
 Topic  |
|
|
Lon2
Junior Member
USA
151 Posts |
 Posted - 08 January 2009 : 10:06:43
|
We've been tweaking and tuning-up our site. Upon going through our IIS 6.0 log files, we noticed many errors relating to our Snitz forum, version 3.4.03 upgraded to 3.4.06. The errors look like this:
2009-01-08 03:49:39 W3SVC904 XX.XX.XXX.XXX GET /forum/active.asp |114|80004005|[DBNETLIB][ConnectionOpen_(Connect()).]SQL_Server_does_not_exist_or_access_denied. 80 - XX.XXX.XXX.XXX
There are about a 100 errors per day. They are via any file: topic.asp, pop_profile.asp, default.asp, forum.asp, topic.asp, etc. And all by different IP addresses.
I searched online and ran acrossed Microsoft doc: http://support.microsoft.com/kb/888228
Before I go trying new connection strings, what is the latest-and-greatest connection string for SQL 2005 Express server?
Besides the connection string, could there be anything else causing all the errors on a daily basis?< |
|
|
HuwR
Forum Admin
United Kingdom
20584 Posts |
Posted - 08 January 2009 : 10:28:26
|
quote:
Before I go trying new connection strings, what is the latest-and-greatest connection string for SQL 2005 Express server?
a good start would be to maybe tell us what connection string you are currently using 
quote:
Besides the connection string, could there be anything else causing all the errors on a daily basis?
most probably caused by network/server timeout problems< |
 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 08 January 2009 : 10:30:23
|
| You should contact your host about it. Probably you have a too busy a server, or there are other issues, maybe network related. In any case, you need to contact the host. I also doubt that the connection string has any role on that.< |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
Lon2
Junior Member
USA
151 Posts |
Posted - 08 January 2009 : 10:56:48
|
Thanks for the quick replies! Our current connection string is:
strConnString = "Provider=SQLOLEDB;Data Source=xxxx.server.com,1750;database=clientid_dbname;uid=client_uidname;pwd=password;"
Does this look right?< |
|
|
|
AnonJr
Moderator
United States
5768 Posts |
Posted - 08 January 2009 : 11:01:15
|
I'm not the SQL Server expert, but I don't see where that would be an issue. I've also seen that the reccomended connection string for SQL Server 2005 is:
Provider=SQLNCLI;server=servernameoraddress;database=databasename;uid=client_uidname;pwd=yourpassword;
Its what I'm using on SQL Server 2005 Express Edition for an internal site. I doubt that's the issue, but it couldn't hurt.< |
|
|
|
Lon2
Junior Member
USA
151 Posts |
Posted - 08 January 2009 : 12:56:38
|
Thanks, AnonJr. I found this: http://www.connectionstrings.com/sql-server-2005 but I guess I need to know Native Client and Version, Standard or Trusted Connection, and ODBC or OLEDB.
Another question I have now is: Does Snitz' Admin Server Information (admin_info.asp) report server info based on the actual server or does my connection change some things, like "Provider Friendly Name: Microsoft OLE DB Provider for SQL Server"?< |
|
|
|
HuwR
Forum Admin
United Kingdom
20584 Posts |
Posted - 08 January 2009 : 13:18:32
|
quote:
Does Snitz' Admin Server Information (admin_info.asp) report server info based on the actual server or does my connection change some things, like "Provider Friendly Name: Microsoft OLE DB Provider for SQL Server"?
yes, your connection string would change what was reported.
your connection string is unlikely to be the cause of the server not found errors.< |
|
|
|
Podge
Support Moderator
Ireland
3775 Posts |
|
|
Lon2
Junior Member
USA
151 Posts |
Posted - 19 January 2009 : 16:48:31
|
quote:
Originally posted by AnonJr
I'm not the SQL Server expert, but I don't see where that would be an issue. I've also seen that the reccomended connection string for SQL Server 2005 is:
Provider=SQLNCLI;server=servernameoraddress;database=databasename;uid=client_uidname;pwd=yourpassword;
Its what I'm using on SQL Server 2005 Express Edition for an internal site. I doubt that's the issue, but it couldn't hurt.
AnonJr, have you ever checked your log files to see if your forums produce connection errors? And are your forums pretty active?< |
|
|
|
AnonJr
Moderator
United States
5768 Posts |
Posted - 19 January 2009 : 20:05:12
|
| That particular one is not very active, and there are no connection errors in the log. Its also an in-house server, and I have my own VPS all to my self.< |
|
|
|
Lon2
Junior Member
USA
151 Posts |
Posted - 20 January 2009 : 15:59:52
|
| Thanks. That's exactly what I wanted to do before I heard ISPs were cracking down on people running web sites on home computers/servers using up ISP bandwidth. Are you getting away with it now? I used to check dslreports.com on that but haven't in a while. You would not believe all the problems we'ave had in the past 10 years with shared hosting and uneducated hosting companies!< |
|
|
|
AnonJr
Moderator
United States
5768 Posts |
Posted - 20 January 2009 : 22:35:30
|
| By in-house I mean for the company, behind the firewall and not accessable to the public.< |
|
|
|
Lon2
Junior Member
USA
151 Posts |
Posted - 22 January 2009 : 16:43:23
|
quote:
Originally posted by AnonJr
I'm not the SQL Server expert, but I don't see where that would be an issue. I've also seen that the reccomended connection string for SQL Server 2005 is:
Provider=SQLNCLI;server=servernameoraddress;database=databasename;uid=client_uidname;pwd=yourpassword;
Its what I'm using on SQL Server 2005 Express Edition for an internal site. I doubt that's the issue, but it couldn't hurt.
I changed our connection string to your recommendation and we went from over 100 errors a day to just 1 or 2. I'd say it's workin good now. Thanks for your help, AnonJr!  < |
|
|
| |
Topic |
|
Topic Locked
