on 07-03-2007 4:01 PM
My Netweaver 2004s SP11 hangs up during the "Start central services instance" -
Connection to message server failed: NIECONN_REFUSED.
I looked it up in help.sap.com and they suggested:
Check if the central service instance is already running. The message server has to be up and running on the specified host and port.
How can I check the above?
Thank you.
Hi Amr,
in SQl 2005 only SQL_Latin1_General_CP850_BIN2
is supported. So, either you have to change all the databases using SQL_Latin1_General_CP850_BIN to SQL_Latin1_General_CP850_BIN2 according to note: 600027 or if this is not possible, you have to drop all the databases and re-install.
Cheers !!
Satya.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I see your error message talks about same 'SQL_Latin1_General_CP850_BIN2'.
Could there be some database previously created with different collation ? Check for each database.
Also make sure you have installed latest Service Pack for SQL server (note 62988). Minimum version required: 9.00.2047.
Cheers !!
Satya.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Are you sure that you have Microsoft SQL Server 2003 ? As far as I know there was SQL Server 2000 and then next release SQL Server 2005.
Cheers !!
Satya.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amr,
Please check installation manual. It refers ( I copied the section):
***********************************************************************
<b>Installing the Corrected MS SQL Server Collation</b>
When you install the MS SQL Server 2000 database for an SAP system, in the eld Collation Settings we recommend
that you select Binary order for use with the 850 (Multilingual) Character Set.
This means that all new databases and table columns will be created with this collation setting.
. Note
To view the default collation of MS SQL Server use the query:
select serverproperty('collation')
This query returns the default collation of the overall server. When you have selected code page cp850, it
returns: SQL_Latin1_General_CP850_BIN
Unfortunately this collation setting does not sort Unicode data as it is required by an SAP system. To solve this
problem, Microsoft provides a corrected collation as a hot x (QFE) for SQL Server. The QFE is included in the
hot x you installed during the standard installation for the MS SQL Server database. [page 11]
When you have installed the hot x, you have to run the executable INSTCOLL.EXE from SAP, as desribed
below. For more information on INSTCOLL.EXE, see SAP Note 600027.
Prerequisites
■ You have installed the MS SQL Server 2000 database. In the eld Collation Settings, you selected Binary order for
use with the 850 (Multilingual) Character Set.
■ If you run your SQL Server in a 32-bit system, you have installed SP3 and the latest hot x. For more
information, refer to SAP Notes 62988 and SAP Note 608651.
■ If you run your SQL Server in a 64-bit system, you have installed the latest hot x. For more information,
see SAP Note 608651.
. Note
Besides applying SP3 and/or the hot x you do not have to make any changes on the client side (SAP
application servers).
■ To obtain a correct collation order with MS SQL Server, you have to use the new collation for all new
installations of a Unicode or non-Unicode SAP system with the MS SQL Server database. New versions of
the SAPinst installation tool check for the new collation.
■ At present, there is no need to convert existing SAP system installations to the new collation.
■ A new SAP system using the new collation and an existing SAP system that is using the old collation cannot
run as two databases in the same MS SQL Server instance. If you want to install a new system on a database
server with an existing system you have to apply the new collation with INSTCOLL.EXE.
Procedure
1. Download the INSTCOLL.EXE le, which is attached as zip le to SAP Note 600027, and extract it to your
server.
2. Open a command prompt and change to the directory where you extracted the INSTCOLL.EXE le.
16 PUBLIC December 22, 2004
2 Standard Installation
2.1 Installation Process
3. Enter the following:
■ For a default instance enter: INSTCOLL.EXE
■ For a named instance enter: INSTCOLL.EXE -S<server>\<instance> (without any spaces after S)
The collation executable starts the SQL Server Service if it is not running already and runs several checks.
When you are asked to apply the new collation to all databases conrm with Yes.
When the conversion has nished it stops the SQL Server Service.
4. To verify whether the MS SQL Server is properly congured, run:
select serverproperty('collation')
. Caution
You have to run INSTCOLL.EXE only once to apply the new collation. To convert a single SAP database
to the new collation, see SAP Note 600027
**********************************************************************
Cheers !!
Satya.
PS: Points always encourage me to reply...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amr,
Can you check the startsap.log as well ? The 'profile' message is not any error.
Do you have any installation with System number '00' ?
Can you try to start SAP from outside of the SAPINST ? (e.g. manually via MMC) ?
Cheers !!
Satya.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have a new problem now.
I have started a new install of Netweaver 2004s Rapid Installer and I have SQL Server 2003 Enterprise Edition:
I get the follwoing pop-up window:
Required MS SQL Server collation for the SAP System installation is:
SQL_Latin1_General_CP850_BIN2
Your server uses collation: SQL_Latin1_General_CP850_BIN2
how can I change the collation? Do I need to re-install SQL Server?
Thanks,
Hi,
Can you please check of the Enqueue server is up and running....You can checj via /usr/sap/<SYS>/exe/run/enqt (pls check exact syntax with enqt -help)...
Also check if the services file entry for port definition is correct ?
A good idea would be to reboot the server and see if it works...
If not, can you please attach the detailed error message and your platform information?
Cheers !!
Satya.
PS: Pls reward points if answer is helpfull....Thx.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, for your input.
I followed what you told me. I still have the same problem.
It is taking a long time to start the instance J2E/SCS02.
Here is the error messages I am getting....
ERROR 2007-07-03 14:38:00.782
FCO-00104 Component with ID NW_Standalone_Java_Units_No_Engine|ind|ind|ind|ind should be used as toplevel component but there is no such component.
INFO 2007-07-03 14:38:15.297
Copied file 'C:/Program Files/sapinst_instdir/ERP/RI/INST/ADA/inifile.xml' to 'C:/Program Files/sapinst_instdir/ERP/RI/INST/ADA/inifile.19.xml'.
INFO 2007-07-03 14:38:15.360
Copied file 'C:/Program Files/sapinst_instdir/ERP/RI/INST/ADA/inifile.xml' to 'C:/Program Files/sapinst_instdir/ERP/RI/INST/ADA/inifile.20.xml'.
INFO 2007-07-03 14:38:18.610
Execute step Component W2K_ServicePack_Check|ind|ind|ind|indPreprocess of component |rapidinstaller|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
INFO 2007-07-03 14:38:35.985
Copied file 'C:/Program Files/sapinst_instdir/ERP/RI/INST/ADA/keydb.xml' to 'C:/Program Files/sapinst_instdir/ERP/RI/INST/ADA/keydb.9.xml'.
INFO 2007-07-03 14:38:36.219
Execute step startSCSInstance of component |rapidinstaller|ind|ind|ind|ind|0|0|NW_Java_OneHost|ind|ind|ind|ind|3|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0.
INFO 2007-07-03 14:38:36.547
Starting instance J2E/SCS02...
WARNING 2007-07-03 14:38:39.16
Connect to message server (w2rzyl3m01/3902) failed: NIECONN_REFUSED.
INFO[E] 2007-07-03 14:38:39.563
FSL-02077 File system export (share) Portaladmin does not exist.
INFO 2007-07-03 14:38:39.641
Creating file C:\Program Files\sapinst_instdir\ERP\RI\INST\ADA\stop_J2E_SCS02.log.
INFO 2007-07-03 14:38:39.672
Output of C:\usr\sap\J2E\SYS\exe\uc\NTI386\stopsap.exe name=J2E nr=02 SAPDIAHOST=w2rzyl3m01 is written to the logfile stop_J2E_SCS02.log.
WARNING 2007-07-03 14:38:43.750
Execution of the command "C:\usr\sap\J2E\SYS\exe\uc\NTI386\stopsap.exe name=J2E nr=02 SAPDIAHOST=w2rzyl3m01" finished with return code -1. Output: STOPSAP: execution of C:\usr\sap\J2E\SYS\exe\uc\NTI386\sapntwaitforhalt.exe name=J2E nr=02 SAPDIAHOST=w2rzyl3m01 3600 failedDetails are written to C:\Program Files\sapinst_instdir\ERP\RI\INST\ADA\stopsap.log
WARNING 2007-07-03 14:38:43.750
Could not stop instance 'SCS02' of SAP system J2E.
WARNING 2007-07-03 14:38:44.844
Connect to message server (w2rzyl3m01/3902) failed: NIECONN_REFUSED.
INFO[E] 2007-07-03 14:38:45.0
FSL-02077 File system export (share) Portaladmin does not exist.
INFO 2007-07-03 14:38:45.94
Creating file C:\Program Files\sapinst_instdir\ERP\RI\INST\ADA\start_J2E_SCS02.log.
INFO 2007-07-03 14:38:45.125
Output of C:\usr\sap\J2E\SYS\exe\uc\NTI386\startsap.exe name=J2E nr=02 SAPDIAHOST=w2rzyl3m01 is written to the logfile start_J2E_SCS02.log.
WARNING 2007-07-03 14:42:08.16
Execution of the command "C:\usr\sap\J2E\SYS\exe\uc\NTI386\startsap.exe name=J2E nr=02 SAPDIAHOST=w2rzyl3m01" finished with return code -1. Output: STARTSAP failedDetails are written to C:\Program Files\sapinst_instdir\ERP\RI\INST\ADA\startJ2E.log
WARNING 2007-07-03 14:42:09.47
Connect to message server (w2rzyl3m01/3902) failed: NIECONN_REFUSED.
INFO 2007-07-03 14:42:09.47
State of instance J2E/SCS02 changed from UNKNOWN to STOP.
WARNING 2007-07-03 14:42:17.141
Connect to message server (w2rzyl3m01/3902) failed: NIECONN_REFUSED.
WARNING 2007-07-03 14:42:47.110
Connect to message server (w2rzyl3m01/3902) failed: NIECONN_REFUSED.
WARNING 2007-07-03 14:43:17.0
Connect to message server (w2rzyl3m01/3902) failed: NIECONN_REFUSED.
WARNING 2007-07-03 14:43:46.969
Connect to message server (w2rzyl3m01/3902) failed: NIECONN_REFUSED.
ERROR 2007-07-03 14:43:46.969
CJS-30086 Instance J2E/SCS02 [STOP] did not start after 5:00 minutes. Giving up.
ERROR 2007-07-03 14:43:47.63
FCO-00011 The step startSCSInstance with step key |rapidinstaller|ind|ind|ind|ind|0|0|NW_Java_OneHost|ind|ind|ind|ind|3|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|startSCSInstance was executed with status ERROR .
Hi,
Can you check the message for missing file share :
INFO[E] 2007-07-03 14:38:45.0
FSL-02077 File system export (share) Portaladmin does not exist.
Also, please check the log stop_J2E_SCS02.log, start_J2E_SCS02.log for any additional error....the devloper trace files as well...
What is the message server port ? It should be defined on 3602.
Cheers !!
Satya
I checked the following file: stopsap.log:
SAPSRVKILL finished successfully on w2rzyl3m01_J2E_02
Error occured when waiting for halt on w2rzyl3m01_J2E_02.
C:\usr\sap\J2E\SYS\exe\uc\NTI386\sapntwaitforhalt.exe=>sapparam(1c): No Profile used.
running C:\usr\sap\J2E\SYS\exe\uc\NTI386\sapsrvkill.exe w2rzyl3m01_J2E_02
running C:\usr\sap\J2E\SYS\exe\uc\NTI386\sapntwaitforhalt.exe name=J2E nr=02 SAPDIAHOST=w2rzyl3m01 3600
How can I solve the problem with the profile?
Regards,
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
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.