on 01-27-2005 9:03 PM
I have WebAS 6.20 installed. I have set up my RZ10 parameters as described in Craig's recent weblog.
When I run transaction SICK I now get the following error:
"application server with enque service P123456_BSP_00 not running"
Any ideas how I can fix this?
Thanks and regards,
JB
Jonathan, can it be that the incorrect profile is inactive. Please check whether the BSP_D00 profile is active (using RZ10). And any other Instance Profile is deactivated, by checking basic Maintenance. When profile is inactive a error message appears stating the Server is not active. Also make sure after having made any changes in the profile that you restart the application server for the changes to be applied. Kind regards, Tiest
Message was edited by: Tiest van Gool
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Craig and Tiest,
Thanks for your answers. I have now re-installed MiniWAS so that everything is vanilla.
Now, when I start SAP and run transaction SICK/SM28 the system says 'no application server offers an ENQ service'.
Any ideas how I can add an ENQ service to the Application Server?
Furthermore, I have had a look in RZ10 and I have three profiles defined: DEFAULT (Default profile), BSP_DVEBMGS00_P72367 (Instance profile) and START_DVEBMGS00_P72367 (Start profile). The server name in all of these profiles is <b>p72367_BSP_00</b> - should I change this to the correct server name which I believe to be <b>P123456_BSP_00</b>? Will this help with the ENQ problem above?
Thanks for any help you can provide. The first few steps on Craig's weblog are proving to be frustrating for me!
JB
Jonathan, in order to determine which instance profile is used by the WAS, check the Application Server Command Prompt window. In this window look for the REM statements and check the following commands: start /B msg_server.exe pf=<<YOUR PROFILE>> and disp+work.exe break pf=<<YOUR PROFILE>>. Make sure you have updated the Work Process parameters as described in Craig's weblog in this profile, restart your WAS and transaction sick should not return any error anymore. Tiest
Tiest,
Thanks for your help. I have now managed to import the SPAM update and enter in the ABA and BASIS SP's upto number 30. All is going well so far. I didn't make any changes to the RZ10 transaction. SICK is still showing an ENQ error but the transport system seems to be working fine besides this problem.
I would still like to clear the error out of SICK but don't want to risk playing with the profiles yet until I have finished updating the system and have made a backup.
Incidentally, I could only find SP's upto number 41 - where are the SP's upto 43/44?
Thanks again,
JB
Craig,
Thanks for your reply. I am now upto SP31 and the ENQ error is SICK is still there.....
Which section of your weblog are you referring to? If I could just get rid of this SICK error
When looking on SAP Marketplace for the SP's which link are you clicking on? I click on SAP Downloads -> SAP Support Packages -> Support Package Stacks -> SAP R/3 4.7x200. The dropdowns for ABA and BASIS on the next page show upto SP 44 but don't allow me to download anything above SP 41. Any ideas?
Thanks and regards,
JB
Found the SP's on Marketplace now - here are the directions:
Goto <a href="http://service.sap.com/swdc">http://service.sap.com/swdc</a>
Then navigate to Download -> Support Packages and Patches -> My Company's Application Components-> SAP R/3 ENTERPRISE-> SAP R/3 ENTERPRISE 47X200->SAP R/3 Enterprise Server
This has all SP's upto 48 for ABA and BASIS.
I have tried setting the parameters for BTC and ENQ as described in your weblog and I got the error as mentioned in the first post of this thread. Now that my system is more up-to-date I will try it again tonight and let you know how I go on. After making a backup of course!!
Thanks again,
JB
Craig,
I tried your suggestion last night and set the parameters as described in your weblog and <b>it worked!!</b> Thank you for your help with this issue - my SICK transaction now display no errors.
I am sure this didn't work after I had installed MiniWAS, I think the kernel needed to be updated for this to work, at least in my case. Either way, it is working now so thanks again.
Regards,
JB
Congrats! I have the same (ENQ) problem you had before, so would like to upgrade my kernel first as you suggested.
Would you mind telling us what exact upgrades you downloaded and applied (Kernel, TP, MaxDB...) please? I'm having trouble relating the various available downloads to those required (for 6.20 SP24).
Many thanks in advance...
User | Count |
---|---|
92 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.