Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ColinD
Starting Member
40 Posts |
 Posted - 2007-06-04 : 06:25:45
|
| Hi all,I have a MS Access application which uses SQL Server 2000 as a backend. Everything has been working fine for weeks, but today my MD has a problem running one particular report. This report works fine for every other user on the system.The problem is as follows. He selects the button which runs the report and after a longish wait (10 minutes), gets the following error:Connection failedSQL State '01000'SQL Server error 53[microsoft][ODBC SQL Server Driver][DBNETLIB]Connection OpenConnection failedSQL State '08001SQL Error 17[microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access deniedFinally, a login box appears asking him to login to SQL server.I realise that this looks like a network error, but there are no other network problems on his p/c until he clicks on this particular report. All other reports work fine for him. However, once he has clicked on the report, his whole p/c more or less locks up and needs to be rebooted.I am completely confident that it is not a network error which is causing this, in fact it is running the report which causes the network error.Am I wrong? Can you suggest any other possibilites?ThanksColin |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2007-06-04 : 08:42:51
|
| Sounds like it might be running out of resources on his machine.I wouldn't be surprised if access had to render the report in memaory so might be running out of that.His whole PC locking up sounds a bit like that.Could be that the report is corrupt, not enough space for the page file to expand, database needs compacting, ...==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
SQL Server error 53