Client Error 1001

By Hans Wilhelmsen, Updated on 26 Jun 2012
push_pin
star

Ok, so this annoying bugger of an error message has been causing some issues lately. It appears at the very end of the client installation and rolls back the installation.

Luckily it's usually one client at the time though.

 

The problem i encountered today revealed that the Install Shield process ISBEW64.exe could not be extracted from ISREGSVR.dll. Doing some googling, I quickly realised that this didn't tell me all to much on how to fix the issue, as almost all cases were different.

We tried a few solutions without any success, and tried extracting the msi (SuperOffice7.exe /a) and running it alone with different parameters.

 

What I suddenly realised though, without actually getting to the core of the issue is that this error occurs due to something not being quite right in the users profile, but seeing that everything else worked fine it would be nice to find a way to solve this without recreating the entire user profile.

 

So after a little while I came up with an idea (one which I probably should have thought of sooner though).

Shift+Right Clicking on SuperOffice7.exe -> Run as Different User -> <enter credentials for some other user>.
Turns out this did the trick and got stuff done. 

 

While this didn't fix the user profile, it sure solved the problem for this user. It made me wonder though, if anyone who reads this knows a whole lot more about user profiles than me; why on earth did it work? Does suddenly look to access other .DLL files or might it just be that it used files from a non-broken/corrupt user profile? :)

I had the same xperience as you tonight installing a lot of clients. One of them got the Error 1001. Didn't think of running as another user since i used a domain user account. So when i tried that after reading your post everything went ok. So thank you for sharing!


Dag 

Dag Engebretsen 4 Oct 2012