Problem installing OnePacs WS on a XP Pro SP2

[hilario]

We are having troubles installing OnePacs WS on an XP Pro SP2.
- I have disabled Antivirus on the OnePACS directory
- I have disable Firewall
But the problem remain. Two behaviours:
- The poller refuse to start
- The WS start but give an error windows. As soon as I close this windows, the system close the WS windows.

I include:
- c:\onepacs\workstation\logs
- The error windows

[tom]

Was this the first installation of OPW on this computer? Any prior installs?

[hilario]

It is not the first installation.
Before was another version (I can't tell you exactly what version)
But I have uninstalled it before installing the last one
It is very probable that the First installation of the new one was not before Un-installing the previous one.

Thanks

[tom]

The installer should offer you an option for a "clean install", deleting all data associated with prior installs. Did you get offered this option? If not, download the latest version of the installer which will offer this.

This will probably fix this issue. It sounds like something is held over from a previous install that was not updated properly.

This assumes of course that you don't mind deleting the data from the prior install. If there's any reason you need to keep that data we can look into this more deeply, but I think if you run a clean install it will work fine.

[hilario]

I have run the "clean uninstall" option, and reinstalled the WS.
Now the poller is working fine
But the OnePacs Workstation SCP Service on Localhost doesn't start.
Error 1067

What do you need to continue dibugging?
Regards

[jeremy]

Error 1067 is displayed when a windows service cannot start. Please check that there is no other application that is running on the the default port (44104) of the workstation. TCPView - http://technet.microsoft.com/en-us/sysi ... s/bb897437 may be helpful to identify what programs are running on particular ports. Please follow the instructions contained by the link http://wiki.onepacsforums.com/doku.php? ... debug_logs to get logs if further debugging is necessary. Those logs may be sent to support@onepacs.com.

Regards,
Jeremy

[hilario]

after loading TCPview, no service use port 44104 (where do I configure the port on the WS?)
I include here the logs file.

By the way, I tried to use messaging system from the faulty WS and when I open the composition window it open too hight then I can't see the upper part of the windows (near till subjet field)
Then I can't find the admin user to send you the files via messaging.

Regards
Hilario

[jeremy]

A ticket has been created for further investigation.

The logs indicate that the service fails to start because "No se pudieron convertir algunas o todas las referencias de identidad." The following Microsoft article seems to indicate that this error can occur because
"On some non-English operating systems, the installer cannot locate the Network Service account because the account name is localized." The workstation seems to have trouble starting the service for similar reasons.

The following link gives a possible resolution.
http://support.microsoft.com/kb/941209

1. Create a new local user group with name "Network Service"
See "Create a new local group" on
http://www.microsoft.com/resources/docu ... x?mfr=true

2. Add the localized network service account to the recently created "Network Service" group. Here's a mapping:

* German - NT-AUTORITÄT\NETZWERKDIENST
* French - AUTORITE NT\SERVICE RÉSEAU
* Italian - NT AUTHORITY\SERVIZIO DI RETE
* Spanish - NT AUTHORITY\SERVICIO DE RED
See "Add a user to a group" link from "Create a new local group" section of the link above.

A clean reinstall may be necessary after attempting the above.

Regards,
Jeremy

[tom]

Hilario,

Regarding the messaging system window being too large, it sounds like the monitor resolution is too low. For OP we recommend at least 1024 x 800 for the window displaying the worklist.

We'll have someone else look at this issue.

Tom

[tom]

An easier workaround would be to try creating a new account and installing it in the new account as windows in spanish doesnt seem able to handle this user named 'user' on the spanish language system.

Can you make a new user with a username of something other than "user" and install into the new account? That may work.