Hi,
I seem to be getting a lot of reports all of a sudden from members complaining the web app keeps erroring with the following message...
This error was reported @ 08:45 this morning, i've done some investigating and found in the SQL log that the SQL agent ran our backup then....
Now ok the backup was running however, as you can see this DB was created in 2004 and has run the backup at the same time every two hours ever since, it's not been a problem before.
Can the SQL agent backup cause connectivity issues?
Also I did a search and found this MS thread... which looks exactly like it could be the problem, except one thing.
It specifically states while using 'Windows Authentication' yet my perl script connect via Username/Password authentication, so am reluctant to make any registry changes, as this part of the KB article doesn't match the way I connect to the SQL server.
What do you guys think? is it worth a go, but why would things work fine for years and now start to become an issue.
The one thing that has changed in those years is the number of members using the extranet and so SQL traffic has increased.
Could it simply be a situation of our resources running out for the amount of traffic / connections it is trying to make?
All advice appreciated.
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
Google Rank Extractor -> Perl beta with FusionCharts
I seem to be getting a lot of reports all of a sudden from members complaining the web app keeps erroring with the following message...
which is the perl script bombing when trying to access the SQL DB.Software error:
getSQL Error Connecting: [11] [] "[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation."
This error was reported @ 08:45 this morning, i've done some investigating and found in the SQL log that the SQL agent ran our backup then....
2010-03-17 08:45:35.46 Database backed up: Database: xxxxxxx, creation date(time): 2004/09/30(09:36:25), pages dumped: 22649, first LSN: 2905:122:1, last LSN: 2905:124:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'D:\SQL Backup\xxxxx.BAK'}).
Now ok the backup was running however, as you can see this DB was created in 2004 and has run the backup at the same time every two hours ever since, it's not been a problem before.
Can the SQL agent backup cause connectivity issues?
Also I did a search and found this MS thread... which looks exactly like it could be the problem, except one thing.
It specifically states while using 'Windows Authentication' yet my perl script connect via Username/Password authentication, so am reluctant to make any registry changes, as this part of the KB article doesn't match the way I connect to the SQL server.
What do you guys think? is it worth a go, but why would things work fine for years and now start to become an issue.
The one thing that has changed in those years is the number of members using the extranet and so SQL traffic has increased.
Could it simply be a situation of our resources running out for the amount of traffic / connections it is trying to make?
All advice appreciated.
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
Google Rank Extractor -> Perl beta with FusionCharts