ars_db was not created during the inst of the mobile repository server

[alexander_brocke]

Hi @ all,

During the instllation of the mrs on a seperate machine in our landscape, the ars_db database was not created.

We use Release 5.0 SP09, MSSQL Server 2000 SP4 Standard on Windows Server 2003 Standard SP2 on 32bit and Java version 1.4.2_08 (SDK and JRE!)

Does anybody know how to create it after the installation manually or is the creation of the DB possibly while using some specific options during the installation.

OR

Does anybody know WHY it was not created

[alexander_brocke · Accepted solution]

Hi Wolfhard,

Thanks for your quick answer.

When i try to install the database ars_db an error occurs:

12-->07.12.2007 09:10:54: Failed to copy database CAR file

Do you know how to handle this?

Thanks for your efforts in advance.

regards

Alexander

[Former Member · Accepted solution]

Hi,

this sounds strange because switchDB should work independent from an MSA/MRS installation, having been successfully or not.

Did you already check whether there is already an ars_db.dat or ars_db.car file located in some directory (temp or MSSQL2K)?

Regards,

Wolfhard

[alexander_brocke · Accepted solution]

Hi,

I guess the problem is that I'm running out of disk space: SwitchDB copies the ars_db file to "C:\Program Files\SAP\Mobile_Installation_logfiles", and on drive C: are only 1,18GB available. Also in the same directory the "ars_db.mdf" is created and it seems that it will be bigger than 1GB.

What size will the database normally have?

The instroot of SAP mobile on this machine is set to D:\Program Files\SAP\***. Is it possible to change the target of the copy, e.g. in the registry? On this drive are 250GB available..... I suppose this will be enough.

Thanks a lot,

regards

Alexander

[Former Member · Accepted solution]

Hi,

I like this kind of errors like "disk full"...;-)))

As you noticed the car file is copied in the directory mentioned below and extracted into a mdf file in same directory which has a similar size (both about 1 GB).

Afterwards it is copied to the data directory of the MSSQL2K inst (on 😧 ?!?) and finally attached to the DB using the stored procedure sp_attach_db (or sp_attach_single_file_db).

If it is not possible to change this inst directory within switchDB to 😧 you might try to unzip the car file using sapcar and continue using the stored proc mentioned above.

Regards,

Wolfhard

[alexander_brocke · Accepted solution]

Hi again.

I have now set up a new server only for the MRS with enough space on C:

I have now installed the MRS and after that i installed the ars_db manually by using switch_db. In the folder "C:ProgrammeSAPMobileARSUserManagement" are several sql-scripts. I'm absolutely new in using SQL Server: What do i have to do with them? Because of that a step-by-step - instruction would be very helpful.

By using "osql -E -i <Path-to-sql-script>" only returns with errors:

Ungültiger Objektname 'dbo.ARSUserAccount'.

Ungültiger Objektname 'ARSUserAccount'.

Thanks in advance for your efforts.

Alexander Brocke

[alexander_brocke · Accepted solution]

btw: By installing the ars_db with Switch_db i have checked the box "Set Compatibility for IDES" --> is this allright?

[Former Member · Accepted solution]

Hi,

I assume that the original problem (ARS_DB missing) when trying to install the MRS had the same reason as the problem when trying to install it directly?!?

Wasn't the MRS installation successfully this time? ARS_DB still missing?

If still missing then after installing ARS_DB manually using switchDB (compatibility option mentioned by you in the next post is only needed for restoring of IDES DB not for ARS_DB) only isql.bat needs to be executed - when did you encounter the mentioned error?

Probably you have run this script for the "master" DB instead of for ARS_DB because the user is unknown. So better open SQL Analyzer Tool (sa/<blank>), switch to DB ars_db and paste the scripts in the panel. Run with F5.

Regards,

Wolfhard

[alexander_brocke · Accepted solution]

Hi,

Yes, you understood me right: Within the new installation the ars_db was not created Maybe its a problem of SP09?

I have now tried again to create the ars_db, without the IDES compatibility. In the enterprise-manager of the SQL Server the db is visible, but switch_db says, after installaing, it has failed to attach ars_db to my server. What could this be? Any idea?

The SAP installation Guide says that normally the user "arsadmin" with no pwd is created during the installation of the mrs. But after installing the database on my own, while using "isql.bat -E" the only user i can see in the SQL Server enterprise manager is "ars_db". Btw: During the execution of sql-scripts, i can see in the logfiles that some errors has occured, such as "Objectname not found" or "doesn't exist".

Thanks for further help,

Alexander

[Former Member · Accepted solution]

Hi,

