Access 2010 performance on VM

Topic

New Reply

I have a client who needed more space for Access 2010 data. The most cost-effective way to provide that was to P2V the machine to a SAN attached virtual machine. Now he experiences slow performance and resource errors. I kind of expected the slow performance but not the errors. Does anyone have any Access 2010 tuning hints that might help resolve the resource errors?

Reply | Quote

Replies

What resource errors?
Is there enough RAM assigned to the VM?
Have you checked the event log in the VM?

Joe

--Joe

Reply | Quote

The error comes from Visual Basic. “Error 3035. System resource exceeded.” There’s nothing in the event logs.

Reply | Quote

Also, how much data is being returned?

Joe

--Joe

Reply | Quote

Joe, The physical machine had 3 GB RAM and so does the VM. Yes, SP1 is installed. I don’t understand what you mean when you ask how much data is being returned.
Wendell, good call. The client’s vendor who wrote the database also suggested that. The client changed that setting within the Access menu without success.

Reply | Quote

The error comes from Visual Basic. “Error 3035. System resource exceeded.” There’s nothing in the event logs.

It’s a good chance that the error comes from the Registry setting for MaxLocksPerFile. See the support article http://support.microsoft.com/?id=286153.

Reply | Quote

What resource errors?
Is there enough RAM assigned to the VM?
Have you checked the event log in the VM?

Joe

--Joe

Reply | Quote

Is SP1 installed for Access?

Joe

--Joe

Reply | Quote

Don’t you have a way to find out where precisely is the error occurring? That would probably give a good idea of what is causing it.

Reply | Quote

Unfortunately, the only error the client sees is a pop-up from Visual Basic saying “Error 3035. System resource exceeded.”
I think my only way to get more precise is to ask his vendor to insert some diagnostic stop-points into the code.

Reply | Quote

This is screwy. When we first saw this error, we Googled it and didn’t find any hotfixes. Now, a Google search shows Microsoft KB2726928 near the top.
That hotfix seems to have helped. Thanks to all who chimed in.

Reply | Quote

Glad you have a resolution. Thanks for posting back.

Joe

--Joe

Reply | Quote

Thanks for posting the solution – we run some pretty complex Access front-ends and have never seen the problem, but someone else is sure to hit it sooner or later and this may help them find the solution.

Reply | Quote