Jump to content

Fred Marker

Member Since 29 Jan 2001
Offline Last Active Aug 20 2012 02:15 PM

Topics I've Started

ProIV serialization on virtual server (VMware)

09 October 2007 - 03:42 PM

Has anyone been successful in installing a licensed and serialized ProIV 5.5 kernel on a virtual Windows 2003 server using VMware?

Were there any problems or issues with the ProIV serialization?

Can the virtual server with the serialized ProIV kernel be saved and then started later as a new instance as a backup and recovery approach for the original installation (assuming the ProISAM or SQL database is stored on a SAN or another server)?



ProISAM error

19 March 2007 - 02:56 PM

Last week, our Windows 2003 Server's application event log registered 121,487 errors (event 52) logged consecutively for a single 10 minute period from the ProISAM service with the text entry of "Error hit maximum page number." No other logs or signs that there were any problems/issues in the ProIV application.

Has anyone else seen this event log error before or know what this is regarding?


Client build vs Kernel release

15 December 2005 - 12:47 PM

Is there any negative impact of using an older 5. 5 client build (e.g. 513, 523, 524) to access a 5.5 kernel release 518 instead of build 5.6.# or later?


ProIV 5.5 r518

23 November 2005 - 02:54 PM

During installation of the ProIV kernel 5.5 r 518 on a Windows 2003 Server where ProIV kernel r345-USRAN-004 was already installed, I received the following error messages:

Error copying to windows directory: forpro32evt.dll
Error copying to windows directory: forpisamevt.dll

The installation completed and the applications appear to run correctly.

Is there any significance or consequences of these error messages?

Is this caused by the fact that the pisamevt.dll and pro32evt.dll from the previous kernel already reside in the c:\windows\system32 folder?


Windows 2003 Server SP1

16 November 2005 - 01:19 PM

After installing Windows 2003 Server SP1 on our ProIV server (kernel 5.5 r345), we are getting a "Pro32Srv error 6: SetServiceStatus" in the event log every time ProIV service is stopped. Has anyone else seen this?