if the DB is visible within the enterprise manager then the DB should be attached properly...

As I can see the user ars_db is created & assigned by running script <ars_db_logins.sql>.

However script <UserManagementAfterDBRestore.sql> seems not working properly - did you already try with copying the content in query analyzer panel - see above?

Regards,

Wolfhard

[alexander_brocke · Accepted solution]

Hi,

Yes id did.... and it worked properly. But I'm not able to connect to the database using "SAP MAR Transport Configurator" by using DSN "ars_db" and Login: "arsadmin" and an empty pwd; Error: "Cannot load RepositoryID parameter"

These Mobile Application make me completely weird ))

Regards and thanks for your helpful advises,

Alexander

[Former Member · Accepted solution]

Hi,

did you also apply script <arsPrepare4Customer.sql>?

Anyway you should check in ars_systable whether the value for the 'RepositoryID' is set correctly -> see script.

Regards,

Wolfhard

PS: Getting weird when working with Mobile is quite normal, don't be afraid...;-)))

[alexander_brocke · Accepted solution]

Hi,

Wow, absolutely amazing..... the connection to the ars_db now works..... after a restart!

BUT

I'm not able to establish a connection to the CRM-Server

I have created a "Communication User" named "mrs" on client 800. By using the dedicated server option the following error occurs:

Connecting to "TA_TEST" ... failed!

Could not establish connection to "TA_TEST"

Details:

[-2147467260] Incomplete logon data.

By using the "load balancing server" option another option occurs:

Connecting to "TA_TEST" ... failed!

Could not establish connection to "TA_TEST"

Details:

[-2147467260] Connect to message server failed

Connect_PM MSHOST=nta04sap, R3NAME=C5I, GROUP=PUBLIC

LOCATION CPIC (TCP/IP) on local host

ERROR service 'sapmsC5I' unknown

TIME Thu Dec 13 10:45:02 2007

RELEASE 620

COMPONENT NI (network interface)

VERSION 36

RC -3

MODULE nixxi_r.c

LINE 2616

DETAIL NiIServToAddr

COUNTER 84

Do you know what to do? I'm so tired of MSA.....

Regards and thanks for your efforts.

Alexander

[Former Member · Accepted solution]

Hi,

this is based on a "normal" RFC call like SAPGUI is doing.

Is there a SAPGUI installed on this machine and if yes, is the connection working with this logon data you mentioned above?

Regards,

Wolfhard

[alexander_brocke · Accepted solution]

Hi,

OK, now i have installed the latest GUI, but now it is the fact, that a runtime error occurs when i open the tab "CRM Server Connection" in the MAR Transport Configurator:

"Cannot Create RFC Resource Dispenser", whatever that means.....

it sucks..... i have fixed an error and a new occurs..... i'm really getting angry by time

Thanks lot, you're real halp to me and much faster than the SAP-Support.... I'm very thankful!!!

Regards,

Alexander

[Former Member · Accepted solution]

Hi,

I am out of any ideas now...

Maybe note 904972 helps as it seems that for Win 2000 and maybe 2003 too there were issues regarding dcom connector.

Is the connection to CRM via SAPGUI with the logon data listed above possible now?

Regards,

Wolfhard

[alexander_brocke · Accepted solution]

Hi

In the installation Guide it is mentioned, that I should create a "Communication-User" Because of that you are not able to connect via GUI.

Altough, I installed a GUI and after that installation a new errer has occured:

RuntimError "-2147220999 (800401f9)":

Cannot Create RFC Resource Dispenser.

After uninstalling the GUI the error exists furthermore.

You are not the only one, who is out of any ideas. I have read some threads (not just in this forum) that SP09 is not working well and the authors of this threads recommend not to install it..... Did your ever hear about it?

kind regards and thanks a lot for your help.

Alexander

[Former Member · Accepted solution]

Hi,

I don't think this particular issue is related to SP09.

I have a 5.0 SP09 test environment and don't face this issue (TO was not configured so far).

Astonishingly I have now the same error on my 4.0 demo environment (also XP) even after registering all DLLs/OCX files RFC.DLL/.OCX in bin directory.

Checking the OSS for related notes and customer messages shows only very few entries i.e. this seems to be a more OS (dcom connector) related issue.

Therefore I would suggest to create an OSS message too.

Regards,

Wolfhard

[alexander_brocke · Accepted solution]

Hi Wolfhard,

I will now make a complete new installation of the MRS, without the SAP-GUI.... or must i install it?

