Our company purchased a new computer with Microsoft Office Pro 2007. We've been running a Microsoft Access 2003 ADP for years with no problems. Since Access 2007 has been accessing our Windows Server 2003, our server crashes. This has happened twice. The first time was about 4 days after Access 2007 was being utilized. The second time was 3 days after the master node was reset. The server is a Virtual Server hosted by VPSLand. The Access ADPs are accessing data in SQL Server 2000. Authentication mode is SQL Server only. We're not using Windows Authentication.
The signs leading up to the crash occur in the following order...
1. Everyone can log in just fine.
2. All users are dropped from the server and can't log back in except the Access 2007 user.
3. I can't access the server thru RDC or any other tools, but can still ping the server. As RDC begins to log me into the server, I see the desktop, but the icons never show up.
4. The Access 2007 user is dropped from the server and can't log back in.
5. At this point, the I can still ping the server, but can't access it in any other way.
6. Finally, I can't even ping the server.
The only way VPSLand can fix the situation is by rebooting the "Master Node". This is the second time this has happened, and I feel like Access 2007 is the culprit due to the timing.
There have been some errors in the event log. Error 1355 I believe.
Is Access 2007 causing the issue? What is causing this issue? We're reverting back to Access 2003, but I need to know if the issue is related to Access 2007.
I'm an advanced developer in SQL and Access, but only intermediate on issues like login management, or memory management.
Start Free Trial
