Problem with Volatile registry key
Hi everyone,
I'm currently working on "IBM iSeries Access for Windows V5R4M0" and have a problem while a profile-fix (self-repair) occur to update a HKCU registry entry.
Some info:
Registry table
Registry Root Key Name Value Component_
registry54 1 Software\IBM\Client Access Express\CurrentVersion\Volatile\Communication\Time Stamps\192.168.10.10 Default User Mode #2 CurrentUser
MSI-Log
Executing op: RegOpenKey(Root=-2147483647,Key=Software\IBM\Client Access Express\CurrentVersion\Volatile\Communication\Time Stamps\192.168.10.10,,BinaryType=0)
Executing op: RegAddValue(Name=Default User Mode,Value=#2,)
Note: 1: 1401 2: HKEY_CURRENT_USER\Software\IBM\Client Access Express\CurrentVersion\Volatile\Communication\Time Stamps\192.168.10.10 3: 1021
Message Code 1401 = Could not create key: [2]. System error [3].
net helpmsg 1021 = Cannot create a stable subkey under a volatile parent key.
Process Monitor
Process Name Operation Path Result Detail
msiexec.exe RegCreateKey HKU\S-1-5-21-1801674531-1078145449-682003330-1004\Software\IBM\Client Access Express\CurrentVersion\Volatile\Communication\Time Stamps\192.168.10.10 0xC0000181 Desired Access: Read/Write
Result code 0xC0000181 (STATUS_CHILD_MUST_BE_VOLATILE) = An attempt was made to create a stable subkey under a volatile parent key.
So what happens during logon for a user is that the "HKCU\Software\IBM\Client Access Express\CurrentVersion\Volatile\Communication\Time Stamps\192.168.10.10" key has already been created, I'm not sure yet which background process/service is creating the registry but it has been (guessing again) created with the RegCreateKeyEx function + REG_OPTION_VOLATILE option.
As I need to add the "Default User Mode" DWORD entry (value doesn't seem to make any difference) to set the "Prompt every time" "iSeries Signon Information" option for the 192.168.10.10 connection I need to go around this problem.
So; any idea how this could be solved?
I havn't tried to add the registry key to the RemoveRegistry table yet and then repair it as normal (through Registry table) but I guess that is my next attempt.
I'm currently working on "IBM iSeries Access for Windows V5R4M0" and have a problem while a profile-fix (self-repair) occur to update a HKCU registry entry.
Some info:
Registry table
Registry Root Key Name Value Component_
registry54 1 Software\IBM\Client Access Express\CurrentVersion\Volatile\Communication\Time Stamps\192.168.10.10 Default User Mode #2 CurrentUser
MSI-Log
Executing op: RegOpenKey(Root=-2147483647,Key=Software\IBM\Client Access Express\CurrentVersion\Volatile\Communication\Time Stamps\192.168.10.10,,BinaryType=0)
Executing op: RegAddValue(Name=Default User Mode,Value=#2,)
Note: 1: 1401 2: HKEY_CURRENT_USER\Software\IBM\Client Access Express\CurrentVersion\Volatile\Communication\Time Stamps\192.168.10.10 3: 1021
Message Code 1401 = Could not create key: [2]. System error [3].
net helpmsg 1021 = Cannot create a stable subkey under a volatile parent key.
Process Monitor
Process Name Operation Path Result Detail
msiexec.exe RegCreateKey HKU\S-1-5-21-1801674531-1078145449-682003330-1004\Software\IBM\Client Access Express\CurrentVersion\Volatile\Communication\Time Stamps\192.168.10.10 0xC0000181 Desired Access: Read/Write
Result code 0xC0000181 (STATUS_CHILD_MUST_BE_VOLATILE) = An attempt was made to create a stable subkey under a volatile parent key.
So what happens during logon for a user is that the "HKCU\Software\IBM\Client Access Express\CurrentVersion\Volatile\Communication\Time Stamps\192.168.10.10" key has already been created, I'm not sure yet which background process/service is creating the registry but it has been (guessing again) created with the RegCreateKeyEx function + REG_OPTION_VOLATILE option.
As I need to add the "Default User Mode" DWORD entry (value doesn't seem to make any difference) to set the "Prompt every time" "iSeries Signon Information" option for the 192.168.10.10 connection I need to go around this problem.
So; any idea how this could be solved?
I havn't tried to add the registry key to the RemoveRegistry table yet and then repair it as normal (through Registry table) but I guess that is my next attempt.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
Mallikarjun
9 years ago
Hi am also looking the solution for the same issue. Could anyone help on this?
Comments:
-
When I am creating a registry manually in this hive I am getting an error - Cannot create key: Error writing to the registry (HKEY_CURRENT_USER\Software\IBM\Client Access Express\CurrentVersion\Volatile\Communication\Time Stamps)...but if I launch the shortcut and select 'prompt every time' its taking. - Mallikarjun 9 years ago
Posted by:
kiptek
15 years ago
try installing from vendor media onto a machine but not launching the app. if you go into the HKCU tree, do you see these keys? Now launch the app & check? Maybe you do not need to include these keys as they may be created by the sign on process...
Posted by:
AngelD
15 years ago
RemoveRegistry did the trick; removes the existing key with all subkeys during repair and then re-writes them back.
RemoveRegistry Root Key Name Component_
RemoveRegistry1 1 Software\IBM\Client Access Express\CurrentVersion\Volatile - CurrentUser
Kip,
The app creates the DWORD entries "Host VRM" and "Admin System Indicator" but not "Default User Mode" which I needed.
I wish I had though of the RemoveRegistry idea like 2 days ago :)
RemoveRegistry Root Key Name Component_
RemoveRegistry1 1 Software\IBM\Client Access Express\CurrentVersion\Volatile - CurrentUser
Kip,
The app creates the DWORD entries "Host VRM" and "Admin System Indicator" but not "Default User Mode" which I needed.
I wish I had though of the RemoveRegistry idea like 2 days ago :)
Posted by:
anonymous_9363
15 years ago
IBM software's a piece o' work, ain't it? Jeez, they can't decide, even now, whether it's called 'iSeries Access' or still called 'Client Access'. Don't get me started on the DLLs which have to be registered by their custom EXE...
Was this available as an MSI, Kim? I recall their beta for V5R2 was missing 'iSeries Navigator', amongst clearly non-essential features [sarcastic].
Was this available as an MSI, Kim? I recall their beta for V5R2 was missing 'iSeries Navigator', amongst clearly non-essential features [sarcastic].
Posted by:
AngelD
15 years ago
I can't understand why vendors still insist to create non-msi based installations now days.
Couldn't find any MSI that was not related for 64-bit with a fullblown installation Ian, so I had to capture the legacy setup and "servicepack" (SI27741).
Couldn't find any MSI that was not related for 64-bit with a fullblown installation Ian, so I had to capture the legacy setup and "servicepack" (SI27741).
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.