btw: In the CRM-Server (TX smoeac) i get an error, that my com4abap is not configured right: (I guess you speak german, so i post the error-message to you 😞

Systemfehler: RFC-Destination AC-COM4ABAP und Programm com4abap.exe prüfen

Meldungsnr. SMOE_MESSAGE096

Diagnose

Die Administrationskonsole versucht, die TCP/IP-RFC-Verbindung 'AC-COM4ABAP' zu öffnen. Aufgrund eines Kommunikations- oder Systemfehlers ist das nicht möglich.

Vorgehen

Wählen Sie "Anzeige und Pflege von RFC-Destinationen" (Transaktion SM59). Unter den TCP/IP-Verbindungen sollte die Verbindung AC-COM4ABAP erscheinen.

Wenn diese Verbindung fehlt, lesen Sie den Abschnitt über das Ändern von Mitarbeitern in der Dokumentation zu Ihrer Administrationskonsole. Hier finden Sie die Informationen zur Pflege der Verbindung AC-COM4ABAP.

Wenn die Verbindung vorhanden ist, testen Sie sie. Wenn der Test nicht erfolgreich ist, lesen Sie die zuvor erwähnte Dokumentation.

Wenn der Test keine Fehler zurückliefert, müssen Sie die Funktionalität des Programms COM4ABAP auf der Kommunikationsstation testen, wo sie als Windows-Dienst installiert ist.

Überprüfen Sie, ob die Kommunikationsstation und das Programm COM4ABAP laufen. Wenn das der Fall ist, vergleichen Sie die aktuellen "SAP COM für ABAP"-Einstellungen mit den Installationseinstellungen wie in der zuvor erwähnten Dokumentation beschrieben.

Überprüfen Sie, ob die Datei CRYPTINGLib.xmlnd im "Type Repository Path" zu finden ist und ob "Host" und "Service" richtig konfiguriert sind. Diese Einstellungen werden alle im Programm COM4ABAP gepflegt.

But where is "CRYPTINGLib.xmlnd? I cannot find this file on any machine in my mobile landscape...

Did you ever hear about this? In Tx sm59, while making a connection-test for the com4abap-rfc-connection, everythings seems to be ok..... I cannot understand where the problem might be.

Thanks in advance for your helpful efforts.

Alexander

[Former Member · Accepted solution]

Hi,

no, for the MRS you don't need a SAPGUI installation. I only mentioned it because of being able to test the RFC connection based on a different way.

Regarding the 'AC-COM4ABAP' issue I would suggest to create a new thread as it is related to a new problem.

Anyway this is a quite well-known issue and is also covered by some OSS notes like 409602.

Normally the error occurs when trying to change the Mobile user's pwd in smoeac because it uses the encryption tools available on the comm.- station.

The problem might be the wrong destination definition in sm59 or the fact that the service mentioned above is not running.

Please note the the file's name is CRYPTINGLib.xml and not CRYPTINGLib.xmlnd...:-))

Regards,

Wolfhard

[alexander_brocke · Accepted solution]

Hi Wolfhard,

So, the CRYPTINGLib.xml must normally be on the CommStation in the installation target, right?..... But i cannot find such file on my CommStation.... There's just Interop.CRYPTINGLib.dll and CRYPTING.dll.....

regards,

Alexander

Edited by: Alexander Brocke on Dec 17, 2007 11:32 AM

[Former Member · Accepted solution]

Hi,

obviously the error message is out-of-date because for 5.0 the connection is named NET4ABAP instead of COM4ABAP...;-))

Was Tx smoeac working fine before you noticed the error message?

Did you already check whether the comm station is installed & configured properly?

Is qmtcnfg.exe running properly on the comm station?

Regards,

Wolfhard

[alexander_brocke · Accepted solution]

Hi Wolfhard.

The issue is now solved.... what a luck!

The failure was, that because of the naming change i had to create two tcp/ip connections in Tx sm59: One named AC-NET4ABAP and the other AC-COM4ABAP, but both with the same options: registered server program, same gatewayhost and gateway itself and also same programID: net4abap. However, now everything seems to work.... after my holidays i have to check whether the connection from the mobile client is working....

Thanks a lot for your helpful advises and efforts.

Merry Christmas and kind regards,

Alexander Brocke

[Former Member]

Hi,

you could import the ars_db car file (installation CD path Mobile_Client_Installation\databases\Latin1\ars_db) using SwitchDB.exe (C:\Program Files\SAP\Mobile\Bin.Net) and afterwards run isql.bat (same directory) for applying the sql scripts (database rights/user/logins).

Furthermore you need to check/create a proper ODBC setting for ARS_DB manually.

Probably you could have a problem with the shorttermlockserver which is already installed but maybe you try first...

Regards,

Wolfhard