I have Attain 3.10A NAS and I am running SQL Server option, with a database that still has a codebase of 2.60F in 3.10A Executables. I recently installed and started testing NAS. I added Trigger 99 to my Codeunit 1 and it starts and runs fine. I originally installed it on the same server where my SQL Server database runs. After I run it for awhile, and try to stop it, the service hangs for awhile then I get a message in the NAS SnapIN that says “the pipe has ended” I try stopping the service directly from control panel on the machine, and I get “Service did not respond to stop request in a timely manner…” The Application Event log shows Internal Error 1 in Module 5 or sometimes mmc.exe throws a Dr. Watson error. I tried moving the NAS instance off the database server onto another machine with no luck. Incidentally, at this point Trigger 99 is doing NOTHING other than returning a message to the Event Log Please help
Hi Devin, Are using the NFTimer.dll component? If so try using the CPtimer.dll instead that one is more stable. I think there is some kind of memory leak in NFTimer.dll, especially if you are using the 3.10 one, preferably use the 3.70 CPTimer.dll component. I have experienced similar problems with 3.10 NAS and NFTimer.dll, switching to CPTimer.dll was better but eventually we upgraded to 3.70 and now it is working fine. Regards, Bruno
Actually, I am using the CPTimer.dll version 3.10. Is it possible to replace that one with the 3.70 CPTimer?
unregister the old dll, copy the new dll, register the new dll