This error happened when the FCS MMC was launched:
FX:{f337d96e-45c1-4106-88b1-e417a7703d6b}
Solution for this problem is to install this MS Hotfix KB942581.
It must be order it from Microsoft and in one day Microsoft will deliver it.
The ZIP file contain KB942581.sql script file.
There is a MS Article ID with a way how to install it:
http://support.microsoft.com/kb/942581
After the installation this problem is solved.
Tuesday, March 16, 2010
Friday, March 5, 2010
Problem with deploying REG file with SCCM 2007 R2 to 64-bit Windows Server 2008
Registry modification REG file by SCCM 2007 R2 can deploy with this command:
regedit.exe /s MyRegFile.reg
where /s is used to suppress the confirmation dialog
BAT file, including this command, is created and it works on the way how we want.
Ex: If we execute this BAT manually, MyRegFile.reg creates all nesseccery REG folders and sub keys under:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags]
When this BAT is pushed by SCCM 2007 R2 on Windows Server 2008 or Windows 7 64-BIT MACHINES it creates folders and keys under:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AppCompatFlags]
I'm not sure why it does working on this way, but the alternative to avoid this issue is to deploy this BAT file with GPO.
All REG folders and files are created under:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags]
regedit.exe /s MyRegFile.reg
where /s is used to suppress the confirmation dialog
BAT file, including this command, is created and it works on the way how we want.
Ex: If we execute this BAT manually, MyRegFile.reg creates all nesseccery REG folders and sub keys under:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags]
When this BAT is pushed by SCCM 2007 R2 on Windows Server 2008 or Windows 7 64-BIT MACHINES it creates folders and keys under:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AppCompatFlags]
I'm not sure why it does working on this way, but the alternative to avoid this issue is to deploy this BAT file with GPO.
All REG folders and files are created under:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags]
Event ID: 8149 "The client-side extension could not remove user policy settings for ' ' ...
Event ID: 8149 :The client-side extension could not remove user policy settings for ' ' because it failed with error code '0x8007000d The data is invalid.' See trace file for more details.
- System
- Provider
[ Name] Group Policy Power Options
+ EventID 8194
[ Qualifiers] 34305
Level 2
Task 2
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2010-03-04T19:39:38.000Z
EventRecordID 23269
Channel Application
Computer "Server name"
- Security
[ UserID] xxx
- EventData
remove
user
0x8007000d The data is invalid.
_____________________________________________________
This error has appeared in Application log on Windows Server 2008.
This error was related with Client Side Extensions and Power Options.
The GPO with Group Policy Preferences with settings for Power Optiond previously was deleted and this GPO was not applied any more.
The solution was to rename XML files to this folder:
C:\ProgramData\Microsoft\Group Policy\History\{11111111-1111-1111-1111-111111111111}\S-1-5-21-1111111111-111111001-1111111110-1111\Preferences\PowerOptions\PowerOptions.xml
Note: C:\ProgramData is hidden in Windows Server 2008.
This alert has dissapeared after renaming XML files.
- System
- Provider
[ Name] Group Policy Power Options
+ EventID 8194
[ Qualifiers] 34305
Level 2
Task 2
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2010-03-04T19:39:38.000Z
EventRecordID 23269
Channel Application
Computer "Server name"
- Security
[ UserID] xxx
- EventData
remove
user
0x8007000d The data is invalid.
_____________________________________________________
This error has appeared in Application log on Windows Server 2008.
This error was related with Client Side Extensions and Power Options.
The GPO with Group Policy Preferences with settings for Power Optiond previously was deleted and this GPO was not applied any more.
The solution was to rename XML files to this folder:
C:\ProgramData\Microsoft\Group Policy\History\{11111111-1111-1111-1111-111111111111}\S-1-5-21-1111111111-111111001-1111111110-1111\Preferences\PowerOptions\PowerOptions.xml
Note: C:\ProgramData is hidden in Windows Server 2008.
This alert has dissapeared after renaming XML files.
Monday, March 1, 2010
Maya 2010, isscript.msi and Directx problem
When installation of Maya2010.msi is launched there is an error "The InstallScript engine is missing from this machine. If available, please run ISScript.msi, or contact your support personnel for further assistance."
ISScript.msi is in the same folder as Maya2010.msi and it has to be executed and installed in order to install Maya 2010.
But when Maya 2010 is launched there is another error:
"The program can't start because d3dx9_39,dll is missing from your computer... "
ISScript.msi is in the same folder as Maya2010.msi and it has to be executed and installed in order to install Maya 2010.
But when Maya 2010 is launched there is another error:
"The program can't start because d3dx9_39,dll is missing from your computer... "
To resolve this problem just install the latest DirectX.
Subscribe to:
Posts (Atom)