I want to test the upgrade process of Discovery.
I zip the Discovery program folder in the source prod. machine. Copy the zip and extract in the same drive and directory of another machine.
But when I run Discovery.exe -s in another machine, I type the password (current one used in source prod. machine), it shows Wrong password...
How to resolve this issue? Are there any specific procedures?
I found somewhat of a workaround, not sure how much this will help.
It should be noted that credentials will still be broken, but all the other settings will remain.
If you install a fresh instance, set a password, open "Discovery.cfg", copy <InstanceID>*****</InstanceID><AnalyticsInstanceID>********************************</AnalyticsInstanceID><Version>7.0.3</Version><SettingsType>Discovery</SettingsType><ServerObjectHash>********************************</ServerObjectHash><MPWHash>****************************</MPWHash> and paste it into the old instance folder's "Discovery.cfg" to replace the old section, it should open using the password.
It's kind of complicated and I didn't get the credentials out of it, but it kind of worked. Hopefully Atlassian has a better solution though.
I am also seeing this issue when following the same steps. I believe its also causing the machine not to report into Atlassian Cloud after scanning
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@elui I'd be interested to hear how you made your deployment and how you resolved this particular issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.