Logon Load Balancing

1. Install all application server/dialog instances


2. Configure Logon Group using transaction SMLG


3. Assign proper instance, check mark Ext. RFC enabled, provide reponse time and number of users


4. Click on Copy


5. Do the same for all Instances


6. Save


7. Go to your system directory, system32\drivers\etc\services file


8. Add the following entry


9. sapms 39xx/tcp


10. The above port number should be the same what you used as Message Server port during your Dialog Instance installations


11. Go to your SAP GUI logon pad


12. Configure your connection details as following:


13. Create or Modify by clicking New Item or Change Item


14. Provide Description


15. Provide System Id


16. Provide Message Server


17. Move to Group/Server tab and the Logon Group you created should become visible there along will all app servers and what processes they have


18. System Number should come automatically as well


19. Click OK

Test the logon!!!

How to apply MSSQL Patch/SP for DB in SAP System

SAP System
DB - MSSQL
OS - Windows Server


Straight and Simple:

1. Download the patch from SAP Service MarketPlace
2. Stop SAP using MMC
3. Stop DB using MS Visual Studio
4. Stop all SAP Services from service.msc
5. Stop all SQL Services from service.msc
6. Close MMC console
7. Close MS Visual Studio console
8. Drill down the installer for your OS/HW from the downloaded media, i.e. x64, x86, etc.
9. Double Click the installer
10. Let the installer check if any conflicting services are running or not
11. Complete the installation
12. Check DB/Bring DB online
13. Check SQL services/Start SQL services from service.msc
14. Start SAP services from service.msc
15. Start SAP using MMC

SQL Patching is done!

Check and confirm SQL patch number from MS Visual Studio.

Good luck!

Shival

Dialog Instance Installation

Short and Sweet scenario:

SAP System: SAP CRM 5.0
OS: Windows 2003 Server R2, SP2
DB: MSSQL 2005, SP3

I have a newly installed central instance up and running

Now, I upgraded the kernel.

Now, tried installing Dialog Instance and got the error of "disp+work" not starting up.

Following is what worked!!

1. Restored the original kernel files.
2. Uninstalled the progressed installation of DI
3. Re-initialized DI installation.

And it went through!

###############

Now I upgraded kernel on Central Instance.

DI Dialog Queue became unavailable.

Following is what worked!!

1. Stop MMC on Dialog Instance
2. Stop sap_NN service
3. Close MMC window
4. Close service.msc window
5. Physically Copy 'sapstartsrv.exe' from Central Instance.
6. Rename 'sapstartsrv.exe' under Windows\system32 (being conservative)
7. Paste 'sapstartsrv.exe' to this location.
8. Open MMC window
9. Start SAP
10. The above should work just fine!!!

Try referring following SAP Notes for digging this deeper!!!

1. sapnote_0000035278 - STARTSAP-STOPSAP - TIME OUT no system connected
2. sapnote_0000072248 - In NT Dispatcher in status Yellow - SAP system running
3. sapnote_0000142100 - Windows Problems with new SAP service as of Rel. 4.5B
4. sapnote_0000396309 - Dispatcher remains yellow, although the system is running

Good luck!

Shival B. Tailor
sbtailor@gmail.com