ProvideX:Initialization error on launch

[doliber]

I have a customer that just upgraded to MAS90 3.71. Entire new network... Windows Server 2003 and new XP Pro workstations. All other workstations launch MAS error free and are functional. One machine however is throwing fits. I receive the above type error which states: Cannot open Activation key file - No Valid Activation Found!!

I've worked with the support person on this and she believes it is a problem with the user account. I have deleted the user account from the server and recreated, added permissions individually for MAS to this user, disconnected the network drive; removed MAS, remapped the drive and reinstalled MAS. Same error when trying to launch. I then removed the computer from the domain, rebooted and readded. Same error when launching.
Does anybody have any thoughts?

 

[mrstnturner]

can you unistall the workstation? can you reinstall the workstation? we are getting the same type of error and i can not unistall because it says it can not find the binary code. and i can not reinstall over itself because it gives me an error about an unistall in process error 432. is any of this the same problem you are having????

 

[doliber]

Couple things we found here. When the MAS support person installed/converted the MAS 90 folder is three levels deep. Each of these folders were shared out. Permissions were all over the place, some inherited others not. Here is an excerpt of documentation that was found and worked in my customers case:

MAS 90 path may be mapped incorrectly. The ..\MAS90 directory itself might be shared so that the workstation only see the directories beneath the MAS90 directory (e.g. F:\Home instead of F:\MAS90\Home.
Remove the share form the MAS 90 directory and share the drive or directory above ..\MAS90.
Reinstall System Setup from the workstation so that the installation path is consistant with the path that the workstation sees.
NOTE: If ..\MAS90 is under a shared direcotry (e.g. C:\apps\mas90, the workstation sees F:\MAS90), System Setup must be installed from a workstation so that the installation path is consistant with the mapping.