Database Keeps Crashing

[gemma-the-husky]

We have two servers - both have A2007 and A2003, but are running in A2003

A database works perfectly off-server (development environment)

A database was reported as suddenly generating a "repair database crash" on certain forms.

I rebuilt the database carefully from the latest version, on separate developement machine.

It now works off-server (in the development environment)

when uploaded, it again works correctly on server 1 (no crashes)

but on server 2, a handful of forms (browse or design mode) crash access instantly in A2003, but work properly in A2007.

Any thoughts?

Is it likely to be an installation/updates issue with A2003 on server 2

 

[boblarson]

What Operating System software is your server running on?

 

[gemma-the-husky]

it's a Terminal server running XP Professional SP 3.

 

[boblarson]

it's a Terminal server running XP Professional SP 3.

Windows XP does not run Terminal Services. It would be Windows Server 2003 or 2008. If 2008, then it is possible that the SP1 problem with ADO keys is causing the crashes. If on Windows Server 2003 then I'm not sure what it could be.

 

[gemma-the-husky]

iI am pretty sure it is XP Service Pack 3
it's using a product called winconnect server

http://download.cnet.com/WinConnect-Server-XP/3000-2064_4-10392957.html

as I said the issue is that Access is crashing on one server, and not on the other.

 

[boblarson]

Given that it is not a Microsoft Product, I can't help. It is highly likely it has to do with something WinConnect Server, so it might be something to try to ask them
http://www.thinsoftinc.com/support.aspx#winconxp

But the main thing is trying to find out what is different about each one of the installations. That can be a big pain.

 

[gemma-the-husky]

bob, thanks for the thoughts.

 

[Galaxiom]

XP does indeed run Terminal Services but only allows one session. Remote Desktop is none other than the terminal services client. Terminal Services service just needs to be enabled in the Windows setup.

It means it when it says one session though and won't allow you to connect while there is a local session. (BTW I tried it once while I had a local session locked. The remote login failed and the local login went completely nuts and had to be rebooted.)

Firstly I would check if the database works locally on the server.

If that works then maybe try connecting with Remote Desktop. I imagine both terminal services and WinConnect would share some resources so if TS raised the problem it would probably clear the resonsibility from WinConnect.