Hi Belgium,
For NWBC Desktop Client the favorites are stored in follwoing directories "C:\Users\<USERID>\AppData\Roaming\SAP\NWBC\NWBC.favorites " .
you can move this file to new PC.
Thanks,
BM
Hi Belgium,
For NWBC Desktop Client the favorites are stored in follwoing directories "C:\Users\<USERID>\AppData\Roaming\SAP\NWBC\NWBC.favorites " .
you can move this file to new PC.
Thanks,
BM
Hi Prithviraj,
This blog already checks it, but I do not deal very well like to do it, inside the route:/etc/init.d/sap would there be necessary to add the parameters inside the file sapini and later of the parameters that already it has? Or would there be necessary to create a file in white only with these parameters?
I have tried to add it with my <SIDadm> but on having restarted the servant does not start sap.
Might it detail do it to me like in order that it works?
Thank you very much
Regards
Hi Jose,
you can check for the sapcontrol Command lines to start and check the status of the services also after the startup.
Please find below links for same.
also the sapstartsrv is auto started using init.d in Linux. so it will be easy to use sapcontrol mechanism.
And use sudo su and ssh if you want to remotely do this activity.
Let us know if you need further help. and yes as mention in earlier reply you need to take help from you linux admins.
Regards,
Ram
Hi Experts,
We have successfully migrated BW system this weekend.
There are both ABAP and Java Systems with separate databases.
The system details are as below.
Operating system : Windows 2008
Database : Oracle 12.1C
Netweaver : 7.02
Type : Distributed system
After migration the Java status is not available from SAPMMC, but the JAVA system is up and running(checked from jcmon and users are logging in).
In mmc it only shows for jcontrol : status info unavailable. In AS Java processes nothing is shown.
Restarting the OS or closing and opening mmc has not solved it.
Result of sapcontrol -nr 00 -function GetProcessList:
30.09.2015 03:57:31
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
jcontrol.EXE, J2EE Server, YELLOW, Status info unavailable, 2015 09 20 00:56:59,
243:00:32, 5048
igswd.EXE, IGS Watchdog, GREEN, Running, 2015 09 20 00:56:59, 243:00:32, 648
Kindly help in resolving the issue.
Thanks in advance,
Anitha
Hi Friends,
In our ERP system we found that there are wrong entries in PAHI table for column System ID. there are number of single digit entries in SystemID in PAHI.
-Can you guys let me know why there are wrong entries or single digit values for system id in PAHI?
-How we can trace this single digit values to find out from where these wrong entries are coming ?.
Thanks,
Krishna
HI Anitha,
Please check below notes
1724391 - jcontrol.exe is in yellow status with message "J2EE info unavailable" in MMC
877795 - Problems with sapstartsrv from Release 7.00 and 6.40 patch 169
Thanks,
Mofizur
Hi Ram,
The Linux system we have if you have the sapinit script located in the /etc/init.d route.
I applied the steps outlined in this link:
All Agents of the Host | If you want to start or stop all SAP NetWeaver management agents on a host, call the sapinit script with the following parameters: sapinit stop sapinit start The command sapinit stop also shuts down all instances on the relevant host, since the command is mainly used for the shutdown of the host. In the same way, sapinit start starts the instances on the host, although only if the profile parameterAutostart=1 is set for this instance. Depending on the type of UNIX, the sapinit start script is at the following path:
|
If i run sapinit stop works.
The problem I have when I start it, I first added the parameter Autosart=1 n the instance profile, but doesn´t start. The process disp+work is stopped.
Do you know if that parameter must add in all the profiles?
Thanks
Regards
Hi Anitha,
What is the output of the commands below?
sapcontrol -nr 00 -function GetVersionInfo
sapcontrol -nr 00 -function J2EEGetProcessList
In addition we may need to check the profiles, if you please
Namastê,
Americo
Hi Jose,
Make sure you have things in place as mentioned in the below sap note..
823941 - SAP start service on Unix platforms
Regards,
Prithviraj.
Hi Prithviraj,
The file path Sapinit is correct: /etc/init.d/sapinit
I have reviewed the note 823941 and all parameters are correct, but I don´t know if i have to change something but that SAP starts automatically after a reboot of the machine.
I tried to add the parameter: Autostart=1 in the instance profile, but now SAP not start and the process "disp+work" is stopped.
Thanks
Regards
Hi Prithviraj,
The file path Sapinit is correct: /etc/init.d/sapinit
I have reviewed the note 823941 and all parameters are correct, but I don´t know if i have to change something but that SAP starts automatically after a reboot of the machine.
I tried to add the parameter: Autostart=1 in the instance profile, but now SAP not start and the process "disp+work" is stopped.
Thanks
Regards
Hi Prithviraj,
The file path Sapinit is correct: /etc/init.d/sapinit
I have reviewed the note 823941 and all parameters are correct, but I don´t know if i have to change something but that SAP starts automatically after a reboot of the machine.
I tried to add the parameter: Autostart=1 in the instance profile, but now SAP not start and the process "disp+work" is stopped.
Thanks
Regards
Hi Jose,
Do you mean that start process works fine but disp+work is stopped?
If yes....than
Please check the sapstart trace/log file placed @home directory of sidadm user to see what went wrong during startup.
Also check dev_disp, dev_w* log in work direcotry.
Regards,
Prithviraj.
Hi,
When I add the parameter Autosart=1 in the instance profile will not start when you restart SAP not even if I run it manually, I had to use a backup instance profile that not have this parameter and copying it to the Profiles folder.
Whereby the problem is that the parameter does not work correctly.
I'll do it again and check the logs that you indicate.
thanks
regards
Hi Mirso,
For analyzing startup issues on the disp+work component within ABAP instances, proceed as follows:
- Completely stop your SAPINST/SWPM;
- Completely stop your SAP system and services;
- Remove all files under /usr/sap/SID/INSTANCE/work
- Start the instance.
As soon as you see your dispatcher grayed out in the SAPMMC right after the startup attempt, go inside your work directory and read the newly created dev_w0 log. The reason for the issue will most likely be indicated on this log file. If you can't find anything on this log, look at log dev_disp as well.
Best of luck,
Ricardo
Hello Experts,
I am facing an issue during a patch upgrade for our Solman system using SUM.The patch upgrade i started using option "Manual stack directory" and components included for update are LM-Service/IS-AGENT/J2EE Engine/J2EE Core.
During execution phase SUM is throwing the below error
"Could not detect system components. Could not detect deployed components. Could not synchronize the table with system component versions with SDM repository. com.sap.sdm.apiimpl.remote.client.APIRemoteExceptionImpl: Server JBLDCVSDSSM03 did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server JBLDCVSDSSM03 at port 50018: Connection refused: connect (port 50018 to address 10.51.31.36) com.sap.sdm.apiimpl.remote.client.APIRemoteExceptionImpl: Server JBLDCVSDSSM03 did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server JBLDCVSDSSM03 at port 50018: Connection refused: connect (port 50018 to address 10.51.31.36 ".
When I checked I found that SDM is not running.I tried to start the SDM using standalone and integrated mode but no luck.
After this it is creating 2 log files "sdm_server.err" and "sdm_server.out".But both the files are of 0KB and no content is there.
Please suggest.
Hi,
The other thing I noticed was
The parameter Autostart=1 (careful: watch upper and lower case) should be mentioned in START profile and not in INSTANCE profile.
Regards,
Prithviraj.
Hi Neil,
I'm interested in having logging for deletion of Archivelink documents in SAP.
Regards,
Wayne
Hi Sreenivasa,
Please try SAP* initial user.
1.If currently sap* user is not having password "pass" means you have sap* user's details in your database. So delete sap* user from system database and required client.
2. Set parameter 'rdisp/no_automatic_user_sapstar' to value 0 in any one apps server of your system. And take restart of the system.
3. Login into the system (use user sap* and password as 'pass') with same apps on which you have set parameter and same client from which you have deleted sap* user
Then try to run client deletion. Hope it will work.
Thanks
Santosh
Hello,
You need to generate the certificate request at the Web Dispatcher, then sign this request and import the response from the CA.
Read the WIKI page below for assistance with the steps at the Web Dispatcher.
Managing PSE files at the Web Dispatcher - Application Server Infrastructure - SCN Wiki
Regards,
Isaías