/build/static/layout/Breadcrumb_cap_w.png

Question on Integer values in registry

OK this is really frustrating. I'd like to be able to configure a server port at runtime, an interger value being
"TCPAgentPort" in the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\TNT Software\ELM Log Manager\5.5\Settings

I would the option change the Reg Value (an integer specifying a port) at install time. I tried setting a property TCPAGENTPORT to a numeric value in the property table, with and without the #, and also specifying the registry value TCPAgentPort=#[TCPAGENTPORT] and I keep getting errors telling me I can't write the value. It works fine just hard coding the number in the registry table, TCPAgentPort=#1260 or whatever.

I know there's got to be a way to do this? What am I missing? Thanks in advance for any help.

0 Comments   [ + ] Show comments

Answers (4)

Posted by: pgiesbergen 15 years ago
Orange Belt
1
I get the error message if the property is not in the property table. If I add one the install succeeds. Are you sure did not made a typing error in the property somewhere? You probably know that an empty value is returned if the value between "[]" cannot be resolved, and DWORD values cannot be empty, therefore the error message.

Cheers,

P.
Posted by: pgiesbergen 15 years ago
Orange Belt
0
What happens if you enter value #[TCPAGENTPORT] in the registry table directly? Or create a new key, double Word with the property as value. Should have the same effect. Works ok here with a simple test project. Or did I misread your post and you've done that already? I checked their website and it s a vendor msi [:@], maybe in there something is screwing things up. Just for fun do a capture and see if that works [;)]
Posted by: aogilmor 15 years ago
9th Degree Black Belt
0
ORIGINAL: pgiesbergen

What happens if you enter value #[TCPAGENTPORT] in the registry table directly?

It gives the error. TCPAGENTPORT is set to a numeric value in the property table (but of course it's a string) but my understanding is that in this case #[TCPAGENTPORT] should work.
Posted by: aogilmor 15 years ago
9th Degree Black Belt
0
i will double check the logs when i get in on monday
i did put the properties in, possible i could have made an error in the name.
at one point the log did point to the value of TCPAGENTPORT being '1260' with single quotes so I'm still thinking it had to do with the string to dword conversion, i thought it would be resolved by just putting the # in front of the property like #[TCPAGENTPORT], but kept getting the error. Thanks!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