Link to home
Start Free TrialLog in
Avatar of BenBispham1
BenBispham1

asked on

Unable to install PS4.5 - Installation ended prematurely, error 10001

I have a problem installing Citrix PS4.5. All machines are up to date with Windows and have rollup pack 2. Here's what's happening:

Recently the Citrix datastore was moved from SQL 2000 to another server running SQL 2005.
The move was done by copying the database over to the new server and running dsmaint.
The move appears to have been successful for all the existing servers  everything is working.

I came to add a new server to the farm and the installation of PS ends with Installation ended prematurely because of an error Then Error 10001. Ive looked in the KB for the error but none of the solutions/causes fit. I went back to the last test server I built (before the move) and removed PS and tried to reinstall with the same result. Is this likely to have something to do with the SQL move? Any suggestions? The ODBC connection tested OK. I have the install log, but cant see anything obvious in there. Not sure where to go from here& Thanks.
Avatar of Daniel Borger
Daniel Borger
Flag of United States of America image

Is there more to the error? Can you get through the install by creating a new Access farm and then join it to the SQl farm?
Is there a chance the installation media is corrupt?
Avatar of BenBispham1
BenBispham1

ASKER

Thanks for the thoughts. There isnt any more to the error, but I do have the MSI log if that would help. Saw this in the event log, dont know if its connected:

Event Type:      Warning
Event Source:      WinMgmt
Event Category:      None
Event ID:      5603
Date:            12/05/2009
Time:            14:47:09
User:            NT AUTHORITY\SYSTEM
Computer:      VCTX01
Description:
A provider, MgmtEventProv, has been registered in the WMI namespace, Root\Citrix\Management, but did not specify the HostingModel property.  This provider will be run using the LocalSystem account.  This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.  Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.  

Ive done the install again, this time pointing at the old database and the problem is still there. Probably no point trying a new database. Agree?
It seems that this isnt to do with the move. The only thing I can think of that has changed recently would be installation of windows security patches, perhaps one of those has broken something&
This looks like a ODBC or SQl username/password issue. To test, try doing an install and choosing a new farm with a local access database. once it's done you can user the chfarm command and add it to the production farm.
I restored the VM to its orginal state and tried the install again with a new farm and local Access DB. I got the same error.

I really can't think of anything else that could have changed...
Is there anything else running on the server?
Are you at the console doing the install and not through RDP?
I'm doing the install via RDP as I always have in the past. Is that a bad idea?

Have read both of the articles, I've tried skipping the adding remote desktop users part.
Need to make another install log as I lost it when I reset the VM...

Nothing else running, just clean 2003 R2 SP2. No AV, nothing else.
check to see if you have this enabled on your policy.
printer.bmp
ASKER CERTIFIED SOLUTION
Avatar of BenBispham1
BenBispham1

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial