momuser1100

Hi everyone,
I spoke with someone that told me I need to update the momwin.exe file to the latest build that is from October 2008. We no longer have a service agreement with MOM. Is there someone out there that may be able to get me the latest mom 5.4 update download? So I can test the theory? Thanks......

Hi everyone,

It looks like I may have found what the problem is, we have 3 network switches in our network and one of them was bad and was not working properly. We only found this out by chance because we had a wireless router setup on it and it was not allowing internet access. So we switched it to another router and determined that the network switch was not working right. It would still let us get internet for the desktops and we could transfer files etc, so it appeared to be working right but when we replaced with another one all the networking started to run smoother and when we tried MOM again it seems to be working and has been working for several hours. In the past it would only last a few minutes before bombing. I am leaving this post incase someone else ever has this error. Thanks....

Hi everyone,
I spoke with someone that told me I need to update the momwin.exe file to the latest build that is from October 2008. We no longer have a service agreement with MOM. Is there someone out there that may be able to get me the latest mom 5.4 update download? So I can test the theory? Thanks......

its definitely a networking problem or you have referenced in mom someplace the E drive anything with the ~ sym is a temps system file

Hi

Thanks for responding. Since I posted last I did move imom to an XP machine and had the same problems with the networked in windows pro 2000 machines. We never had this problem before with all the same equipment I do not know what changed. I did however find out that the ~ is used for temporary windows files but only when it is the first charactor of the file name. With this error it is actually short hand for a long file name stored in old MSDOS format. In other words, this was the way MSDOS programs named files when the file name was longer then the eight dot three format. Apparently, mom has old programing that is using the old file naming convention. Please read

http://ask-leo.com/w..._hard_disk.html for a history of the convention.

What the error really is saying is e:\document and settings\albert~1.000\local settings\temp\main.fxp The user is Albert which most of been one of the programers for mom since we have never had an Albert working here. The main.fxp is actually a foxpro temporary data file that it creates inorder to function.

I have not found any reference in mom about the E drive. I am thinking it may have something to do with windows 2000 updates and maybe an update screwed up the way files are done on the network or mom or something that is the only thing that changed. I will try a few things and get back to the forum. Thanks again for responding...