3 replies to this topic

[Fred Marker]

Below is the text of an error message we are getting in the Windows 2000 Server Event Log on our ProIV server when our ProIV application hangs so badly that new .piv sessions display in the ProIV Service Manager with only an Id, Thread and Client Machine IP address but no Function, SF or Status! The threads can not be killed from ProIV Service Manager and transparent logins of proiv.exe on the server (such as data imports [see more info below] ) can not be killed by NT Task Manager!

This seems to be happening about every other day, especially late in the afternoon (4:00 - 6:00 pm) as users are doing actions that interface 2 separate ProIV applications more heavily than in the morning.

We are running ProIV Kernel Version 4.6000, Revision 2.1.4 (Aug 8, 00) on Windows 2000 Server 5.00.2195 SP 3 on a Dell PowerEdge 2650 with multiple Intel Xeon 2.0 Ghz processors and 2 Gb RAM.

===================================
Event Type: Error
Event Source: ProIsam
Event Category: None
Event ID: 33
Date: 7/14/2003
Time: 5:34:18 PM
User: N/A
Computer: ProIV_Server
Description:
The description for Event ID ( 33 ) in Source ( ProIsam ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 8.
===================================

FYI: We have a scheduling package called Opalis Robot running on the same server as ProIV that executes transparent logins to the ProIV application (doing data imports) every minute from 6:00 am until midnight daily.

Any ideas or suggestions????

Thanks.
Fred

[Ralph Gadsby]

Fred, you ought to have a pisamevt.dll in your WINNT\SYSTEM32 directory. From the fact that the event description is missing it would appear that you do not have this DLL (or the file is in the wrong location).

[Fred Marker]

Ralph, the pisamevt.dll does exist in c:\winnt\system32!

[Ralph Gadsby]

It would seem that there was a problem that the pisamevt.dll failed to register successfully in previous releases under certain circumstances. This problem was fixed in 5.5r200.

Fred, if you would like to log this fault with PROIV support we will investigate the cause of your problem.