JChemWebServicesInstaller-5_3_3.msi install

On Install on window 2008 Server 64x, the error as shown in the attached file is displayed only

when attempting to setup the service to run as a user on install.

 

Error : "There is a problem with this Windows Installer package. A Program run as part of the setup did not finish

as expected. Contact your support personnell or package vendor"

 

Is there a known solutino to address this problem ?

 

Hi,

please send me the related record from the Event Viewer.

Thanks, Edvard

Hi Edvard,

 

Find below, copy of data from event Viewer and associated screenshot.

Regards

kevin

 

Log Name:      Application
Source:        MsiInstaller
Date:          6/3/2010 2:56:33 PM
Event ID:      11722
Task Category: None
Level:         Error
Keywords:      Classic
User:          KINVPC1001\Administrator
Computer:      KinVPC1001
Description:
Product: JChem Web Services -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action viewer.exe, location: C:\Windows\Installer\MSID47F.tmp, command: "C:\Program Files (x86)\ChemAxon\JChem Web Services\bin\serviceInstall.bat"
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MsiInstaller" />
    <EventID Qualifiers="0">11722</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-06-03T13:56:33.000Z" />
    <EventRecordID>164</EventRecordID>
    <Channel>Application</Channel>
    <Computer>KinVPC1001</Computer>
    <Security UserID="S-1-5-21-2418878970-2438456123-931693952-500" />
  </System>
  <EventData>
    <Data>Product: JChem Web Services -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action viewer.exe, location: C:\Windows\Installer\MSID47F.tmp, command: "C:\Program Files (x86)\ChemAxon\JChem Web Services\bin\serviceInstall.bat" </Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Binary>7B45303442364635382D363634342D344245342D423331332D4441394432424131423333457D</Binary>
  </EventData>
</Event>

Hi,

thank you for the detailed report.
Please check if an installed JChemWebServices service is existing in your machine. Maybe that caused the problem.
If that is exsist, please try to remove it firstly with <JChem Web webservices>/bin/serviceUninstall.bat. You can perform it with the zip package of JChemWebServices.

Regards, Edvard

This was a brand new clean machine, so there was no software on the machine.

 

Can you sucessfully install the webservice on a 64bit machine??

 

Have you any other ideas of how to get this working?

 

Karl

 

I just performed it again on another brand new clean machine windows 2008 64 bit server and it actually worked.

Are there any prerequisites for JChemWebServicesInstaller-5_3_3.msi?

Karl

Hi Karl,

Based on the event viewer report, the Windows Service installation was not successful.
It seems to be a permission problem.  The user who runs the service must be registred in the local security  policies, 'Log on as service' policy.
Or maybe you missed the service user's password in the service dialog.

For the whole conditions please see the admin and installation guides:
https://www.chemaxon.com/webservices/adminGuide.html />https://www.chemaxon.com/webservices/installation_guide_W.html

Regards, Edvard

Thanks for the quick response. I was the administrator on the machine, and I'm nearly 100% I types the correct password.

 

I'm getting the QA'a guys doing an install tomorrow on another clean system. I will let you know the outcome tomorrow,

 

Kind Regards

Karl

 

 I was the administrator on the machine

Unfortunately it is not enough for running Windows services. Just the 'Administrator' built-in user is assigned to the 'Log on as a service' policy.

Also we use ntrights.exe for add permissions to the user. It might has been another reason if that application could not run.

Regards, Edvard