msjava on Windows 7 SP1
Hi!
In our company we recently upgraded from Windows 7 to Windows 7 SP1 and since then out package deployment of msjava stopped working.
MSjava is needed for a old program (HPSD, Hewlett Packard Service Desk) and it worked fine with Windows 7.
The problem seems to be with permissions to create folders under C:\Windows\winsxs. The installer wants to place files under amd64_microsoft-windows-gdi_..........6.1.7600.16734......... (6.1.7600.16734 is related to the windows OS version I assume). Since after the upgrade this folder doesnt exist and the installer has no rights to create it to my amazement.
I tried to take ownership of the winsxs folder and put modify permissions to the administratoraccount and then it worked!
But isn´t there a way to give access for the installer to place the files under winsxs? The file I first encountered an error with was: dciman32.dll if this gives you any more valuable information.
In our company we recently upgraded from Windows 7 to Windows 7 SP1 and since then out package deployment of msjava stopped working.
MSjava is needed for a old program (HPSD, Hewlett Packard Service Desk) and it worked fine with Windows 7.
The problem seems to be with permissions to create folders under C:\Windows\winsxs. The installer wants to place files under amd64_microsoft-windows-gdi_..........6.1.7600.16734......... (6.1.7600.16734 is related to the windows OS version I assume). Since after the upgrade this folder doesnt exist and the installer has no rights to create it to my amazement.
I tried to take ownership of the winsxs folder and put modify permissions to the administratoraccount and then it worked!
But isn´t there a way to give access for the installer to place the files under winsxs? The file I first encountered an error with was: dciman32.dll if this gives you any more valuable information.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
jmaclaurin
13 years ago
Posted by:
jmaclaurin
13 years ago
Posted by:
Agathorn
13 years ago
The installation is executed in the same way as every other installation, via SCCM. It worked fine before SP1 and now stopped working. I also tried to execute it from a command prompt run as administrator with the same outcome.
So yeah, I guess something has changed with access rights to the folder in SP1.
So yeah, I guess something has changed with access rights to the folder in SP1.
Posted by:
anonymous_9363
13 years ago
Posted by:
Agathorn
13 years ago
Posted by:
anonymous_9363
13 years ago
Posted by:
Agathorn
13 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.