UPS Worldship Error On Start as Restricted User

[PulsaMatt]

I'm hoping someone else might have run into this problem before.

I have a total of 5 machines running UPS Worldship 6.0.21 in the factory. 3 of these machines were recently upgraded from slow 400MHz Celerons running Win2k to newer Dell 1.8 GHz machines running Win2k (needed more horsepower for some apps).

These three machines worked perfectly with the users being "restricted users" under win2k. However, in WinXP the program throws an error on load when the user is a "restricted user".

The error is ... error code 1026 - Base Server Services Failed. This comes up when the software is "initializing web services" on the machine.

I gave restricted users read/write to the entire UPS folder, that didnt help. All services that have UPS in the name appear to be on automatic start-up and are started before starting worldship.

I have a call in to UPS but they are less than helpful as usual.

I really need to get these computers back to "Restricted user" because I have big problems with people in the factory screwing around with their computers (installing spyware, etc) ... took me a long time to reign them back in when I took over IT here.

Any help would be greatly appreciated.



Matt Laski
Netadmin, Pulsafeeder Inc.

 

[PulsaMatt]

I should add, that even after the error, the software loads and works but functionality is impaired in that it will not communicate with UPS via the net ... so End of Day won't run right, etc.

In the meantime I have made the users "power users" which solves the problem and allows them to ship error free.

Matt Laski
Netadmin, Pulsafeeder Inc.

 

[bcastner]

Import and apply the Win2k workstation compatability security template:

Compatible (Compatws.inf)
Default permissions for workstations and servers are primarily granted to three local groups: Administrators, Power Users, and Users. Administrators have the most privileges, while Users have the least. Thus, you can significantly improve the security, reliability, and total cost of system ownership by:

Ensuring that end-users are members of the Users group.
Deploying applications that run successfully under a User context.
Applications that comply with the Windows 2000 Application Specification can run successfully under a User context. However, applications that are not certified for Windows 2000 are not likely to run under a User context. Thus, if non-certified applications must be supported, there are two primary options:

Allow users of such applications to be members of the Power Users group.
Relax the default permissions granted to the Users group.
Because Power Users have inherent capabilities such as creating users, groups, printers and shares, some administrators would rather relax the default User permissions than allow users of non-certified applications to be members of the Power Users group. This is precisely what the Compatible template is for. It loosens the default file and registry permissions granted to the Users group in a manner that is consistent with the requirements of most non-certified applications. Also, because it is assumed that the administrator applying the Compatible template does not want users of non-certified applications to be Power Users, the Compatible template also removes all members of the Power Users group.

http://www.microsoft.com/resources/...Windows/XP/all/reskit/en-us/prdd_sec_umgs.asp

 

[smah]

Are all of these running a standalone Worldship stations? If running as networked terminals, only the Administration machine should be trying to phone home during End of Day.

Anyway, all my remote users & Admin station are all running 98, so I haven't run into this. If you're running a networked installation, make sure the remote users have read/write permissions on the shared folder of the Admin machine. But my suspicion is a permission setting in the registry. Worldship makes a lot of entries in the windows registry - maybe you have a permissions problem there.

FWIW, I've had pretty good luck with their Tech support by e-mail.

http://www.ups.com/content/us/en/resources/service/hardware/worldship11.html

 

[bcastner]

Much easier to Start, Administrative Tools, Local Security Policy, Action, Import Security Template, and choose compatws.inf

Done.

If the application ran under Win2k this should make it run under XP if the issue is user rights and permissions.