This is kind of long, but I needed to sound this out...
About a year ago with the help of our VAR we migrated from NT/SQL7 to Win2003/SQL2000.
We had one show stopping issue where they forgot about having to update the macsql.cfg. Corrected and since then the system has been running about as well as can be expected. That was until last Sunday when the server that Macola had been running on started having problems.
Here is the interesting part that I am hoping someone may be able to shade some light on.
When the old server starting having the problems, I brought it down to run diagnostics.
Soon after we started to notice Macola was acting up.
PWE and SQL Explorer would load normally but some screens (PO/OE/AP) would load slowly, some depending on the screen will take from 30 to 60+ seconds to come up.
Now, I had just this week added some Flex code into the OE and PO screens and was thinking it was a change that I made. But it did not make sense. So I went into account who's screens do not have any of my code on them and the had the same issue.
Then I tried disabling and then finally uninstalling our AV. No change. Scanned over the Registry, shared Macola folder and looked at all ini and cfg that I could think of. I did not see anything, with my limited experience as out of the ordinary.
Pull Macola off the system. Deleted Reg entries, Shared Macola folder and macola.ini. Reinstalled. Same problem.
Now back the old server. Since moving Macola I put a clean install of W2k Advanced Server that I am using for File/Print and IIS. The server name and IP address are the same though.
After the move I went to all the workstation removed Macola (Delete Reg, Macola folder and .ini) uninstalled SQL 7. Installed SQL 2000 connectivity, Macola, Flex, ER5 CRW etc.. updated the MDAC to 2.8. and this is what is still running on all the clients today.
Another thing, the problem is only with systems that where on the network before the move. New systems that have refresh installs WinXp, Win2K, since do not have this problem.
I have since brought the old server back online and all the issues with slow loading screens have gone away.
I am thinking there is a pointer somewhere that is causing this.
Any ideas???
Thanks
About a year ago with the help of our VAR we migrated from NT/SQL7 to Win2003/SQL2000.
We had one show stopping issue where they forgot about having to update the macsql.cfg. Corrected and since then the system has been running about as well as can be expected. That was until last Sunday when the server that Macola had been running on started having problems.
Here is the interesting part that I am hoping someone may be able to shade some light on.
When the old server starting having the problems, I brought it down to run diagnostics.
Soon after we started to notice Macola was acting up.
PWE and SQL Explorer would load normally but some screens (PO/OE/AP) would load slowly, some depending on the screen will take from 30 to 60+ seconds to come up.
Now, I had just this week added some Flex code into the OE and PO screens and was thinking it was a change that I made. But it did not make sense. So I went into account who's screens do not have any of my code on them and the had the same issue.
Then I tried disabling and then finally uninstalling our AV. No change. Scanned over the Registry, shared Macola folder and looked at all ini and cfg that I could think of. I did not see anything, with my limited experience as out of the ordinary.
Pull Macola off the system. Deleted Reg entries, Shared Macola folder and macola.ini. Reinstalled. Same problem.
Now back the old server. Since moving Macola I put a clean install of W2k Advanced Server that I am using for File/Print and IIS. The server name and IP address are the same though.
After the move I went to all the workstation removed Macola (Delete Reg, Macola folder and .ini) uninstalled SQL 7. Installed SQL 2000 connectivity, Macola, Flex, ER5 CRW etc.. updated the MDAC to 2.8. and this is what is still running on all the clients today.
Another thing, the problem is only with systems that where on the network before the move. New systems that have refresh installs WinXp, Win2K, since do not have this problem.
I have since brought the old server back online and all the issues with slow loading screens have gone away.
I am thinking there is a pointer somewhere that is causing this.
Any ideas???
Thanks