An important update of Process Monitor was released couple of a days ago:
As you may know, we can use two functions with completely opposite names to open registry key: RegCreateKeyEx and RegOpenKeyEx. When you use RegCreateKeyEx, it creates registry key if it’s non-existed, but just opens it if key exists. RegCreateKeyEx writes which operation (create or open) it’s performed into a separate variable.
RegOpenKeyEx cannot create registry keys and returns error if key doesn’t exist.
Before this release there were no way to determine what operation exactly RegCreateKeyEx perform. “Granted Access” property for execution of that function always contained “Read/Write” value.
From this last update, Process Monitor finally can show you what RegCreateKeyEx does. There is no “Granted Access” property for RegCreateKey operation anymore, it was replaced with new “Disposition” property. “Disposition” may contains following strings:
REG_CREATE_NEW_KEY – if new registry key was created.
REG_OPENED_EXISTING_KEY – if RegCreateKeyEx just opened previously existed key.
“Desired Access” property still contains “Read/Write” value, because we cannot predict which action RegCreateKeyEx will do.
Using this new feature, you can separate RegCreateKeyEx calls: just add new condition into Process Monitor’s filter with following parameters:
Column – “Detail”
Relation – “contains”
Value – “REG_CREATE_NEW_KEY” or “REG_OPENED_EXISTING_KEY”
Action – “Include”
You have one secondary DPM-server (DPM3) and 2 primary connected to it (DPM1 and DPM2). You have a server (PS1) protected by DPM1 and DPM3. You decide to move protection of PS1 from DPM1 to DPM2. You stop protection of PS1 at DPM1 and DPM3. You connect PS1 to DPM2. You wait until first replica is created, then you try to add PS1 back to DPM3 but from DPM2 this time.
In that case you cannot see PS1 at DPM3 in the list of data sources protected by DPM2.
This happens because each protected server has a single record in a table of protected servers at DPM configuration database. One of the attributes of this record is an ID of DPM server protecting that data source. Since secondary DPM knows nothing about you moving data sources between primary servers, it doesn’t update that record with an ID of a new primary DPM server.
You can fix this by manually updating DPMServerId attribute of migrated protected server with an ID of new primary DPM server.
WARNING! This scenario IS NOT supported by Microsoft. Use instructions below at one’s own risk, except and only when you are specifically instructed by Microsoft technical support specialist to do this.
Be sure to backup your DPMDB database before run any T-SQL command!
- Connect to DPMDB of your secondary server (You can find more about it here).
- Get a list of DPM-servers and their IDs:
SELECT ServerId, ServerName, DPMServerId FROM [dbo].[tbl_AM_Server] WHERE IsDPM = 1
- Write down IDs of DPM1 (<OLD-ID>) and DPM2 (<NEW-ID>).
- Determine which primary DPM-server protects PS1 according to the knowledge of DPM3:
SELECT DPMServerId FROM [dbo].[tbl_AM_Server] WHERE ServerName = '<Protected Server's FQDN>'
- Make sure it equals <OLD-ID>, otherwise this instruction is not for you — contact Microsoft Support instead.
- Update protected server record with ID of new primary server:
UPDATE [dbo].[tbl_AM_Server] SET DPMServerId = '<NEW-ID>' WHERE ServerName = '<Protected Server's FQDN>'
- Run new/modify protection group master and press “Clear cache” button.
- You are now able to protect moved resource at secondary DPM again.
- Never ever move protected servers between primary DPMs connected to the same secondary server, since it is NOT supported by Microsoft.
Connection parameters for System Center Data Protection Manager configuration database are located into registry key HKLM\SOFTWARE\Microsoft\Microsoft Data Protection Manager\DB on the computer where DPM server is installed. You can quickly determine essential parameters by running following PowerShell commands:
SQL server name:
(Get-ItemProperty 'HKLM:SOFTWARE\Microsoft\Microsoft Data Protection Manager\DB').SqlServer
(Get-ItemProperty 'HKLM:SOFTWARE\Microsoft\Microsoft Data Protection Manager\DB').DatabaseName
SQL server instance:
(Get-ItemProperty 'HKLM:SOFTWARE\Microsoft\Microsoft Data Protection Manager\DB').InstanceName
Use SQL Server Management Studio to connect to DPM database using values from above. If SQL server instance name is “MSSQLSERVER”, you should omit it while connecting to SQL server.
Only local administrators group is alowed to access DPMDB by default. If you run SSMS on a DPM server locally, don’t forget to run it as administrator.
When you install HP Lights-Out Passthrough Service at a Terminal Server (which means you have RDP Service enabled for multiple users) you receive following errors:
- In installer: Service ‘HP Lights-Out Passthrough Service’ (hplopts) failed to start. Verify that you have sufficient privileges to start system services.
- In Application Log: The Passthrough Service could not be started. You must install Terminal Services or enable Remote Desktop.
This happens because of weird prerequisites check.
Set registry key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerfDenyTSConnections = “0”. Installation should succeed.
If you need to defragment your Exchange database at a computer without Exchange components, you will probably use this MS KB: 244525: How to run Eseutil on a computer without Exchange Server. I tried it when I was defragmenting Exchange 2003 database at a Windows Server 2008 R2 machine.
Eseutil was running fine, but after some time (when it used just over 2 GBs of RAM), I received an error described here: 273087: Error With Jcb.dll While Running Eseutil. Unfortunately, none of the methods described there were useful: when I pressed «Cancel» button, I received an «Operation terminated with error -2102 JET_errCallbackNotResolved, A callback function could not be found) after 1168.136 seconds.» error.
Eventually, I grabbed Process Monitor and found out that files described in Microsoft’s KB 244525 and in this thread «Re: JCB.DLL Not Found Error» weren’t enough – you need another one file: ntlsapi.dll. I copied it from a nearest Windows Server 2003 R2 SP2 box to a system where eseutil were working and everything went smoothly.
When you are trying to change or delete client attributes from client list in master server properties, you get an error:
Unable to save data on some hosts
An error occurred on host example.com. The error is " (1)".
- Go to NetBackup installation folder (usually it’s %PROGRAMFILES%VeritasNetBackup). Then proceed to dbclient folder.
- If there is only one file and it is named “GP_”, go to step 3. If not, I can’t guarantee anything.
- Delete dbclient folder.
- Restart NBU services.
When you are trying to check NetBackup 6 or 7 catalog with NBCC (NetBackup Catalog Consistency Check) utility at Windows, you get an error: «The filesystem for the outputnbccserver.fqdn.name_NBCC_DATE_TIME directory either doesn’t have 1024000 KB of space available. Evaluate the space available and the potential space requirements needed by NBCC to perform the consistency checks and look at the potential usage of the -kbfree command line switch.»
When NBCC checks for free space at a disc, it parses output of DIR command. It looks for the last string at the output which looks like “123,456,789 bytes free”. If you are NOT using a comma (,) as a digit grouping symbol or if you are running NON-ENGLISH version of Windows, NBCC can’t check for free space.
If you are using english version of Windows, just go to «Regional and Language Options» and set «Standards and formats» to the «English (United States)». You can revert it back after NBCC will done.
If you are using non-english version of Windows, run the “nbcc -kbfree 0” command to skip disk free space check.
You can use the same method to avoiding «NBCC aborts with error “Can’t use an undefined value as an ARRAY reference” on a non-English Windows master server» instead of ridiculous Symantec’s methods.
While HP doesn’t support Microsoft Windows Server 2008 R2 as operating system for DL3x0 G4, you can install this software to it as usual. But after installation you find out no information at “HP System Management Homepage”.
This happens because neither WBEM components, nor HP Insight Management Agents cannot be installed.
When you try to install WBEM/HPIMA manually, you receive following error:
Installation for “HP Insight Management Agents for Windows Server 2003/2008 x64 Editions” requires one or more of the following that is not currently installed or in the install set:
– HP ProLiant Advanced System Management Controller Driver for Windows
– HP ProLiant iLO Advanced and Enhanced System Management Controller Driver for Windows
– HP ProLiant iLO 2 Management Controller Driver for Windows
– HP ProLiant iLO 3 Management Controller Driver for Windows
- Download HP ProLiant iLO Advanced and Enhanced System Management Controller Driver for Windows Server 2008 x64 Editions (cp010914.exe) to the server.
- Extract downloaded file with integrated extract feature.
- Set the compatibility mode for cpqsetup.exe as “Windows Server 2008 (Service Pack 1)”.
- Run cpqsetup.exe, installation should works fine.
- Install HP Insight Management Agents/WBEM as usual.
- Also, one unknown device will disappear from Device Manager — it is called “HP ProLiant iLO2 Advanced System Management Controller” from now.
When you are trying to update or install a driver via CompMgmt.msc and click “Update driver”, nothing happens. Also, you get an errors in System log:
Event Type: Warning
Event Source: PlugPlayManager
Event Category: None
Event ID: 264
Client side device installation was not performed because the file "C:WINDOWSsystem32newdev.dll" was not found.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Just extract NEWDEV.DL_ from distributive of Windows Server 2003 to %SYSTEMROOT%System32newdev.dll.