Pervasive

Normal 0 false false false EN-US X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;}

I downloaded and installed the Pervasive patch (10.31.044) on the server and clients today.  The patch installed successfully on both the server and all clients.  However, the control panel on the Server is not showing that the most recent patch was applied.  The client workstations are showing the correct update version of 10.31.044.  The server is still showing version 10.31.026.  I’ve tried installing the patch 4 times now and receive no error and the software shows a successful install.  I have also rebooted the server and tried installing the patch after rebooting.  On one of the installs I decided to follow the Pervasive instructions on creating a log file for the install.  The logs seems to show that the patch was successfully installed, however the control panel is not showing the updated Pervasive engine version of 10.31.044.  Is this a bug in the patch?  I’m concerned that the server isn’t on the updated patch.

The PCC Help/About reports the version of the PCC, not of the engine or client.  Here is the "right" way to check the version of your components:

    http://www.goldstarsoftware.com/papers/DeterminingYourPervasiveEngineVersion.pdf

This confirms that I am running 10.31.037.  Any idea how / why the Pervasive database is not update to 10.31.044 after applying the patch?

I just realized that the components build version is 10.31.037 for the hot fix.  Does that confirm that the install for 10.31.044 was successfully?

Yes, this confirms it. I've asked Pervasive to report on the component build, but they seem to like using the installer build number instead. Go figure.

To determine if the Windows Installer patch package (.MSP) for a particular PSQL Update (v10 or v11) has been applied to the system successfully:

On versions of Windows beginning with Windows Vista/2008 Server, refer to the Version field from "Programs and Features" in Control Panel (this field may not be enabled by default on some versions of Windows).

For Windows XP/2003 Server or earlier, open "Add or Remove Programs" in Control Panel, select the PSQL installation and click the "Click here for support information" link to view the Version field.

 

InstallGuy,

As BtrieveBill mentioned.  The proper way the check the version is included on his post.  The method you suggested is not displaying the correct version for the Pervasive Server.  Your suggested method is only working on the Pervasive clients.  To verify the patch installed properly on the Pervasive server, you must confirm by using the method BtrieveBill posted.

 

No, the proper way to check the version of PSQL installed, beginning with PSQL v10.0 and later, is from the WINDOWS control panel (Programs and Features or Add/Remove Programs). I am not referring to the Pervasive PSQL Control Center (pcc.exe), as BtrieveBill [correctly] pointed out, the "Help-->About" dialog in PCC only shows the version of the individual PCC component (pcc.exe file version).

If you've successfully installed the patch on the server and the version information displayed from the WINDOWS control panel does not show "10.31.044" then that is a bug. However, that information is verified by Pervasive before the patch is published so it should be correctly displaying "10.31.044" for v10 SP3 Update 20.

The method described in the document referenced by BtrieveBill will allow you to see the specific component version for the mentioned PSQL engine files (the file version of the installed components or "10.31.37.0" in the case of ntmkde.dll for v10 SP3 Update 20). However, Pervasive does not currently publish the individual file versions as they are different from the actual PSQL product version and they are different depending on which component/file is being checked (engine files, Pervasive services files, third-party components, etc.). The only version information published on the Pervasive website is the PSQL product version, which should be correctly updated in the WINDOWS control panel after each patch is successfully applied to the system.

If you have successfully applied the v10 SP3 Update 20 patch to your server installation and you do not see "10.31.044" listed as the product version in the WINDOWS control panel (Programs and Features or Add/Remove Programs) then that would indicate a valid issue with the latest v10 SP3 Update.  In which case, please respond with more information regarding you specific PSQL configuration (including what OS version the server and clients are installed on and whether or not v10 SP3 was the first version of PSQL installed or if it was upgraded from an earlier version of PSQL) and I will open a change request with Pervasive support to have the issue fixed.

Thank you!

Thank you for clarifying InstallGuy.  This is in fact a bug in 10.31.044 patch after what you detailed in your post.  The 10.31.044 patch did install successfully as detailed in my original post.  The version information of the ntmkde.dll displays the correct component version of the 10.31.044 patch (component version 10.31.37.0).  The version information in add/remove programs is not properly indicating the correct patch version of 10.31.044.  The version information in add/remove programs never changed from 10.31.026 after successfully applying the 10.31.044 patch.

We have the Pervasive PSQL v10 SP3 Server Engine 32-bit installed on a Windows Server 2008 R2 Enterprise 64-bit operating system.  I also have a install log when I installed the 10.31.044 patch if needed.

 

I was not able to reproduce this issue on my end using the steps outlined below.  Is it possible you had an earlier version of PSQL installed on your 2K8r2 64-bit system prior to installing PSQL v10 SP3 (10.30.024) or perhaps you also installed then removed the 64-bit client from the same system while the 32-bit Server Engine was installed?  Please let me know if your install scenario was different than what is indicated below.

1. 64-bit Windows Server 2008 R2 Enterprise (6.1.7601) w/ no previous version of PSQL installed (no PSQL displayed in Windows Programs and Features).
2. Installed Pervasive PSQL v10 SP3 Server Engine (32-bit) using FCS/GA install package. Windows Programs and Features displays version "10.30.024".
3. Applied PSQL v10 SP3 Update 10. After refreshing the Windows Programs and Features view, version "10.31.026"  is now displayed.
4. Applied PSQL v10 SP3 Update 20. After refreshing the Windows Programs and Features view, version "10.31.044" is now displayed.

 

I am not 100% sure on the original install procedure because we had our ERP consultants setup this up for us.  As far as I am aware here is the install procedure:

1. Installed Pervasive PSQL v10 SP3 Server Engine 32-bit install package from CD (consultants)

2. Installed Pervasive PSQL patch update 10.  Refresh programs and features view, version 10.31.026 now displayed.

3. Installed Pervasive PSQL patch update 20.  Refresh programs and features view, version 10.31.026 still displayed.  Properties of the ntmkde.dll file version displays 10.31.044 patch component of 10.31.37.

It could be possible that the consultants installed the PSQL Server 64-bit version, uninstalled and re-installed PSQL Server 32-bit but I can't confirm that.