Unable to launch Config tool to updaing the Secure Store

[Former Member]

Hi Experts,

We've moved a 7.01 J2EE stack to a new server, where the hardware key has changed. As a result, SAP is not able to build a connection to the Oracle database. (The database is startable via SQLPLUS).

In our attempt to update the secure store information, the configtool does not start to allow changes to the secure store - it simply dies out after not being able to build the connection.

The offline configurarion tool does not start at all for the same reasons.

Any thoughts on how to update the secure store to update the password?

Thanks,

Tim

[Former Member · Accepted solution]

Hello Tim,

To update the secure store you will have to use older version of secure store.

From the service marketplace download CORETOOLS*.SCA from 7.0 SP18 (this is the last SP where config tool doesn't close).

Extract CORETOOLS*.SCA with WinZip and find configtool.sda. Extract configtool.sda with WinZip and copy the properties files from your original configtool directory to the directory of configtool SP18 (2 files, with extension .properties or something similar). These configuration files will tell the new configtool where the secure store is located. After that you could start the config tool and edit the secure store.

Regards,

Ventsi Tsachev

[Former Member · Accepted solution]

Hi Ventsi,

Your answer was dead-on. We were indeed able to lauch the config tool from the 'remote' location and were able to edit the secure store files afterwards. SAP support has stated that the fix for 7.01 will be available with support stack 07 (not yet released).

On a side note, we found the true core of our issue. Apparently, once this server was moved to it's new location (new IP) a firewall rule prevented the proper functioning of the TNSlistener in building a java based connection string. The listener depended on the nslookup functionality working properly.

Once we corrected the port block and nslookup could function correctly, the listener also functioned correctly and everything began to flow.

We're up and running again. I don't understand the false positive we got here for the issue, but we're fixed and running again.

Thanks again Ventsi!

Tim