General Discussion Topics

[Kurtismonger]

We are receiving the following error:

 OBJMGR

Error reading the record: TaskID- 17631534, TaskName- , Error- Caught Exception: "(name not supplied)" - OLE Dispatch Error: m_scError:266744(0x000411f8), Desc:General network error. Check your network documentation.

ConnectionWrite (WrapperWrite())., Help:0, Help File-:: System Definition:

We are on 7.20.7. All users are receiving this error at various points.

 

[Kurtismonger]

Anyone? A hint? A starting point?

[Ralph]

I'm sure you know this already, but the TaskID refers to the Change Business Date task.  Don't know if that helps though, since the error seems to refer to a network issue.

Maybe a little more info about your environment would allow someone to offer more help.  For example, is the MAS client running on a Terminal Server?  If so, Citrix?  What o/s?  Are users all local, or are some across a WAN link from the SQL server?  Etc, etc.

[Kurtismonger]

MAS500 is running on a dedicated MS 2003 server with only 2 users currently. Running version 7.20.7. This problem just cropped up in the past month and there have been no changes to the network.

I was first going to update to a more recent service pack. But when I ran update 7.20.8 on the server, it appeared to install without a problem, but the database version remained at 7.20.7. So I removed 7.20.8 and reinstalled 7.20.7 on both of the clients that were having problems. Haven't seen any problems, but this issue is intermittant and one of the users only uses the system at month end.

[jnoll]

It sounds like their client is not getting close properly on their workstations, then they timeout. The error occurs when they go to reconnect and it believes they were still connected. This is due to have the default check of Startup selected when you install the MAS 500 client.

A couple of ideas to try.

1) Uninstall the client. Delete the MAS 500 folder. Then reinstall the MAS 500 client. Make sure you do not check the Startup check box. This is set th not checked in version 7.3. FINALLY!

2) See if the Sage Icon is still in system tray before they start MAS 500. If it is right click on the Sage Icon and Shut Down MAS 500. Then launch MAS 500 and see if they do not get that error.

3) Locate and Right-click on the Sage MAS 500 Desktop icon. Click on the Properties option. Add the '/S' to the en of the Target line. It will look like 'C:\WINDOWS\system32\BusinessDesktopLoader.exe /S'. Click okay to save. This will keep MAS 500 from launching MAS 500 and keeping the Business Desktop loaded after you close MAS 500.

Just some options to try. Keep us posted.

[Kurtismonger]

Joe - Both users do have MAS500 Desktop run at startup and then it stays in the system tray. Are you saying that the desktop client is timing out because they are not doing anything in the software? For example, If they run it in the morning and then leave the client open, but switch to email or Excel, and then switch back to MAS500 in the afternnon?Or it's not so much whether they actually have the client running it's the fact that the client is run at startup and sitting in the system tray and it's connection to the server is being dropped?

I should mentioned that the errors sometimes occur when they start the client and sometimes after they have been working in the client and try to do something in a particular module.

I will try your suggestions if I see these symptoms continue.

[jnoll]

Yes that is what I was saying. I have seen it at a few clients. Really tough to reproduce.

One thing you may want to check are the Power Settings on the computer. MAS 500 is not happy if the disk drive goes to sleep after inactivity, same with the NIC.