Sage Accounts using VMWare datastore problem

Hi all

I currently run a DL380 G5 with VMWare ESXi 4 (the free version). This has 2 VServers, one of which hosts my shared network drives. Physically this is 4 SAS drives in RAID 10. The servers are well under utilised - only 1 person accessing them most of the time.

Pretty standard procedure and works well, except:

I have Sage Accounts 2010 installed on a client with the Sage data being on its own shared drive. Problem I have is 95% of the time, I open Sage, and it'll hang for ages on the Splash screen.

If I browse to the shared drive, the logon prompt for Sage then appears immediately. If I browse to this drive immediately before opening Sage, it works as expected most of the time.

Scattered occurances of:

- Having to re-browse to the drive for a second time after inputting credentials
- Having to re-browse to the drive after updating any information (Sage will hang with a progress bar saying "Waiting for xxx.dta"
- NOT having to browse at all, just works as expected (very rare, typically if I close sage and re-open immediately)

Once I'm in, it works fine.

Have done AV exclusions, although I cant see why that would cause it to do this. Accessing other shared drives/files all work wonderfully.

Client is Windows 7 Pro x64. Only other PC with Sage installed is an XP VM, which I believe does not have this issue. No other problems that I can think of on the network etc.

Any ideas?
Who is Participating?

Improve company productivity with a Business Account.Sign Up

hongeditConnect With a Mentor Author Commented:
Moved Sage to physical machine in the end.
Bruce DenneySage 50 Consultant and IntegratorCommented:
I would switch to using a UNC path in Sage as it sounds like it is the client is having problems maintaining a Mapped drive letter.

What operating system(s) are you using ?

hongeditAuthor Commented:
Let me try that out.

Windows Servers are 2008 Ent x64
Client is W7Pro x64
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

hongeditAuthor Commented:
Well, that didnt work.

Hung on first go after changing company file!
Bruce DenneySage 50 Consultant and IntegratorCommented:
I doubt this is anything to do with VM-ware. Unless the Datastore access is very slow and or corrupted.  If the store not a local physical disk then this might warrant more of a look?

I would try a fresh install, using something a little less bleeding edge Windows 2003 or, as all you need for Sage is a reliable file share, Linux

hongeditAuthor Commented:
The reason I think it is VMWare is becuase my old server was a low spec ML110, far inferior to what I have now, and didnt have this problem?!
Bruce DenneySage 50 Consultant and IntegratorCommented:
Was it running Windows 2008?
hongeditAuthor Commented:
Yes - SBS 2008
hongeditAuthor Commented:
See last comment
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.