Hi,
Well moving over from Win32::ODBC to DBI/DBD::ODBC has made no difference...people are still getting this sparodic error...
Hunting the web for ODBC general network error throws up threads going back years all complaining about this useless error message.
Some have said it is related to CommanTimeout, well i've upped that from 900 to 1200, some say you have to disable pooling with pooling=false. So i've added that atribute to the DSN. Though the ODBC Data Source Administrator on the server shows all drivers having pooling disabled. Am I looking in the wrong place?
I've also found this KB which implies it's SQL killing the connection because it thinks it's a DOS attack.
So I've updated the registry and will reboot the server tonight.
Does any one have any further suggestions on the possible cause and potential solution.
Our members are starting to get peed off that the systems keep failing out of office hours and there is no one here to support or investigate the problem.
I really need to find a solution to this, so your help is appreciated.
Is this likely to be nothing to do with perl and DBI connectivity but more likely to be the MS SQL server end?
"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
Well moving over from Win32::ODBC to DBI/DBD::ODBC has made no difference...people are still getting this sparodic error...
DBI connect('FILEDSN=my_file_.dsn;Regional=No;','myDB',...) failed: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation. (SQL-08001) [err was 1 now 1] [state was 08001 now 01000]
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (PreLoginHandshake()). (SQL-01000) [err was 1 now 1] [state was 01000 now 01S00]
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribute (SQL-01S00) at
Hunting the web for ODBC general network error throws up threads going back years all complaining about this useless error message.
Some have said it is related to CommanTimeout, well i've upped that from 900 to 1200, some say you have to disable pooling with pooling=false. So i've added that atribute to the DSN. Though the ODBC Data Source Administrator on the server shows all drivers having pooling disabled. Am I looking in the wrong place?
I've also found this KB which implies it's SQL killing the connection because it thinks it's a DOS attack.
So I've updated the registry and will reboot the server tonight.
Does any one have any further suggestions on the possible cause and potential solution.
Our members are starting to get peed off that the systems keep failing out of office hours and there is no one here to support or investigate the problem.
I really need to find a solution to this, so your help is appreciated.
Is this likely to be nothing to do with perl and DBI connectivity but more likely to be the MS SQL server end?
"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