JMS problem with 2004s Java Preview

[peter_norris]

Just installed the full preview of the Java stack for 2004s.

After a frustrating time making sure the DB would install, the install process finally installed running under XP.

The app server appears to work ok, and serves up pages, including the portal login except that whenever I attempt to authenticate for any page I get the message:

com.sap.engine.services.deploy.container.ExceptionInfo: JMS error

In addition the Visual Admin refuses to authenticate.

Anyone come across this. I'm about to reboot the server to see if the JMS service will start, but it takes 45 minutes to boot!

Postscript: Couldnt SAP have made the additional components (Portal etc) instalable options - at least I could have got the server working first without having to wait all the time for the additional content?

[peter_norris]

Restarting the server fixed the JMS issue.

I still have an authentication problem but this appears to be because the Adminstrator user is locked on the server. I'm not sure how this could have happened given that my password for all users was "password"!

[peter_norris]

The procedure for fixing a corrupted (?) Administrator user is covered in SAP Note 669848.

It involves using the Config Tool (with the cluster stopped) to set the SuperAdmin user "SAP*" to active.

Once SAP* is active the server can be restarted and the UME used (having signed in with SAP*) to update the Administrator password.

However, until you disable the SAP* user again (which means another server bounce) you cannot sign on using any other user.

For me this was roughly 60 minutes of effort - just to change a password.

If there are any folks out there with infinite patience who want to make a lot of money consulting, my guess is doing WAS installs could be lucrative - if time consuming and boring.

[Former Member]

I too have a Problem with login to the Portal 2004s Preview. I tried to login with "admin" "admin" and also with the master-pwd i entered at installation time, but cannot log in, till the user was locked. So I installed the whole thing again, with the same result, no logon possible. Some clues?

Regards

Helmut

[Former Member]

ok, i think i have found the solution:

I was able to log on to my newly installed portal 2004s system with the password that is written in the installation document delivered with the preview edition. I entered a personal master password at installation time, but the system is still using the SAP suggestion...not mine...think it is an error within the installation routines

Regards

Helmut

[peter_norris]

Helmut - if you are still unable to login then the solution is contained in SAP Note 669848.

Enter 669848 into the search field and filter by SAP Support Notes.

As I mention above, it requires that you enable the SAP* userid. The only problem is that if SAP* userid is active then noone may use the system except SAP* until the userid is deactivated.