Sage 100

MAS 90 EES 1.2 - client asks me to setup FAS about a year after installing EES. Receiving ""unable to connect to system database"". Unfortunately what Sage recommends doesn't work. The server is a Windows 2008 R2 64 Bit which I can't rule out as the cause. I hate to go the full upgrade on this version mainly because everything is working and I don't want to turn a $1,000 job into $7,500 and still have the problem only to find out it was something simple. Anyone wrestle with anything similar?: I had a client back in January with almost an exact same situation though it wasn't EES. Unfortunately I don't think the fix was the same exact steps as what was in the KB -- and I don't have those notes with me.

Looking over my notes I find that I had to insert an IP address into the Sage Fixed Assets Service Manager -- I tried that a few times here and it didn't seem to work in this case. I can get FAS to run on the server -- it just doesn't come up on any workstations

The server name on this site is ""//prefix.servername.org/path/morepath/MASFAS I've noticed Sage warns against using different characters in the path -- and am wondering if the period (.) that the client has in the server name is causing an issue? Any experiences here?

Their server name that FAS is trying to connect to is \\nbems-data.nbems.org\mas90v4\EES Server\MAS90\MASFASVR\DATA\FAData.bdb

I'm wondering if the hyphen and period in the server name are causing an issue since the KB article seems to say that lengthy paths and/or those with ""special characters"" may produce this message.

try \\ipaddress\mas90v4\EES Server\MAS90\MASFASVR\DATA\FAData.bdb and that might rule out the special characters

Thanks Johnny I just tried that and still the same old error. I am able to run this on the server (Win 2008 R2 64 Bit) but no workstations. I ping the server IP fine I've had a similar issue with another client and I had to stick the IP address into the config for FAS and it worked just fine. This time when I use the IP I just keep getting the same information. I'd start to think firewall or port issue though I can ping the general IP without an issue. Maybe it's a closed port?

Any idea what port # has to be opened? I think I see 1433 in the tech info.

Resolved: The issue here appears to be that the Windows 2008 R2 64 Bit server had the firewall enabled. IT staff tried to open port 1433. Further reply: I followed the .exe used by the Fixed Asset service (dbsvr10.exe) on the server and allowed that through the firewall. Can you see if that works? Once that was allowed through the firewall the EES workstation was able to connect.

Love the tech boys...... At least they helped get it fixed...........

And fast too. Unfortunately this was also a case where EES was setup 1.5 years ago. The customer took it for the cost savings. Never setup FAS and/or CRM. In the interim they moved servers so they did the ""drag and drop"" to move MAS. However I think that breaks the FAS service --- so I had to completely re-load EES to get the FAS back. Live and learn...