Saprfc.ini component absent
Hi All,
when I did an installation check of BEX on my PC - I found out that saprfc.ini was absent from my bex installation. actually i was facing problem in selecting any filter in the query. it was throwing error Active X component missing , so i did the installation check .
Kindly can anyboby let me know can saprfc.ini file be the reason behind it . what is this file saprfc.ini and what for this is used.
Regards,
Dola
Hi Dola..
Please find the below links taken from help.sap.com....may be these below links can helps you...
http://help.sap.com/saphelp_nw04/helpdata/en/22/042a3e488911d189490000e829fbbd/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/22/04294f488911d189490000e829fbbd/content.htm
Regards
Sudheer
Similar Messages
-
i have a solaris box here running ecc. Would I have a saprfc.ini file on this server ? I do not connect this box to any non SAP systems, it just connects to other SAP systems. I thought that saprfc.ini is present only on the client side when connecting non SAP systems to a SAP system through RFC. So, I dont believe there should be a saprfc.ini file on my server in this case. If i am wrong, can you please advise as to where can I find this file ?
thanksHi,
Please don't ask same question on different threads, close anyone.
saprfc.ini file
Regards,
Kiron. -
i have a solaris box here running ecc. Would I have a saprfc.ini file on this server ? I do not connect this box to any non SAP systems, it just connects to other SAP systems. I thought that saprfc.ini is present only on the client side when connecting non SAP systems to a SAP system through RFC. So, I dont believe there should be a saprfc.ini file on my server in this case. If i am wrong, can you please advise as to where can I find this file ?
thanksHi,
The file "saprfc.ini" contains a configuration section for the destination that is used for setting up connection to SAP system.
This file is used as bridge for RFC communication within SAP system itself or between SAP and Non-SAP systems for CCMS Monitoring/agent setup/ IDoc & RFC Adapter configuration in XI, SNC setup, etc..etc.
Open saprfc.ini , you will see such configuration parameters like
DEST=CCMS
TYPE=R
PROGID=<local_host>.sapccm4x.00
GWSERV=sapgw00
GWHOST=<loca_gw host> or <remote_gw host>
RFC_TRACE=0
More information you can get on this link The [SAPRFC.INI File|http://help.sap.com/saphelp_nw04/helpdata/en/22/042a31488911d189490000e829fbbd/content.htm] and [File saprfc.ini|http://help.sap.com/saphelp_apo/helpdata/en/c6/89403f449311d1893e0000e8323c4f/content.htm].
Regards,
Bhavik G. Shroff -
RFC Connection error - Invalid length. Check parameters.
Hi Forum, Good Morning!
My ABAP Program will run in BACK Ground Job Processing(SM37) to download data to Presentation server( Local PC Directory). So I have created a RFC destination type TCP/IP to use 'RFC_REMOTE_FILE' function module in my ABAP Program.
When I am trying to test RFC connection It is giving following error.
ERROR Invalid length. Check parameters
LOCATION SAP- Server dsapp05_R3D_10 on host dsapp05 (wp 2)
COMPONENT CPIC
COUNTER 14
MODULE
LINE
RETURN CODE 240
SUBRC 0
RELEASE 640
TIME Mon Dec 11 10:08:05 2006
I did following procedure before I test RFC destination..
I have created RFC Destination : BJRFC
Technical Settings: Selected Registered Server Program radio button
Program ID: BJACCESS
Gateway host : 172.22.149.199
gateway Service: sapdp10
In my local machine Copied SAPRFC.INI file from the TEXT folder to the BIN Folder.
Then open the SAPRFC.INI file in BIN folder and Register a RFC server program at a SAP Gateway.
DEST=R3D_R
TYPE=R
PROGID=BJACCESS.rfcexec
GWHOST=172.22.149.199
GWSERV=sapdp10
RFC_TRACE=0
DEST=R3D_R
TYPE=R
PROGID=BJACCESS.trfcexec
GWHOST=172.22.149.199
GWSERV=sapdp10
RFC_TRACE=0
Then entered below command in dos prompt.
C:\Program Files\SAP\FrontEnd\SAPgui\rfcsdk\bin>rfcexec -aBJACCESS 172.22.149.199 xsapdp10.
so how do i proceed in this kind of case.
any help please.
Thanks in advance.Hi,
Just you check whether your program is registered or not.
If it is registered then you can find in SMGW transaction and go to
GOTO - Logged on clients
in that you will be able to see your program name if it registers succesfully.
you have typed rfcexec -aBJACCESS 172.22.149.199 xsapdp10
in this way.
In this you have misseg 'g' in front of your sap ip.
Thanks&Regards
Rajehs Balusu -
Error 'Program not registered' while testing RFC
Hi
I have created a RFC with type T. When I am testing the same through SM59, I am getting error:
Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: program <program name>not registered
Error Details LOCATION: SAP-Gateway on host xxxxxx / sapgw01
Error Details DETAIL: TP <program name> not registered
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 6268
Error Details MODULE: gwr3cpic.c
Error Details LINE: 1694
Error Details RETURN CODE: 679
Error Details SUBRC: 0
Error Details RELEASE: 700
Error Details TIME: Tue Jan 27 00:56:55 2009
Error Details VERSION: 2
Can anybody help me in this?
Thanks in advanceSomething helpful related to this
The program in the above error should be registered in the gateway for this connection test to complete successfully. The server program rfcexec is responsible for its registration on the gateway.
To register the program login into the OS level as sudo su - <sid>adm and execute the following command.
rfcexec u2013g<program id> -a<gateway host name> -x<gateway service>
rfcexec is the server program name, the <program id> can be obtained from SM59, it is case sensitive and should match with the entry in SM59. The <gateway host name> and <gateway service> can be obtained from the transaction SMGW. When this command is executed it goes to a hanging loop.
The connection will fail once this command is terminated or the user executing this command logs off
To avoid this, instead of using the above mentioned command an entry should be made in the file saprfc.ini
To do this, execute the following command
sudo su - <sid>adm
rfcexec u2013D<destination name>
<destination name> is the RFC destination name in SM59
So now we are done with registering the server program, but how do we check it is registered, once a server program is registered it is displayed in the Logged on clients in SMGW.
In transaction SMGW choose GOTO-> Logged on clients. There should be an entry for the server program in the screen that is displayed with system type Registered_TP (which indicates that the program is registered) -
Error 'Program not registered' while testing RFC - SRM to MDM / TCP/IP conn
Hello All,
While testing RFC connection in SRM, we are getting this error. This connection between SRM to MDM. Any inputs will be highly appreciated.
Error Details LOCATION: SAP-Gateway on host <hostname> / sapgw<instance no>
our server OS : windows 2008 server
We are getting error while doing connection test in SRM.
This is sm59 connection (TCP/IP ) connection.
Connection Type: T / RFC destination Name: MDM_API_CATALOG
Registered server program: hostname.MDS
I checked smgw transaction ..Logged on clients...Program id is not showing. Any hint will be helpful.
I Checked this MDM setup also.
MDS setup
In mdm server go to folder F:\usr\sap\DM1\MDS00\config
Open MDM.ini file in notepad
Add the below 2 entries.
SAP RFC Gateways= GWHOST=XXXX.hostnamexxx.xxx GWSERV=sapgw00
Trusted SAP Systems= XXD
This will enable gateway connection between SRM and MDM and will enable trusted connection.
For trusted connections to work, we created a service user called SRM_MDM_API with SAP_ALL in SRM and also created the same user in MDM with Default role.
Error message:
Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: program XXXXXXXXPRD.MDS not registered
Error Details LOCATION: SAP-Gateway on host XXXXXXXXprd.xx.xxxxxxhostname.xxx / sapgw00
Error Details DETAIL: TP XXXXXXXXPRD.MDS not registered
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 77326
Error Details MODULE: gwr3cpic.c
Error Details LINE: 1778
Error Details RETURN CODE: 679
Error Details SUBRC: 0
Error Details RELEASE: 700
Error Details TIME:
Error Details VERSION: 2
Procedure Tried
1) This procedure is for Linux OS - Similarly we tried in Windows OS ( If any procedure is wrong also, Please correct us)
To register the program login into the OS level as sudo su u2013 <sid>adm and execute the following command.
rfcexec u2013g<program id> -a<gateway host name> -x<gateway service>
rfcexec is the server program name, the <program id> can be obtained from SM59, it is case sensitive and should match with the entry in SM59. The <gateway host name> and <gateway service> can be obtained from the transaction SMGW. When this command is executed it goes to a hanging loop.
The connection will fail once this command is terminated or the user executing this command logs off
2)
To avoid this, instead of using the above mentioned command an entry should be made in the file saprfc.ini
To do this, execute the following command
sudo su u2013 <sid>adm
rfcexec u2013D<destination name>
<destination name> is the RFC destination name in SM59
In order to do above step 2, we could not find saprfc.ini in windows 2008 server. Please let us know path where it will be usually?
3) Already checked the notes sapnote_0000684841
I know that it is generic error..This is happening to specific one of system only.
Thanks
Edited by: saptest2011 on May 20, 2011 5:36 PMHello SM,
Thanks for your quick reply.
Thanks for sharing link for document ie Configure the MDM Administration_cockpit. It is helpful. I read that document.
But still issue remain there.
The same RFC connection works between SRM sandbox to MDM sandbox.
Only issue with SRM Prod to MDM Prod (newly built system)
difference between MDM Prod and MDM sandbox.
MDM Prod runs: Windows server 2008 OS
MDM Sandbox runs: Windows server 2003 OS
Landscape: PI7.1, MDM 7.1 and SRM 5.5, SRM-MDM Catalog 3.0
Even i did os01 tcode ping test using host name (specific IP address) from SRM prod to MDM prod, it is fine.
Thanks a lot for your help.
I checked these notes also
Note 353597 - Registering a server program
Note 44844 - No connection to registered RFC program
Note: in smgw tcode in SRM system, the required program id is not showing in logged on clients
Thanks
Edited by: saptest2011 on May 23, 2011 5:00 PM
Edited by: saptest2011 on May 23, 2011 5:39 PM -
Help with error program not registered CPI-C error CM_ALLOCATE_FAILURE_RETR
I have the following connection error in SM59 ...
Connection error program ZCCCOM_NZ_PMH01 not registered / CPI-C error CM_ALLOCATE_FAILURE_RETRY.
I have deleted and re-registered the program but still no connection. Any ideas as to what/where I am going wrong would be fantastic!!
RFC Destin = CCCOM
Type = T
Gateway Host = ntchsapqas
Gateway service = sapgw00
ERROR program ZCCCOM_NZ_PMH01 not registered
LOCATION SAP-Gateway on host ntchsapqas / sapgw00
DETAIL TP ZCCCOM_NZ_PMH01 not registered
COMPONENT SAP-Gateway
COUNTER 19364
MODULE gwr3cpic.c
LINE 1593
RETURN CODE 679
SUBRC 0
RELEASE 46D
TIME Tue Jun 10 14:47:28 2008
VERSION 2Something helpful related to this
The program in the above error should be registered in the gateway for this connection test to complete successfully. The server program rfcexec is responsible for its registration on the gateway.
To register the program login into the OS level as sudo su - <sid>adm and execute the following command.
rfcexec u2013g<program id> -a<gateway host name> -x<gateway service>
rfcexec is the server program name, the <program id> can be obtained from SM59, it is case sensitive and should match with the entry in SM59. The <gateway host name> and <gateway service> can be obtained from the transaction SMGW. When this command is executed it goes to a hanging loop.
The connection will fail once this command is terminated or the user executing this command logs off
To avoid this, instead of using the above mentioned command an entry should be made in the file saprfc.ini
To do this, execute the following command
sudo su - <sid>adm
rfcexec u2013D<destination name>
<destination name> is the RFC destination name in SM59
So now we are done with registering the server program, but how do we check it is registered, once a server program is registered it is displayed in the Logged on clients in SMGW.
In transaction SMGW choose GOTO-> Logged on clients. There should be an entry for the server program in the screen that is displayed with system type Registered_TP (which indicates that the program is registered) -
Error while running sapccmsr.exe on Netweaver Trial
Hi there,
I've installed Netweaver Trial on my laptop, and I'm trying to run 'sapccmsr.exe -R' from the command to register the CCMS monitoring agent.
It almost works, but then comes up with the following error:
"After entering the RFC logon info for the user, the password
will be stored here on this machine in a Secure Storage.
client [000] :
user [CSMREG] : sap*
language [EN] :
hostname of NSP message server [localhost] :
use Load Balancing [n]/y ? : n
hostname of application server [localhost] :
system number (00 - 98) [00] :
[optional] route string :
trace level [0] :
please enter password for [NSP:000:sap*]: *******
Try to connect ...
INFO: Updated saprfc.ini in agent work directory C:\saploc\PRFCLOG\sapccmsr
ERROR: Registration failed: Can't get version of NSP. RfcRc = 2, C_CALL_FAILED
RFC Error Info for SALS_MS_GET_LOCAL_MS_INFO
message:
status: EXCEPTION C_CALL_FAILED RAISED
intstat:
INFO: dsr: dsrlib unloaded.
EXITING with code 1"
any help much appreciated, I'm a SAP newbie !
TIA.
Stuart.Hi,
I have exactly the same problem.
sapccmsr -R -j2ee pf=<dir>
client [000] :
user [CSMREG] :
language [EN] :
hostname of PIT message server :
use Load Balancing [n]/y ? :
hostname of application server :
system number (00 - 98) :
[optional] route string :
trace level [0] :
please enter password for [PIT:000:CSMREG]:
Try to connect ...
INFO: Updated saprfc.ini in agent work directory /usr/sap/ccms/<SID>_<SN>/sapccmsr
ERROR: Registration failed: Can't get version of PIT. RfcRc = 2, C_CALL_FAILED
RFC Error Info for SALS_MS_GET_LOCAL_MS_INFO
message:
status: EXCEPTION C_CALL_FAILED RAISED
intstat:
INFO: dsr: dsrlib unloaded.
I have tried to register it via visual admin but the same error appeared.
OS: AIX
DB: oracle 10.2.0.4.0
SAP component: PI7 (SAP NetWeaver 2004s)
Any help?
Thanks in advance
Edited by: Jan Hinka on Jul 2, 2009 6:46 PM -
MaxDB install failure on Win 2003 Server
Win 2003 Server
MaxDB v 7.6.05.09
HP Proliant G5
Good morning,
We've got a problem with a MaxDB install on a fresh Win 2003 server.
- The first install process and the demo database worked fine
- We tried to create a new database instance and it hung. As nothing was working as expected we decided to uninstall maxdb and all its component and to re-start from a clean process. That's were things are becoming weird :
- The first time the setup assistant hung when installing the kernel
- The secund time the setup assistant hung when installing the demo database
- Every following test hangs when installing the kernel
We tried to do a clean uninstall MaxDB, to watch which registry keys we should restore... but nothings worked as expected.
We found a link at this address describing the same problem but it doesn't provide us anything to solve our problem.
Here is our log file :
INSTALLER_INFO: Version = 7.6.05 Build 009-123-191-997
INSTALLER_INFO: Changelist = 191997
INSTALLER_INFO: MakeId = 323091
INSTALLER_INFO: Type = kit
SYS_INFO: Host name = SRVBATINOR
SYS_INFO: System = Windows
SYS_INFO: Architecture = I386
SYS_INFO: Version = NT 5.2
SYS_INFO: Subversion = Service Pack 2
MSG: collector found 12 archives
MSG: debug package SDBBAS.SDB is valid
MSG: debug package SDBKRN.SDB is valid
MSG: debug package SDBUTL.SDB is valid
MSG: initializing package "Base"
MSG: calling preinstall...
MSG: service "sql6" in "C:/WINDOWS/system32/drivers/etc/services" found
MSG: service "sapdbni72" in "C:/WINDOWS/system32/drivers/etc/services" found
MSG: Template set indep data path to "c:/documents and settings/all users/application data/sdb/data"
MSG: Template set indep programs path to "c:/program files/sdb/programs"
ACTION: make directory "c:/documents and settings/all users/application data/sdb/data/config" mode "775"
ACTION: make directory "c:/documents and settings/all users/application data/sdb/data/config/install" mode "775"
MSG: InstallRegistry: space check ok: 41676028 kb on C: (51203980 kb total) available
MSG: install registry successfully locked
MSG: InstallRegistry::Log: space check ok: 41676028 kb on C: (51203980 kb total) available
MSG: writing 0 packages
MSG: net install registry size = 63 bytes
MSG: wrote install registry (125 bytes)
MSG: InstallRegistry: reserved 1024 kb disk space
getRelease():C:/Program Files/SDB/MAXDB1/pgm/kernel.exe not found
MSG: migrate server installation data for INSTROOT "c:/program files/sdb/maxdb1"
MSG: initializing package "Server Utilities"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "Database Kernel"
MSG: calling preinstall...
MSG: Template or instance update set dependent path to c:/program files/sdb/maxdb1
Msg: checking update of package "Database Kernel" in C:Program Filessdbmaxdb1
MSG: installed package is flaged as invalid => skipping update check
MSG: initializing package "Redist Python"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "Loader"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "ODBC"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "Messages"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "JDBC"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "Synchronization Manager"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "SQLDBC"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "MaxDB PHP Driver"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "DB Analyzer"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
ACTION: make directory "C:/Program Files/sdb" mode "555"
ACTION: make directory "C:/Program Files/sdb/programs" mode "555"
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBBAS.TGZ"
MSG: running postprepare of package Base
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBUTL.TGZ"
ACTION: make directory "C:/Program Files/sdb/MAXDB1" mode "555"
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBKRN.TGZ"
MSG: running postprepare of package Database Kernel
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBRDPY.TGZ"
MSG: running postprepare of package Redist Python
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBLD.TGZ"
MSG: running postprepare of package Loader
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBODBC.TGZ"
MSG: running postprepare of package ODBC
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBMSG.TGZ"
MSG: running postprepare of package Messages
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBJDBC.TGZ"
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SYNCMAN.TGZ"
MSG: running postprepare of package Synchronization Manager
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBC.TGZ"
MSG: running postprepare of package Database Connectivity
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBPHP.TGZ"
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBANA.TGZ"
MSG: running postprepare of package DB Analyzer
MSG: space check ok: 41672820 kb on (51203980 kb total) available
MSG: packagedata of package Base changed
MSG: writing 2 packages
MSG: net install registry size = 4113 bytes
MSG: wrote install registry (5162 bytes)
STDOUT: start real extraction of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBBAS.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:58:53 bin/
STDOUT: extracting: -rwxr-xr-x 802816 2008-08-15 21:53:13 bin/dbmevtdisp.exe
STDOUT: extracting: -rwxr-xr-x 294912 2008-08-15 21:49:43 bin/protconv.exe
STDOUT: extracting: -rwxr-xr-x 151552 2008-08-15 20:11:07 bin/sdbconfig.exe
STDOUT: extracting: -rwxr-xr-x 7168 2008-08-16 00:57:39 bin/SDBINST.EXE
STDOUT: extracting: -rwxr-xr-x 6144 2008-08-16 00:57:40 bin/sdbpack.exe
STDOUT: extracting: -rwxr-xr-x 7680 2008-08-16 00:57:40 bin/sdbreg.exe
STDOUT: extracting: -rwxr-xr-x 7680 2008-08-16 00:57:40 bin/sdbregview.exe
STDOUT: extracting: -rwxr-xr-x 13824 2008-08-16 00:57:39 bin/SDBSETUP.EXE
STDOUT: extracting: -rwxr-xr-x 7680 2008-08-16 00:57:39 bin/sdbuninst.exe
STDOUT: extracting: -rwxr-xr-x 7168 2008-08-16 00:57:40 bin/sdbverify.exe
STDOUT: extracting: -rwxr-xr-x 1257472 2008-08-16 00:35:29 bin/sqlcli.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xsysrc.exe
STDOUT: extracting: -rwxr-xr-x 323584 2008-08-15 20:24:45 bin/xtcpupd.exe
STDOUT: extracting: -rwxr-xr-x 294912 2008-08-15 19:55:07 bin/xuser.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_ping.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:58:53 install/
STDOUT: extracting: -rwxr-xr-x 192512 2008-08-16 00:54:07 install/Grid.dll
STDOUT: extracting: -rwxr-xr-x 757760 2008-08-16 00:41:09 install/perl58.dll
STDOUT: extracting: -rw-rr 117099 2008-08-16 00:57:38 install/RESOURCES.TGZ
STDOUT: extracting: -rw-rr 465022 2008-08-16 00:57:38 install/SDBINST.TGZ
STDOUT: extracting: -rwxr-xr-x 421888 2008-08-16 00:57:27 install/sdbrun.dll
STDOUT: extracting: -rwxr-xr-x 1245184 2008-08-16 00:56:33 install/Wx.dll
STDOUT: extracting: -rwxr-xr-x 2265088 2008-08-16 00:53:37 install/wxmsw24.dll
STDOUT: extracting: -rw-rr 64327 2008-08-16 00:57:42 install/WXPERL.TGZ
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:58:54 pgm/
STDOUT: extracting: -rwxr-xr-x 2101248 2008-08-15 21:49:55 pgm/dbmcli.exe
STDOUT: extracting: -rwxr-xr-x 2101248 2008-08-15 21:49:55 pgm/dbmcli_HelpInst.exe
STDOUT: extracting: -rwxr-xr-x 217088 2008-08-15 22:11:27 pgm/regupd.exe
STDOUT: extracting: -rwxr-xr-x 307200 2008-08-15 20:25:09 pgm/sqlping.exe
STDOUT: extracting: -rwxr-xr-x 49152 2008-08-15 19:46:03 pgm/sqltcp.dll
STDOUT: extracting: -rwxr-xr-x 49152 2008-08-15 19:46:03 pgm/sqltcp1.dll
STDOUT: extracting: -rwxr-xr-x 49152 2008-08-15 19:46:05 pgm/sqltcp2.dll
STDOUT: extracting: -rwxr-xr-x 45056 2008-08-15 19:46:07 pgm/sqltcpn.dll
STDOUT: extracting: -rwxr-xr-x 281952 2008-08-16 00:58:28 pgm/sqluser72.dll
STDOUT: extracting: -rwxr-xr-x 372672 2008-08-16 00:58:32 pgm/sqluser73.dll
STDOUT: extracting: -rwxr-xr-x 393216 2008-08-16 00:58:35 pgm/sqluser74.dll
STDOUT: extracting: -rwxr-xr-x 438272 2008-08-16 00:58:38 pgm/sqluser74n.dll
STDOUT: extracting: -rwxr-xr-x 524288 2008-08-16 00:15:41 pgm/sqluser76.dll
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:01 Support/
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:02 Support/Mapfiles/
STDOUT: extracting: -rw-rr 3023564 2008-08-15 21:49:54 Support/Mapfiles/dbmcli.map
STDOUT: extracting: -rw-rr 1265024 2008-08-15 21:53:13 Support/Mapfiles/dbmevtdisp.map
STDOUT: extracting: -rw-rr 115063 2008-08-15 20:28:06 Support/Mapfiles/sqltcp.map
STDOUT: extracting: -rw-rr 115066 2008-08-15 20:28:07 Support/Mapfiles/sqltcp1.map
STDOUT: extracting: -rw-rr 115148 2008-08-15 20:28:09 Support/Mapfiles/sqltcp2.map
STDOUT: extracting: -rw-rr 108889 2008-08-15 20:28:13 Support/Mapfiles/sqltcpn.map
STDOUT: extracting: -rw-rr 125887 2008-08-16 00:58:30 Support/Mapfiles/sqluser72.map
STDOUT: extracting: -rw-rr 147341 2008-08-16 00:58:33 Support/Mapfiles/sqluser73.map
STDOUT: extracting: -rw-rr 258131 2008-08-16 00:58:36 Support/Mapfiles/sqluser74.map
STDOUT: extracting: -rw-rr 739428 2008-08-16 00:58:39 Support/Mapfiles/sqluser74n.map
STDOUT: extracting: -rw-rr 916710 2008-08-16 00:15:41 Support/Mapfiles/sqluser76.map
STDOUT: extracting: -rw-rr 593052 2008-08-15 20:24:45 Support/Mapfiles/xtcpupd.map
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:04 symbols/
STDOUT: extracting: -rw-rr 8252416 2008-08-15 21:49:54 symbols/dbmcli.pdb
STDOUT: extracting: -rw-rr 3836928 2008-08-15 21:53:13 symbols/dbmevtdisp.pdb
STDOUT: extracting: -rw-rr 289792 2008-08-15 20:28:06 symbols/sqltcp.pdb
STDOUT: extracting: -rw-rr 289792 2008-08-15 20:28:07 symbols/sqltcp1.pdb
STDOUT: extracting: -rw-rr 289792 2008-08-15 20:28:09 symbols/sqltcp2.pdb
STDOUT: extracting: -rw-rr 281600 2008-08-15 20:28:13 symbols/sqltcpn.pdb
STDOUT: extracting: -rw-rr 1887232 2008-08-16 00:58:37 symbols/sqluser74.pdb
STDOUT: extracting: -rw-rr 2059264 2008-08-16 00:58:40 symbols/sqluser74n.pdb
STDOUT: extracting: -rw-rr 4705280 2008-08-15 20:24:44 symbols/xtcpupd.pdb
STDOUT: checking unpacked archive... MSG: check file "Support/Mapfiles/sqluser72.map": ok
MSG: check file "symbols/sqltcpn.pdb": ok
MSG: check file "pgm/dbmcli_HelpInst.exe": ok
MSG: check file "bin/x_ping.exe": ok
MSG: check file "Support/Mapfiles/sqluser74.map": ok
MSG: check file "bin/SDBINST.EXE": ok
MSG: check file "install/SDBINST.TGZ": ok
MSG: check file "pgm/sqluser74.dll": ok
MSG: check file "symbols/dbmcli.pdb": ok
MSG: check file "symbols/sqltcp1.pdb": ok
MSG: check file "bin/SDBSETUP.EXE": ok
MSG: check file "pgm/sqluser74n.dll": ok
MSG: check file "Support/Mapfiles/sqltcp.map": ok
MSG: check file "bin/protconv.exe": ok
MSG: check file "symbols/sqltcp.pdb": ok
MSG: check file "Support/Mapfiles/sqltcpn.map": ok
MSG: check file "install/WXPERL.TGZ": ok
MSG: check file "install/wxmsw24.dll": ok
MSG: check file "install/sdbrun.dll": ok
MSG: check file "bin/xuser.exe": ok
MSG: check file "pgm/sqluser73.dll": ok
MSG: check file "pgm/sqluser76.dll": ok
MSG: check file "symbols/xtcpupd.pdb": ok
MSG: check file "pgm/sqltcp1.dll": ok
MSG: check file "Support/Mapfiles/sqluser74n.map": ok
MSG: check file "pgm/dbmcli.exe": ok
MSG: check file "pgm/sqltcp.dll": ok
MSG: check file "install/RESOURCES.TGZ": ok
MSG: check file "Support/Mapfiles/dbmevtdisp.map": ok
MSG: check file "Support/Mapfiles/sqluser73.map": ok
MSG: check file "Support/Mapfiles/xtcpupd.map": ok
MSG: check file "bin/sdbverify.exe": ok
MSG: check file "bin/xsysrc.exe": ok
MSG: check file "Support/Mapfiles/sqltcp1.map": ok
MSG: check file "Support/Mapfiles/sqltcp2.map": ok
MSG: check file "install/perl58.dll": ok
MSG: check file "Support/Mapfiles/sqluser76.map": ok
MSG: check file "bin/sdbuninst.exe": ok
MSG: check file "pgm/regupd.exe": ok
MSG: check file "symbols/dbmevtdisp.pdb": ok
MSG: check file "pgm/sqlping.exe": ok
MSG: check file "bin/sdbpack.exe": ok
MSG: check file "symbols/sqltcp2.pdb": ok
MSG: check file "pgm/sqltcpn.dll": ok
MSG: check file "pgm/sqluser72.dll": ok
MSG: check file "symbols/sqluser74.pdb": ok
MSG: check file "Support/Mapfiles/dbmcli.map": ok
MSG: check file "pgm/sqltcp2.dll": ok
MSG: check file "bin/dbmevtdisp.exe": ok
MSG: check file "bin/sdbregview.exe": ok
MSG: check file "bin/xtcpupd.exe": ok
MSG: check file "install/Grid.dll": ok
MSG: check file "bin/sdbconfig.exe": ok
MSG: check file "symbols/sqluser74n.pdb": ok
MSG: check file "bin/sdbreg.exe": ok
MSG: check file "install/Wx.dll": ok
MSG: check file "bin/sqlcli.exe": ok
STDOUT: ok
STDOUT: checking system libraries...MSG: update test sytem file "C:/WINDOWS/system32/mfc70.dll"
MSG: system file "mfc70.dll" inside archive has version 7.00.9466.0
MSG: installed system file "mfc70.dll" is up to date (version 7.00.9466.0)
MSG: update test sytem file "C:/WINDOWS/system32/mfc70u.dll"
MSG: system file "mfc70u.dll" inside archive has version 7.00.9466.0
MSG: installed system file "mfc70u.dll" is up to date (version 7.00.9466.0)
MSG: update test sytem file "C:/WINDOWS/system32/mfc71.dll"
MSG: system file "mfc71.dll" inside archive has version 7.10.3077.0
MSG: installed system file "mfc71.dll" is up to date (version 7.10.3077.0)
MSG: update test sytem file "C:/WINDOWS/system32/mfc71u.dll"
MSG: system file "mfc71u.dll" inside archive has version 7.10.3077.0
MSG: installed system file "mfc71u.dll" is up to date (version 7.10.3077.0)
MSG: update test sytem file "C:/WINDOWS/system32/msvcr70.dll"
MSG: system file "msvcr70.dll" inside archive has version 7.00.9466.0
MSG: installed system file "msvcr70.dll" is up to date (version 7.00.9466.0)
MSG: update test sytem file "C:/WINDOWS/system32/msvcr71.dll"
MSG: system file "msvcr71.dll" inside archive has version 7.10.3052.4
MSG: installed system file "msvcr71.dll" is up to date (version 7.10.3052.4)
STDOUT: ok
SYS: "C:Program Filessdbprograms insdbconfig.exe" "IndepPrograms=C:Program Filessdbprograms"
SYS: "C:Program Filessdbprograms insdbconfig.exe" "IndepData=C:Documents and SettingsAll UsersApplication Datasdbdata"
STDOUT: system path updated successfully
STDOUT: please reboot your system after installation to take effect changes
MSG: registry subkey "SOFTWAREMicrosoft" exist
MSG: registry subkey "SOFTWAREMicrosoftWindows" exist
MSG: registry subkey "SOFTWAREMicrosoftWindowsCurrentVersion" exist
MSG: registry subkey "SOFTWAREMicrosoftWindowsCurrentVersionUninstall" exist
MSG: created registry subkey "SOFTWAREMicrosoftWindowsCurrentVersionUninstallSAP DB (ALL)" successfully
ACTION: make directory "C:/Documents and Settings/All Users/Menu DÈmarrer/Programmes/MaxDB" mode "775"
ACTION: make directory "C:/Documents and Settings/All Users/Menu DÈmarrer/Programmes/MaxDB/Command Line Tools" mode "775"
MSG: start menu shortcuts created
MSG: packagedata of package Base changed
MSG: writing 2 packages
MSG: net install registry size = 32157 bytes
MSG: wrote install registry (36384 bytes)
MSG: packagedata of package Server Utilities changed
MSG: writing 3 packages
MSG: net install registry size = 32773 bytes
MSG: wrote install registry (37403 bytes)
STDOUT: start real extraction of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBUTL.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:53 bin/
STDOUT: extracting: -rwxr-xr-x 65536 2008-08-15 21:52:21 bin/sdbinfo.exe
STDOUT: extracting: -rwxr-xr-x 356352 2008-08-16 00:05:31 bin/sqlrun.dll
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/sysmon.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xbackup.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xinstinfo.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xpu.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_analys.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_cons.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_server.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_show.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_start.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_stop.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_wiz.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_wizard.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_wizstop.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_wiztrc.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:53 env/
STDOUT: extracting: -rw-rr 122 2008-08-15 22:02:13 env/serv.use
STDOUT: extracting: -rw-rr 245 2008-08-15 22:02:13 env/xstart.use
STDOUT: extracting: -rw-rr 542 2008-08-15 22:02:13 env/xstop.use
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:53 etc/
STDOUT: extracting: -rw-rr 207 2008-08-15 19:42:23 etc/VERSIONS
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:53 pgm/
STDOUT: extracting: -rwxr-xr-x 483328 2008-08-15 20:11:45 pgm/serv.exe
STDOUT: extracting: -rwxr-xr-x 307200 2008-08-15 20:11:09 pgm/show.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:54 Support/
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:54 Support/Mapfiles/
STDOUT: extracting: -rw-rr 839796 2008-08-15 20:11:44 Support/Mapfiles/serv.map
STDOUT: extracting: -rw-rr 540173 2008-08-15 20:11:08 Support/Mapfiles/show.map
STDOUT: extracting: -rw-rr 615852 2008-08-16 00:05:31 Support/Mapfiles/sqlrun.map
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:55 symbols/
STDOUT: extracting: -rw-rr 2575360 2008-08-15 20:11:44 symbols/serv.pdb
STDOUT: extracting: -rw-rr 2051072 2008-08-15 20:11:08 symbols/show.pdb
STDOUT: extracting: -rw-rr 2075648 2008-08-16 00:05:31 symbols/sqlrun.pdb
STDOUT: checking unpacked archive... MSG: check file "bin/x_wizstop.exe": ok
MSG: check file "bin/x_analys.exe": ok
MSG: check file "bin/x_cons.exe": ok
MSG: check file "bin/xpu.exe": ok
MSG: check file "bin/sysmon.exe": ok
MSG: check file "bin/x_start.exe": ok
MSG: check file "pgm/serv.exe": ok
MSG: check file "env/xstart.use": ok
MSG: check file "bin/x_server.exe": ok
MSG: check file "bin/sqlrun.dll": ok
MSG: check file "etc/VERSIONS": ok
MSG: check file "bin/x_wiz.exe": ok
MSG: check file "bin/xbackup.exe": ok
MSG: check file "Support/Mapfiles/sqlrun.map": ok
MSG: check file "symbols/show.pdb": ok
MSG: check file "bin/x_show.exe": ok
MSG: check file "symbols/sqlrun.pdb": ok
MSG: check file "env/serv.use": ok
MSG: check file "env/xstop.use": ok
MSG: check file "symbols/serv.pdb": ok
MSG: check file "pgm/show.exe": ok
MSG: check file "bin/x_wizard.exe": ok
MSG: check file "bin/sdbinfo.exe": ok
MSG: check file "bin/xinstinfo.exe": ok
MSG: check file "bin/x_wiztrc.exe": ok
MSG: check file "Support/Mapfiles/show.map": ok
MSG: check file "Support/Mapfiles/serv.map": ok
MSG: check file "bin/x_stop.exe": ok
STDOUT: ok
SYS: "c:program filessdbprograms inx_server.exe" install: 19712 INFO: Service 'XServer' is already installed
SYS: "c:program filessdbprograms inx_server.exe" remove: 19710 INFO: Service 'XServer' removed successfully
SYS: "c:program filessdbprograms inx_server.exe" install: 19709 INFO: Service 'XServer' installed successfully
MSG: SYSTEM PATH is up to date
MSG: packagedata of package Server Utilities changed
MSG: writing 3 packages
MSG: net install registry size = 39793 bytes
MSG: wrote install registry (45406 bytes)
MSG: packagedata of package Database Kernel changed
MSG: writing 3 packages
MSG: net install registry size = 39793 bytes
MSG: wrote install registry (45405 bytes)
MSG: no function "register" in package Database Kernel
MSG: set function reference "unregister" in package Database Kernel
MSG: set function reference "preuninstall" in package Database Kernel
MSG: set function reference "postuninstall" in package Database Kernel
MSG: no function "verify" in package Database Kernel
STDOUT: unregister Database Kernel 7.6.5.9
WRN: cannot execute command: xregcomp -u "c:program filessdbmaxdb1pgmdbpinstall": cannot create process, Le fichier spÈcifiÈ est introuvable.
WRN: cannot execute command: xregcomp -u "c:program filessdbprogramsliblivecachedbg": cannot create process, Le fichier spÈcifiÈ est introuvable.
SYS: dbmcli -R "c:program filessdbmaxdb1" inst_unreg : Error! Connection failed to node (local) for database (no dbname):
SYS: dbmcli -R "c:program filessdbmaxdb1" inst_unreg : dbmsrv executable not found
STDOUT: start real extraction of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBKRN.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:15 bin/
STDOUT: extracting: -rwxr-xr-x 274432 2008-08-15 21:51:01 bin/backint.exe
STDOUT: extracting: -rwxr-xr-x 802816 2008-08-15 21:53:13 bin/dbmevtdisp.exe
STDOUT: extracting: -rwxr-xr-x 552960 2008-08-15 21:53:27 bin/dbmevthndl_display.exe
STDOUT: extracting: -rwxr-xr-x 569344 2008-08-15 21:53:37 bin/dbmevthndl_winlog.exe
STDOUT: extracting: -rwxr-xr-x 290816 2008-08-15 21:48:43 bin/dbmsrvctl.exe
STDOUT: extracting: -rwxr-xr-x 41705 2008-08-15 19:51:15 bin/ireport.py
STDOUT: extracting: -rwxr-xr-x 245760 2008-08-15 21:52:11 bin/pipe2file.exe
STDOUT: extracting: -rwxr-xr-x 1232896 2008-08-15 21:51:09 bin/sdbfill.exe
STDOUT: extracting: -rwxr-xr-x 356352 2008-08-16 00:05:31 bin/sqlrun.dll
STDOUT: extracting: -rwxr-xr-x 53248 2008-08-15 19:55:01 bin/sqlver.exe
STDOUT: extracting: -rwxr-xr-x 53248 2008-08-15 19:55:01 bin/sqlwhat.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xkernprot.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xservice.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xtracesort.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_diagnose.exe
STDOUT: extracting: -rwxr-xr-x 331776 2008-08-15 21:53:55 bin/x_python.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:07 cluster/
STDOUT: extracting: -rwxr-xr-x 2121728 2008-08-15 20:24:13 cluster/dbmsrv_clu.exe
STDOUT: extracting: -rwxr-xr-x 81920 2008-08-15 20:12:33 cluster/SAPDBMSCSEx.dll
STDOUT: extracting: -rwxr-xr-x 122880 2008-08-15 20:12:43 cluster/sapdbmscsman.dll
STDOUT: extracting: -rwxr-xr-x 77824 2008-08-15 20:12:07 cluster/SAPDBMSCSMan.exe
STDOUT: extracting: -rwxr-xr-x 57344 2008-08-15 20:12:01 cluster/SAPDBMSCSRes.dll
STDOUT: extracting: -rwxr-xr-x 307200 2008-08-15 20:12:57 cluster/service_clu.exe
STDOUT: extracting: -rwxr-xr-x 499712 2008-08-15 20:12:55 cluster/serv_clu.exe
STDOUT: extracting: -rwxr-xr-x 339968 2008-08-15 20:12:53 cluster/stop_clu.exe
STDOUT: extracting: -rwxr-xr-x 339968 2008-08-15 20:12:51 cluster/strt_clu.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:07 demo/
STDOUT: extracting: -rw-rr 3110911 2008-08-15 19:51:15 demo/HOTEL.py
STDOUT: extracting: -rwxr-xr-x 367 2008-08-15 19:51:15 demo/ltutorial.py
STDOUT: extracting: -rw-rr 11333 2008-08-15 19:51:15 demo/tutoriallib.py
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:17 doc/
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:19 doc/FirstSteps/
STDOUT: extracting: -rw-rr 3455 2008-08-15 19:51:15 doc/FirstSteps/index.html
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:18 doc/FirstSteps/Java/
STDOUT: extracting: -rw-rr 1019 2008-08-15 19:51:15 doc/FirstSteps/Java/DemodbData.class
STDOUT: extracting: -rw-rr 1536 2008-08-15 19:51:15 doc/FirstSteps/Java/DemodbData.java
STDOUT: extracting: -rw-rr 1599 2008-08-15 19:51:15 doc/FirstSteps/Java/HelloMaxDB.class
STDOUT: extracting: -rw-rr 1459 2008-08-15 19:51:15 doc/FirstSteps/Java/HelloMaxDB.java
STDOUT: extracting: -rw-rr 1959 2008-08-15 19:51:15 doc/FirstSteps/Java/HowToJava.html
STDOUT: extracting: -rw-rr 1305 2008-08-15 19:51:15 doc/FirstSteps/Java/StateMaxDB.class
STDOUT: extracting: -rw-rr 1064 2008-08-15 19:51:15 doc/FirstSteps/Java/StateMaxDB.java
STDOUT: extracting: -rw-rr 227 2008-08-15 19:51:15 doc/FirstSteps/maxdbenv.cmd
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:18 doc/FirstSteps/ODBC/
STDOUT: extracting: -rw-rr 4510 2008-08-15 19:51:15 doc/FirstSteps/ODBC/HelloMaxDB.c
STDOUT: extracting: -rw-rr 1293 2008-08-15 19:51:15 doc/FirstSteps/ODBC/HowToODBC.html
STDOUT: extracting: -rw-rr 393 2008-08-15 19:51:15 doc/FirstSteps/ODBC/Makefile
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:18 doc/FirstSteps/Perl/
STDOUT: extracting: -rw-rr 973 2008-08-15 19:51:15 doc/FirstSteps/Perl/demodbData.pm
STDOUT: extracting: -rw-rr 1894 2008-08-15 19:51:15 doc/FirstSteps/Perl/HowToPerl.html
STDOUT: extracting: -rwxr-xr-x 960 2008-08-15 19:51:15 doc/FirstSteps/Perl/StateMaxDB.pl
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:19 doc/FirstSteps/Python/
STDOUT: extracting: -rw-rr 871 2008-08-15 19:51:15 doc/FirstSteps/Python/demodbData.py
STDOUT: extracting: -rwxr-xr-x 859 2008-08-15 19:51:15 doc/FirstSteps/Python/HelloMaxDB-API.py
STDOUT: extracting: -rwxr-xr-x 859 2008-08-15 19:51:15 doc/FirstSteps/Python/HelloMaxDB.py
STDOUT: extracting: -rw-rr 3043 2008-08-15 19:51:15 doc/FirstSteps/Python/HowToPython.html
STDOUT: extracting: -rwxr-xr-x 865 2008-08-15 19:51:15 doc/FirstSteps/Python/StateMaxDB.py
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:20 doc/FirstSteps/SQLDBC/
STDOUT: extracting: -rw-rr 3522 2008-08-15 19:51:15 doc/FirstSteps/SQLDBC/HelloMaxDB.cpp
STDOUT: extracting: -rw-rr 1329 2008-08-15 19:51:15 doc/FirstSteps/SQLDBC/HowToSQLDBC.html
STDOUT: extracting: -rw-rr 563 2008-08-15 19:51:15 doc/FirstSteps/SQLDBC/Makefile
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:10 env/
STDOUT: extracting: -rwxr-xr-x 6260 2008-08-15 21:53:37 env/APPS.py
STDOUT: extracting: -rw-rr 3800 2008-08-15 21:53:37 env/CNR3DATA.py
STDOUT: extracting: -rw-rr 8216 2008-08-15 21:53:37 env/CNR3TAB.py
STDOUT: extracting: -rw-rr 201779 2008-08-15 22:02:13 env/cserv.pcf
STDOUT: extracting: -rw-rr 1861 2008-08-15 21:53:37 env/DBANA.py
STDOUT: extracting: -rw-rr 17874 2008-08-15 21:53:39 env/DBMVIEWS.py
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:08 env/en/
STDOUT: extracting: -rw-rr 7609 2008-08-15 22:02:13 env/en/DBM.en
STDOUT: extracting: -rw-rr 15713 2008-08-15 21:53:39 env/GARBAGE.py
STDOUT: extracting: -rw-rr 249 2008-08-15 22:02:13 env/general.use
STDOUT: extracting: -rwxr-xr-x 1304 2008-08-15 21:53:45 env/getpackages.py
STDOUT: extracting: -rw-rr 1144 2008-08-15 21:53:39 env/INFO.py
STDOUT: extracting: -rw-rr 14609 2008-08-15 21:53:45 env/installib.py
STDOUT: extracting: -rw-rr 90473 2008-08-15 21:53:39 env/JDBC.py
STDOUT: extracting: -rw-rr 396 2008-08-15 22:02:13 env/kernprot.use
STDOUT: extracting: -rwxr-xr-x 949 2008-08-15 21:53:45 env/lapps.py
STDOUT: extracting: -rw-rr 8269 2008-08-15 19:51:15 env/lsystab.py
STDOUT: extracting: -rw-rr 19514 2008-08-15 21:53:39 env/ODBC.py
STDOUT: extracting: -rw-rr 1241 2008-08-15 21:53:39 env/ORADD.py
STDOUT: extracting: -rw-rr 266421 2008-08-15 21:53:41 env/ORADDCOM.py
STDOUT: extracting: -rw-rr 9586 2008-08-15 21:53:41 env/ORADDSYN.py
STDOUT: extracting: -rw-rr 158400 2008-08-15 21:53:41 env/ORADDV.py
STDOUT: extracting: -rw-rr 1400 2008-08-15 21:53:41 env/PRECOM.py
STDOUT: extracting: -rw-rr 50345 2008-08-15 21:53:45 env/REPOSITORY.py
STDOUT: extracting: -rw-rr 61439 2008-08-15 21:53:39 env/SAPDBLOADER.py
STDOUT: extracting: -rw-rr 4483 2008-08-15 21:53:41 env/SHOWCMD.py
STDOUT: extracting: -rw-rr 49869 2008-08-15 21:53:41 env/SQLDBC.py
STDOUT: extracting: -rw-rr 48352 2008-08-15 21:53:41 env/SYSDBA.py
STDOUT: extracting: -rw-rr 59678 2008-08-15 21:53:43 env/SYSDBACOM.py
STDOUT: extracting: -rw-rr 16770 2008-08-15 21:53:43 env/SYSINFO.py
STDOUT: extracting: -rw-rr 114665 2008-08-15 21:53:43 env/SYSINFOCOM.py
STDOUT: extracting: -rw-rr 17793 2008-08-15 21:53:43 env/TRIGGER.py
STDOUT: extracting: -rw-rr 3203 2008-08-15 21:53:43 env/UDE.py
STDOUT: extracting: -rw-rr 6596 2008-08-15 21:53:45 env/WA.py
STDOUT: extracting: -rw-rr 54914 2008-08-15 21:53:43 env/XDD.py
STDOUT: extracting: -rw-rr 106448 2008-08-15 21:53:43 env/XDDCOM.py
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:11 lib/
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:11 lib/python2.3/
STDOUT: extracting: -rw-rr 6867 2008-08-15 19:51:15 lib/python2.3/optlib.py
STDOUT: extracting: -rwxr-xr-x 135234 2008-08-15 19:51:15 lib/python2.3/pyexpat.pyd
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:11 lib/python2.3/sdb/
STDOUT: extracting: -rw-rr 14852 2008-08-15 19:51:15 lib/python2.3/sdb/dbapi.py
STDOUT: extracting: -rwxr-xr-x 507904 2008-08-15 21:54:03 lib/python2.3/sdb/dbm.pyd
STDOUT: extracting: -rwxr-xr-x 487424 2008-08-15 21:54:07 lib/python2.3/sdb/loader.pyd
STDOUT: extracting: -rwxr-xr-x 475136 2008-08-15 21:54:15 lib/python2.3/sdb/sql.pyd
STDOUT: extracting: -rw-rr 208 2008-08-15 19:51:15 lib/python2.3/sdb/__init__.py
STDOUT: extracting: -rwxr-xr-x 61503 2008-08-15 19:51:15 lib/python2.3/zlib.pyd
STDOUT: extracting: -rwxr-xr-x 49218 2008-08-15 19:51:15 lib/python2.3/_socket.pyd
STDOUT: extracting: -rwxr-xr-x 57407 2008-08-15 19:51:15 lib/python2.3/_sre.pyd
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:11 misc/
STDOUT: extracting: -rw-rr 2437 2008-08-16 00:38:45 misc/create_demo_db.cmd
STDOUT: extracting: -rw-rr 417 2008-08-16 00:38:45 misc/drop_demo_db.cmd
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:17 pgm/
STDOUT: extracting: -rwxr-xr-x 200704 2008-08-15 21:52:15 pgm/backup.exe
STDOUT: extracting: -rwxr-xr-x 380928 2008-08-15 20:10:53 pgm/cons.exe
STDOUT: extracting: -rwxr-xr-x 45056 2008-08-15 20:10:33 pgm/cr_param.exe
STDOUT: extracting: -rwxr-xr-x 940032 2008-08-15 19:51:15 pgm/dbghelp.dll
STDOUT: extracting: -rwxr-xr-x 299008 2008-08-15 21:49:01 pgm/dbmreg.exe
STDOUT: extracting: -rwxr-xr-x 454656 2008-08-15 21:49:37 pgm/dbmshm.exe
STDOUT: extracting: -rwxr-xr-x 2105344 2008-08-15 21:48:31 pgm/dbmsrv.exe
STDOUT: extracting: -rwxr-xr-x 1843200 2008-08-15 21:49:17 pgm/dbmsrvscd.exe
STDOUT: extracting: -rwxr-xr-x 299008 2008-08-15 21:48:49 pgm/dbmstart.exe
STDOUT: extracting: -rwxr-xr-x 299008 2008-08-15 21:48:53 pgm/dbmstop.exe
STDOUT: extracting: -rwxr-xr-x 299008 2008-08-15 21:49:05 pgm/dbmunreg.exe
STDOUT: extracting: -rwxr-xr-x 69632 2008-08-16 00:15:35 pgm/dbpinstall.dll
STDOUT: extracting: -rwxr-xr-x 1073152 2008-08-15 20:33:23 pgm/diagnose.exe
STDOUT: extracting: -rwxr-xr-x 7258112 2008-08-15 21:48:17 pgm/kernel.exe
STDOUT: extracting: -rwxr-xr-x 118784 2008-08-15 20:25:15 pgm/libhsscopy.dll
STDOUT: extracting: -rwxr-xr-x 1204224 2008-08-16 00:11:25 pgm/liboms.dll
STDOUT: extracting: -rwxr-xr-x 159744 2008-08-16 00:16:23 pgm/libsqlcls.dll
STDOUT: extracting: -rwxr-xr-x 1191936 2008-08-16 00:17:23 pgm/libSQLDBC.dll
STDOUT: extracting: -rwxr-xr-x 1269760 2008-08-16 00:20:23 pgm/libSQLDBC_C.dll
STDOUT: extracting: -rwxr-xr-x 3022848 2008-08-15 22:01:27 pgm/lserver.exe
STDOUT: extracting: -rwxr-xr-x 20545 2008-08-15 19:51:15 pgm/pysapdb.exe
STDOUT: extracting: -rwxr-xr-x 974915 2008-08-15 19:51:15 pgm/python23.dll
STDOUT: extracting: -rw-rr 2071185 2008-08-15 19:51:15 pgm/python23.zip
STDOUT: extracting: -rwxr-xr-x 45056 2008-08-15 20:10:31 pgm/renparam.exe
STDOUT: extracting: -rwxr-xr-x 294912 2008-08-15 20:11:51 pgm/service.exe
STDOUT: extracting: -rwxr-xr-x 417792 2008-08-15 20:11:55 pgm/sqlinst.dll
STDOUT: extracting: -rwxr-xr-x 1359872 2008-08-15 20:11:59 pgm/sqlmsg.dll
STDOUT: extracting: -rwxr-xr-x 319488 2008-08-15 20:11:01 pgm/stop.exe
STDOUT: extracting: -rwxr-xr-x 319488 2008-08-15 20:10:57 pgm/strt.exe
STDOUT: extracting: -rwxr-xr-x 98304 2008-08-15 22:11:33 pgm/StudioUtil.dll
STDOUT: extracting: -rwxr-xr-x 49152 2008-08-15 20:25:11 pgm/sysrc.exe
STDOUT: extracting: -rwxr-xr-x 73728 2008-08-15 20:11:57 pgm/systemrc.exe
STDOUT: extracting: -rwxr-xr-x 229376 2008-08-15 22:11:43 pgm/TableDefC.dll
STDOUT: extracting: -rwxr-xr-x 45056 2008-08-15 21:53:29 pgm/Tools_WinEvtLog.dll
STDOUT: extracting: -rwxr-xr-x 73728 2008-08-15 22:01:47 pgm/tracesort.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:17 sap/
STDOUT: extracting: -rw-rr 147 2008-08-15 19:51:15 sap/dbpinstall.lst
STDOUT: extracting: -rw-rr 761 2008-08-15 21:50:29 sap/grantxdb.dbm
STDOUT: extracting: -rwxr-xr-x 18192 2008-08-15 19:51:15 sap/lcinit.bat
STDOUT: extracting: -rwxr-xr-x 126976 2008-08-16 00:15:27 sap/lvcbench.dll
STDOUT: extracting: -rw-rr 89 2008-08-15 19:51:15 sap/saprfc.ini
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:44 pgm/
STDOUT: extracting: -rwxr-xr-x 14577664 2008-08-15 23:36:03 pgm/slowknl.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:45 Support/
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:57 Support/Mapfiles/
STDOUT: extracting: -rw-rr 505962 2008-08-15 21:51:00 Support/Mapfiles/backint.map
STDOUT: extracting: -rw-rr 661472 2008-08-15 20:10:53 Support/Mapfiles/cons.map
STDOUT: extracting: -rw-rr 121797 2008-08-15 20:10:32 Support/Mapfiles/cr_param.map
STDOUT: extracting: -rw-rr 1265024 2008-08-15 21:53:13 Support/Mapfiles/dbmevtdisp.map
STDOUT: extracting: -rw-rr 913124 2008-08-15 21:53:26 Support/Mapfiles/dbmevthndl_display.map
STDOUT: extracting: -rw-rr 918119 2008-08-15 21:53:36 Support/Mapfiles/dbmevthndl_winlog.map
STDOUT: extracting: -rw-rr 802618 2008-08-15 21:49:36 Support/Mapfiles/dbmshm.map
STDOUT: extracting: -rw-rr 3115022 2008-08-15 20:24:12 Support/Mapfiles/dbmsrv-clu.map
STDOUT: extracting: -rw-rr 3049582 2008-08-15 21:48:31 Support/Mapfiles/dbmsrv.map
STDOUT: extracting: -rw-rr 2607026 2008-08-15 21:49:16 Support/Mapfiles/dbmsrvscd.map
STDOUT: extracting: -rw-rr 78229 2008-08-16 00:15:35 Support/Mapfiles/dbpinstall.map
STDOUT: extracting: -rw-rr 1937316 2008-08-15 20:33:22 Support/Mapfiles/diagnose.map
STDOUT: extracting: -rw-rr 155915 2008-08-15 20:10:31 Support/Mapfiles/get_page.map
STDOUT: extracting: -rw-rr 11970292 2008-08-15 21:48:16 Support/Mapfiles/kernel.map
STDOUT: extracting: -rw-rr 191857 2008-08-15 20:25:15 Support/Mapfiles/libhsscopy.map
STDOUT: extracting: -rw-rr 2152785 2008-08-16 00:11:24 Support/Mapfiles/liboms.map
STDOUT: extracting: -rw-rr 259698 2008-08-16 00:16:22 Support/Mapfiles/libsqlcls.map
STDOUT: extracting: -rw-rr 1983758 2008-08-16 00:17:23 Support/Mapfiles/libSQLDBC.map
STDOUT: extracting: -rw-rr 2270630 2008-08-16 00:20:22 Support/Mapfiles/libSQLDBC_C.map
STDOUT: extracting: -rw-rr 3030264 2008-08-15 22:01:26 Support/Mapfiles/lserver.map
STDOUT: extracting: -rw-rr 241759 2008-08-16 00:15:26 Support/Mapfiles/lvcbench.map
STDOUT: extracting: -rw-rr 22799 2008-08-15 19:51:40 Support/Mapfiles/odbcreg.map
STDOUT: extracting: -rw-rr 437361 2008-08-15 21:52:10 Support/Mapfiles/pipe2file.map
STDOUT: extracting: -rw-rr 170094 2008-08-15 20:12:32 Support/Mapfiles/sapdbmscsex.map
STDOUT: extracting: -rw-rr 260595 2008-08-15 20:12:42 Support/Mapfiles/sapdbmscsman.map
STDOUT: extracting: -rw-rr 130593 2008-08-15 20:12:01 Support/Mapfiles/sapdbmscsres.map
STDOUT: extracting: -rw-rr 864387 2008-08-15 20:12:55 Support/Mapfiles/serv-clu.map
STDOUT: extracting: -rw-rr 573796 2008-08-15 20:12:57 Support/Mapfiles/service-clu.map
STDOUT: extracting: -rw-rr 545676 2008-08-15 20:11:50 Support/Mapfiles/service.map
STDOUT: extracting: -rw-rr 15115432 2008-08-15 23:36:03 Support/Mapfiles/slowknl.map
STDOUT: extracting: -rw-rr 674679 2008-08-15 20:11:54 Support/Mapfiles/sqlinst.map
STDOUT: extracting: -rw-rr 138012 2008-08-15 19:55:01 Support/Mapfiles/sqlver.map
STDOUT: extracting: -rw-rr 137724 2008-08-15 19:55:00 Support/Mapfiles/sqlwhat.map
STDOUT: extracting: -rw-rr 100215 2008-08-16 00:05:33 Support/Mapfiles/sql_run.map
STDOUT: extracting: -rw-rr 126593 2008-08-15 20:25:11 Support/Mapfiles/sysrc.map
STDOUT: extracting: -rw-rr 205806 2008-08-15 20:11:57 Support/Mapfiles/systemrc.map
STDOUT: extracting: -rw-rr 329621 2008-08-15 22:11:43 Support/Mapfiles/TableDefC.map
STDOUT: extracting: -rw-rr 180003 2008-08-15 22:01:47 Support/Mapfiles/tracesort.map
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:01:45 symbols/
STDOUT: extracting: -rw-rr 1199104 2008-08-15 21:51:00 symbols/backint.pdb
STDOUT: extracting: -rw-rr 2092032 2008-08-15 20:10:53 symbols/cons.pdb
STDOUT: extracting: -rw-rr 281600 2008-08-15 20:10:32 symbols/cr_param.pdb
STDOUT: extracting: -rw-rr 3836928 2008-08-15 21:53:13 symbols/dbmevtdisp.pdb
STDOUT: extracting: -rw-rr 3058688 2008-08-15 21:53:26 symbols/dbmevthndl_display.pdb
STDOUT: extracting: -rw-rr 3083264 2008-08-15 21:53:36 symbols/dbmevthndl_winlog.pdb
STDOUT: extracting: -rw-rr 2485248 2008-08-15 21:49:36 symbols/dbmshm.pdb
STDOUT: extracting: -rw-rr 8563712 2008-08-15 20:24:12 symbols/dbmsrv-clu.pdb
STDOUT: extracting: -rw-rr 8391680 2008-08-15 21:48:30 symbols/dbmsrv.pdb
STDOUT: extracting: -rw-rr 7703552 2008-08-15 21:49:15 symbols/dbmsrvscd.pdb
STDOUT: extracting: -rw-rr 420864 2008-08-16 00:15:35 symbols/dbpinstall.pdb
STDOUT: extracting: -rw-rr 4803584 2008-08-15 20:33:21 symbols/diagnose.pdb
STDOUT: extracting: -rw-rr 338944 2008-08-15 20:10:31 symbols/get_page.pdb
STDOUT: extracting: -rw-rr 36047872 2008-08-15 21:48:12 symbols/kernel.pdb
STDOUT: extracting: -rw-rr 470016 2008-08-15 20:25:15 symbols/libhsscopy.pdb
STDOUT: extracting: -rw-rr 5868544 2008-08-16 00:11:24 symbols/liboms.pdb
STDOUT: extracting: -rw-rr 1264640 2008-08-16 00:16:21 symbols/libsqlcls.pdb
STDOUT: extracting: -rw-rr 4713472 2008-08-16 00:17:22 symbols/libSQLDBC.pdb
STDOUT: extracting: -rw-rr 5180416 2008-08-16 00:20:21 symbols/libSQLDBC_C.pdb
STDOUT: extracting: -rw-rr 7171072 2008-08-15 22:01:25 symbols/lserver.pdb
STDOUT: extracting: -rw-rr 642048 2008-08-16 00:15:26 symbols/lvcbench.pdb
STDOUT: extracting: -rw-rr 1207296 2008-08-15 21:52:10 symbols/pipe2file.pdb
STDOUT: extracting: -rw-rr 3058688 2008-08-15 20:12:32 symbols/sapdbmscsex.pdb
STDOUT: extracting: -rw-rr 1002496 2008-08-15 20:12:42 symbols/sapdbmscsman.pdb
STDOUT: extracting: -rw-rr 330752 2008-08-15 20:12:01 symbols/sapdbmscsres.pdb
STDOUT: extracting: -rw-rr 2739200 2008-08-15 20:12:55 symbols/serv-clu.pdb
STDOUT: extracting: -rw-rr 2141184 2008-08-15 20:12:56 symbols/service-clu.pdb
STDOUT: extracting: -rw-rr 1944576 2008-08-15 20:11:50 symbols/service.pdb
STDOUT: extracting: -rw-rr 40643584 2008-08-15 23:35:57 symbols/slowknl.pdb
STDOUT: extracting: -rw-rr 2321408 2008-08-15 20:11:54 symbols/sqlinst.pdb
STDOUT: extracting: -rw-rr 2075648 2008-08-16 00:05:31 symbols/sqlrun.pdb
STDOUT: extracting: -rw-rr 306176 2008-08-15 19:55:01 symbols/sqlver.pdb
STDOUT: extracting: -rw-rr 306176 2008-08-15 19:55:00 symbols/sqlwhat.pdb
STDOUT: extracting: -rw-rr 248832 2008-08-16 00:05:33 symbols/sql_run.pdb
STDOUT: extracting: -rw-rr 2214912 2008-08-15 20:12:51 symbols/start-clu.pdb
STDOUT: extracting: -rw-rr 2206720 2008-08-15 20:12:52 symbols/stop-clu.pdb
STDOUT: extracting: -rw-rr 306176 2008-08-15 20:25:10 symbols/sysrc.pdb
STDOUT: extracting: -rw-rr 388096 2008-08-15 20:11:57 symbols/systemrc.pdb
STDOUT: extracting: -rw-rr 846848 2008-08-15 22:11:43 symbols/TableDefC.pdb
STDOUT: extracting: -rw-rr 887808 2008-08-15 22:01:47 symbols/tracesort.pdb
STDOUT: checking unpacked archive... MSG: check file "Support/Mapfiles/diagnose.map": ok
MSG: check file "doc/FirstSteps/ODBC/HowToODBC.html": ok
MSG: check file "lib/python2.3/_socket.pyd": ok
MSG: check file "Support/Mapfiles/get_page.map": ok
MSG: check file "pgm/dbmsrv.exe": ok
MSG: check file "env/INFO.py": ok
MSG: check file "symbols/dbmsrv-clu.pdb": ok
MSG: check file "pgm/diagnose.exe": ok
MSG: check file "symbols/cons.pdb": ok
MSG: check file "misc/create_demo_db.cmd": ok
MSG: check file "symbols/sapdbmscsres.pdb": ok
MSG: check file "symbols/cr_param.pdb": ok
MSG: check file "Support/Mapfiles/dbpinstall.map": ok
MSG: check file "lib/python2.3/sdb/__init__.py": ok
MSG: check file "symbols/dbmevthndl_winlog.pdb": ok
MSG: check file "symbols/libSQLDBC_C.pdb": ok
MSG: check file "bin/xtracesort.exe": ok
MSG: check file "bin/x_diagnose.exe": ok
MSG: check file "symbols/pipe2file.pdb": ok
MSG: check file "pgm/Tools_WinEvtLog.dll": ok
MSG: check file "symbols/dbmshm.pdb": ok
MSG: check file "pgm/cons.exe": ok
MSG: check file "sap/grantxdb.dbm": ok
MSG: check file "demo/tutoriallib.py": ok
MSG: check file "demo/HOTEL.py": ok
MSG: check file "symbols/liboms.pdb": ok
MSG: check file "env/cserv.pcf": ok
MSG: check file "Support/Mapfiles/TableDefC.map": ok
MSG: check file "lib/python2.3/_sre.pyd": ok
MSG: check file "pgm/service.exe": ok
MSG: check file "doc/FirstSteps/Python/HowToPython.html": ok
MSG: check file "doc/FirstSteps/ODBC/HelloMaxDB.c": ok
MSG: check file "Support/Mapfiles/libSQLDBC.map": ok
MSG: check file "doc/FirstSteps/Java/DemodbData.java": ok
MSG: check file "sap/saprfc.ini": ok
MSG: check file "pgm/dbghelp.dll": ok
MSG: check file "cluster/strt_clu.exe": ok
MSG: check file "symbols/libhsscopy.pdb": ok
MSG: check file "symbols/dbmsrv.pdb": ok
MSG: check file "symbols/sapdbmscsman.pdb": ok
MSG: check file "cluster/SAPDBMSCSMan.exe": ok
MSG: check file "pgm/tracesort.exe": ok
MSG: check file "Support/Mapfiles/sqlinst.map": ok
MSG: check file "bin/sqlwhat.exe": ok
MSG: check file "lib/python2.3/pyexpat.pyd": ok
MSG: check file "pgm/libSQLDBC_C.dll": ok
MSG: check file "Support/Mapfiles/sapdbmscsman.map": ok
MSG: check file "Support/Mapfiles/sapdbmscsres.map": ok
MSG: check file "Support/Mapfiles/dbmevthndl_winlog.map": ok
MSG: check file "bin/x_python.exe": ok
MSG: check file "symbols/sql_run.pdb": ok
MSG: check file "pgm/python23.dll": ok
MSG: check file "env/SQLDBC.py": ok
MSG: check file "symbols/tracesort.pdb": ok
MSG: check file "cluster/SAPDBMSCSRes.dll": ok
MSG: check file "cluster/stop_clu.exe": ok
MSG: check file "pgm/sqlinst.dll": ok
MSG: check file "pgm/StudioUtil.dll": ok
MSG: check file "Support/Mapfiles/slowknl.map": ok
MSG: check file "doc/FirstSteps/Python/HelloMaxDB.py": ok
MSG: check file "symbols/lserver.pdb": ok
MSG: check file "Support/Mapfiles/serv-clu.map": ok
MSG: check file "pgm/cr_param.exe": ok
MSG: check file "bin/backint.exe": ok
MSG: check file "bin/sqlrun.dll": ok
MSG: check file "pgm/libSQLDBC.dll": ok
MSG: check file "Support/Mapfiles/kernel.map": ok
MSG: check file "symbols/kernel.pdb": ok
MSG: check file "bin/dbmsrvctl.exe": ok
MSG: check file "env/UDE.py": ok
MSG: check file "symbols/dbmsrvscd.pdb": ok
MSG: check file "symbols/sqlinst.pdb": ok
MSG: check file "doc/FirstSteps/Java/DemodbData.class": ok
MSG: check file "env/lsystab.py": ok
MSG: check file "sap/lcinit.bat": ok
MSG: check file "lib/python2.3/zlib.pyd": ok
MSG: check file "doc/FirstSteps/Perl/StateMaxDB.pl": ok
MSG: check file "pgm/python23.zip": ok
MSG: check file "doc/FirstSteps/Java/HelloMaxDB.class": ok
MSG: check file "symbols/dbmevtdisp.pdb": ok
MSG: check file "env/installib.py": ok
MSG: check file "pgm/renparam.exe": ok
MSG: check file "doc/FirstSteps/Python/StateMaxDB.py": ok
MSG: check file "env/TRIGGER.py": ok
MSG: check file "pgm/libhsscopy.dll": ok
MSG: check file "symbols/serv-clu.pdb": ok
MSG: check file "pgm/systemrc.exe": ok
MSG: check file "pgm/dbmunreg.exe": ok
MSG: check file "Support/Mapfiles/sysrc.map": ok
MSG: check file "Support/Mapfiles/libhsscopy.map": ok
MSG: check file "bin/dbmevtdisp.exe": ok
MSG: check file "doc/FirstSteps/ODBC/Makefile": ok
MSG: check file "Support/Mapfiles/dbmsrv-clu.map": ok
MSG: check file "pgm/stop.exe": ok
MSG: check file "Support/Mapfiles/service-clu.map": ok
MSG: check file "Support/Mapfiles/lserver.map": ok
MSG: check file "Support/Mapfiles/libsqlcls.map": ok
MSG: check file "symbols/backint.pdb": ok
MSG: check file "Support/Mapfiles/systemrc.map": ok
MSG: check file "symbols/get_page.pdb": ok
MSG: check file "lib/python2.3/sdb/sql.pyd": ok
MSG: check file "Support/Mapfiles/dbmsrv.map": ok
MSG: check file "env/APPS.py": ok
MSG: check file "env/kernprot.use": ok
MSG: check file "Support/Mapfiles/lvcbench.map": ok
MSG: check file "symbols/systemrc.pdb": ok
MSG: check file "symbols/sqlver.pdb": ok
MSG: check file "pgm/liboms.dll": ok
MSG: check file "cluster/service_clu.exe": ok
MSG: check file "env/ORADDSYN.py": ok
MSG: check file "Support/Mapfiles/backint.map": ok
MSG: check file "env/SYSINFOCOM.py": ok
MSG: check file "Support/Mapfiles/dbmevthndl_display.map": ok
MSG: check file "cluster/SAPDBMSCSEx.dll": ok
MSG: check file "pgm/slowknl.exe": ok
MSG: check file "symbols/slowknl.pdb": ok
MSG: check file "symbols/sqlwhat.pdb": ok
MSG: check file "symbols/TableDefC.pdb": ok
MSG: check file "doc/FirstSteps/SQLDBC/HelloMaxDB.cpp": ok
MSG: check file "env/CNR3DATA.py": ok
MSG: check file "doc/FirstSteps/index.html": ok
MSG: check file "doc/FirstSteps/Java/HowToJava.html": ok
MSG: check file "bin/pipe2file.exe": ok
MSG: check file "doc/FirstSteps/Perl/demodbData.pm": ok
MSG: check file "bin/dbmevthndl_winlog.exe": ok
MSG: check file "Support/Mapfiles/tracesort.map": ok
MSG: check file "symbols/lvcbench.pdb": ok
MSG: check file "demo/ltutorial.py": ok
MSG: check file "symbols/sapdbmscsex.pdb": ok
MSG: check file "bin/xservice.exe": ok
MSG: check file "doc/FirstSteps/Python/HelloMaxDB-API.py": ok
MSG: check file "symbols/libSQLDBC.pdb": ok
MSG: check file "env/REPOSITORY.py": ok
MSG: check file "Support/Mapfiles/cr_param.map": ok
MSG: check file "lib/python2.3/optlib.py": ok
MSG: check file "cluster/serv_clu.exe": ok
MSG: check file "symbols/sysrc.pdb": ok
MSG: check file "env/ORADDCOM.py": ok
MSG: check file "doc/FirstSteps/SQLDBC/Makefile": ok
MSG: check file "pgm/dbmsrvscd.exe": ok
MSG: check file "symbols/diagnose.pdb": ok
MSG: check file "pgm/TableDefC.dll": ok
MSG: check file "doc/FirstSteps/Perl/HowToPerl.html": ok
MSG: check file "Support/Mapfiles/sqlwhat.map": ok
MSG: check file "symbols/stop-clu.pdb": ok
MSG: check file "cluster/dbmsrv_clu.exe": ok
MSG: check file "pgm/sysrc.exe": ok
MSG: check file "pgm/kernel.exe": ok
MSG: check file "Support/Mapfiles/sql_run.map": ok
MSG: check file "doc/FirstSteps/Java/StateMaxDB.class": ok
MSG: check file "Support/Mapfiles/dbmsrvscd.map": ok
MSG: check file "symbols/service-clu.pdb": ok
MSG: check file "symbols/dbmevthndl_display.pdb": ok
MSG: check file "Support/Mapfiles/odbcreg.map": ok
MSG: check file "env/SAPDBLOADER.py": ok
MSG: check file "bin/sqlver.exe": ok
MSG: check file "env/general.use": ok
MSG: check file "sap/dbpinstall.lst": ok
MSG: check file "pgm/dbpinstall.dll": ok
MSG: check file "doc/FirstSteps/Java/StateMaxDB.java": ok
MSG: check file "env/en/DBM.en": ok
MSG: check file "sap/lvcbench.dll": ok
MSG: check file "pgm/lserver.exe": ok
MSG: check file "env/getpackages.py": ok
MSG: check file "env/lapps.py": ok
MSG: check file "Support/Mapfiles/dbmshm.map": ok
MSG: check file "Support/Mapfiles/service.map": ok
MSG: check file "misc/drop_demo_db.cmd": ok
MSG: check file "lib/python2.3/sdb/dbm.pyd": ok
MSG: check file "env/WA.py": ok
MSG: check file "symbols/dbpinstall.pdb": ok
MSG: check file "bin/ireport.py": ok
MSG: check file "Support/Mapfiles/sapdbmscsex.map": ok
MSG: check file "Support/Mapfiles/libSQLDBC_C.map": ok
MSG: check file "Support/Mapfiles/liboms.map": ok
MSG: check file "lib/python2.3/sdb/dbapi.py": ok
MSG: check file "doc/FirstSteps/Java/HelloMaxDB.java": ok
MSG: check file "env/ORADDV.py": ok
MSG: check file "doc/FirstSteps/maxdbenv.cmd": ok
MSG: check file "pgm/pysapdb.exe": ok
MSG: check file "pgm/libsqlcls.dll": ok
MSG: check file "env/GARBAGE.py": ok
MSG: check file "symbols/libsqlcls.pdb": ok
MSG: check file "bin/xkernprot.exe": ok
MSG: check file "Support/Mapfiles/dbmevtdisp.map": ok
MSG: check file "env/SYSINFO.py": ok
MSG: check file "symbols/sqlrun.pdb": ok
MSG: check file "env/XDDCOM.py": ok
MSG: check file "bin/sdbfill.exe": ok
MSG: check file "lib/python2.3/sdb/loader.pyd": ok
MSG: check file "env/XDD.py": ok
MSG: check file "doc/FirstSteps/SQLDBC/HowToSQLDBC.html": ok
MSG: check file "pgm/backup.exe": ok
MSG: check file "env/ODBC.py": ok
MSG: check file "Support/Mapfiles/pipe2file.map": ok
MSG: check file "Support/Mapfiles/cons.map": ok
MSG: check file "pgm/dbmshm.exe": ok
MSG: check file "env/SYSDBA.py": ok
MSG: check file "env/CNR3TAB.py": ok
MSG: check file "env/ORADD.py": ok
MSG: check file "env/PRECOM.py": ok
MSG: check file "pgm/strt.exe": ok
MSG: check file "cluster/sapdbmscsman.dll": ok
MSG: check file "Support/Mapfiles/sqlver.map": ok
MSG: check file "env/DBANA.py": ok
MSG: check file "env/SHOWCMD.py": ok
MSG: check file "pgm/dbmstop.exe": ok
MSG: check file "env/SYSDBACOM.py": ok
MSG: check file "symbols/start-clu.pdb": ok
MSG: check file "bin/dbmevthndl_display.exe": ok
MSG: check file "doc/FirstSteps/Python/demodbData.py": ok
MSG: check file "pgm/dbmstart.exe": ok
MSG: check file "env/DBMVIEWS.py": ok
MSG: check file "env/JDBC.py": ok
MSG: check file "pgm/sqlmsg.dll": ok
MSG: check file "pgm/dbmreg.exe": ok
MSG: check file "symbols/service.pdb": ok
STDOUT: ok
MSG: file "c:/program files/sdb/maxdb1/doc/FirstSteps/index.html" modified by installer
MSG: file "c:/program files/sdb/maxdb1/doc/FirstSteps/Perl/HowToPerl.html" modified by installer
MSG: file "c:/program files/sdb/maxdb1/doc/FirstSteps/Python/HowToPython.html" modified by installer
MSG: file "c:/program files/sdb/maxdb1/doc/FirstSteps/ODBC/HowToODBC.html" modified by installer
MSG: file "c:/program files/sdb/maxdb1/doc/FirstSteps/Java/HowToJava.html" modified by installer
MSG: file "c:/program files/sdb/maxdb1/misc/create_demo_db.cmd" modified by installer
MSG: file "c:/program files/sdb/maxdb1/misc/drop_demo_db.cmd" modified by installer
MSG: file "c:/program files/sdb/maxdb1/doc/FirstSteps/maxdbenv.cmd" modified by installer
SYS: "C:Program FilessdbMAXDB1 indbmsrvctl.exe" start
SYS: "C:Program Filessdbprogramspgmdbmcli.exe" -R "C:Program FilessdbMAXDB1" inst_reg -k "C:Program FilessdbMAXDB1": ERR
SYS: "C:Program Filessdbprogramspgmdbmcli.exe" -R "C:Program FilessdbMAXDB1" inst_reg -k "C:Program FilessdbMAXDB1": -24913,ERR_SERVICEDB: Cannot register service database instance for C:Program FilesSDBMAXDB1
STDERR: error occured while executing "C:Program Filessdbprogramspgmdbmcli.exe" -R "C:Program FilessdbMAXDB1" inst_reg -k "C:Program FilessdbMAXDB1"
STDERR: "C:Program Filessdbprogramspgmdbmcli.exe" -R "C:Program FilessdbMAXDB1" inst_reg -k "C:Program FilessdbMAXDB1": ERR
"C:Program Filessdbprogramspgmdbmcli.exe" -R "C:Program FilessdbMAXDB1" inst_reg -k "C:Program FilessdbMAXDB1": -24913,ERR_SERVICEDB: Cannot register service database instance for C:Program FilesSDBMAXDB1
STDERR: installation exited abnormally at Fr, Jan 09, 2009 at 18:17:25
MSG: packagedata of package Redist Python changed
MSG: writing 4 packages
MSG: net install registry size = 40263 bytes
MSG: wrote install registry (46259 bytes)
STDOUT: start real extraction of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBRDPY.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:04:43 bin/
STDOUT: extracting: -rwxr-xr-x 331776 2008-08-15 21:53:55 bin/x_python.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:04:43 lib/
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:04:44 lib/python2.3/
STDOUT: extracting: -rw-rr 6867 2008-08-15 19:51:15 lib/python2.3/optlib.py
STDOUT: extracting: -rwxr-xr-x 135234 2008-08-15 19:51:15 lib/python2.3/pyexpat.pyd
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:04:43 lib/python2.3/sdb/
STDOUT: extracting: -rwxr-xr-x 507904 2008-08-15 21:54:03 lib/python2.3/sdb/dbm.pyd
STDOUT: extractiHI there,
it really does look like as the "uninstallation" was done by merely deleting files from the filesystem.
This will always lead to problems when you try to re-install a MaxDB afterwards.
Uninstallations should be done via SDBUNIST to avoid such issues.
Based on the error messages like:
getRelease():C:/Program Files/SDB/MAXDB1/pgm/kernel.exe not found
MSG: migrate server installation data for INSTROOT "c:/program files/sdb/maxdb1"
MSG: installed package is flaged as invalid => skipping update check
WRN: cannot execute command: xregcomp -u "c:program filessdbmaxdb1pgmdbpinstall": cannot create process, Le fichier spÈcifiÈ est introuvable.
>WRN: cannot execute command: xregcomp -u "c:program filessdbprogramsliblivecachedbg": cannot create process, Le fichier spÈcifiÈ est introuvable.
we can tell: the MaxDB installation registration had not been deleted correctly.
If I'd to guess, I'd say you just deleted whatever was in the folder "c:program filessdb" and crossed fingers that this would do.
Anyhow, on this system, due to the usage of non-SAP-standard folder layout check this one, the installation registration can by found in the all users data folder:
>MSG: Template set indep data path to "c:/documents and settings/all users/application data/sdb/data"
This would have to be removed as well.
Anyhow, maybe you want to read the documentation before messing up your system by try and error:
Installation Manual
regards,
Lars -
RFC Destination could not be created in TREX administration tool
Hi All,
Recently i installed the TREX server, I am trying to connect the ABAP system with the RFC connection. I entered all necessary data for the RFC connection it giving error as
RFC Destination could not be created.
To solve the above problem i created one RFC connection of type TCP/IP in ABAP server eventhough it is not solved.
Can i have the solution for the above problem?
Regards,
Vivek.Hi Michale,
Thanks for your quick response; I tried all the mentioned possibilities in that help document, still i am facing the same problem.
It is giving the below error
Connect to SAP System failed.Possible reasons:
-Logon data incorrect
-Password is not uppercase(must also be uppercase)
-SAP system user locked
-SAP user not in specified client
-SAP User rights are insufficient
-SAP system not reachable
-saprfc.ini unavailable or entries incorrect
-TREXTcpipClient.ini section[communication],parameters rfcdestination, sapsystem not set
-SAP system Basis component below 6.20 or SP too low
-->check also latest TREXTcpiplient trace file entries.*
The above all are check by me everything is fine.
The below information from the saprfc.ini file
DEST=NPI
TYPE=B
MSHOST=server1
GROUP=server1_group*.
Is there any mistake, please let me know.
Regards,
Vivek. -
Inconsistency with ZPMSENDSTATUS for Open Hub Destination
Hi Experts,
I dont know you have come accross this scenario but I will apprecaite all your advice.
We have APO 7.0 and we are using the BW component to extract data to informatica.
Our environment is as follow
SAP SCM 7.0 SP8
Informatica PWCD 8.1.6 hot fix 13
1.we have created 5 chains with similar variants for ZPMSENDSTATUS
2. Each variant relates to a folder and workflow to be executed within informatica
3. When we execute the chains only two work correctly all the time and 3 fail
the 3 that are failing are failing within the ZPMSENDSTATUS when running API RSB_API_OHS_DEST_SETPARAMS. This is odd since the other two only differ on the workflow to be executed and obviously on the Open Hub destination. Can anyone provide some advice on this?
thanks,
NatHi Maruthi,
thanks for your response but here are the details for the variants that are working and failining
working:
DEST: < here we have the RFC that relates to the logical system and the program id which is also included in saprfc.ini>
INFPARA: AERO/APO:WF_SAP_APO_PART_PLATFORM_ABP2_BGA:S_M_SAP_APO_PART_PLATFORM_ABP2
CONTEXT: OHS API
OHDEST: <OHDS defined as target>
Failing:
DEST: < here we have the RFC that relates to the logical system and the program id which is also included in saprfc.ini>
INFPARA: AERO/APO:WF_SAP_APO_PART_PLATFORM_ABP4_ATR:S_M_SAP_APO_PART_PLATFORM_ABP4
CONTEXT: OHS API
OHDEST: <OHDS defined as target>
So you see, they all target the same folder only different workflows. Still it works for the first and not for the second. -
Hello ,
I have created SSIS package to connect SAP using ado.net Connection and i am successfully pooling data from sap to Sql server (2014 64 bit ) (Windows server 2008 R2 (64 bit)).
My Package is running properly using SSIS But when i try to schedule it from SQL server Agent i am getting following error .
"Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 3:00:00 AM Error:
2014-11-27 03:00:03.57 Code: 0xC0208449 Source: ADRC ADO NET Source [2] Description: ADO NET Source has failed to acquire the connection {B4F9F268-670A-4E37-A752-AC135CD692DE} with the following error message: "Details:
ErrorCode=RFC_OK. ErrorGroup=RFC_ERROR_LOGON_FAILURE. SapErrorMessage=Open file 'saprfc.ini' failed: 'No such file or directory'. AdapterErrorMessage=.". End Error Error: 2014-11-27 03:00:03.57 Code: 0xC0047017
Source: ADRC SSIS.Pipeline Description: ADO NET Source failed validation and returned error code 0xC0208449. End Error Error: 2014-11-27 03:00:03.57 Code: 0xC004700C Source: ADRC SSIS.Pipeline
Description: One or more component failed validation. End Error Error: 2014-11-27 03:00:03.57 Code: 0xC0024107 Source: ADRC Description: There were errors during task validation. End Error DTExec:
The package execution returned DTSER_FAILURE (1). Started: 3:00:00 AM Finished: 3:00:03 AM Elapsed: 3.4 seconds. The package execution failed. The step failed."
I have tried all possible solution from internet but not success yet.Please help me to solve this as soon as possible.
Regards,
AKshay Adivarekar
Akshay AdivarekarHi AKshay,
Based on the error message, it seems that the issue is caused by the current user NT Service\SQLSERVERAGENT doesn’t have required permissions to connect to the SAP that the ADO.NET Connection Manager accesses.
By default, the NT Service\SQLSERVERAGENT account only has the following permissions granted by SQL Server Setup:
Log on as a service (SeServiceLogonRight)
Replace a process-level token (SeAssignPrimaryTokenPrivilege)
Bypass traverse checking (SeChangeNotifyPrivilege)
Adjust memory quotas for a process (SeIncreaseQuotaPrivilege)
In this scenario, we can change the SQL Server Agent Service Account to another account that has required permission or we can create a SQL Server Agent proxy account. This proxy account must use a credential that lets SQL Server Agent run the job as the account
that created the package or as an account that has the required permissions.
For more information about how to run a SSIS Package from SQL Server Agent Using a Proxy Account, please refer to the following blog:
http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support -
Hi,
I try to pass "Test Plan Secure Network Communications BC-SNC" for SNC-adapter, developed our team. Problem occur on step "2.11 Testing Secure КАС-connections, front end to SAP (SAPINFO) (2.11.2 RFC with load-balancing (RFC Type B))".
I created PUBLIC and SNC logon groups on SAP Web AS. Each group include one sever.
I createed SAPRFC.ini file with following content:
/* Conventional access */
DEST=DV2_PUBLIC
TYPE=B
R3NAME=DV2
MSHOST=<our_hostnsme>
GROUP=PUBLIC
/* Access using SNC-protected communication */
DEST=DV2_SNC
TYPE=B
R3NAME=DV2
MSHOST=<our_hostnsme>
GROUP=SNC
SNC_MODE=1
SNC_PARTNERNAME=p:CN=SERVER
SNC_LIB=<pass_to_our_library>
Then I run SAPINFO program with 2 varians:
1. SAPINFO DEST=DV2_PUBLIC
2. SAPINFO DEST=DV2_SNC
The first finished with success. Second with faild. Error message:
<----
>
RFC resize I/O buffer to 16000 bytes
RFC >>>> DV2_SNC : EXT 10.10.206.200 >>> OPEN.
RFC ======> Connect to message server failed
Connect_PM MSHOST=10.10.206.200, R3NAME=DV2, GROUP=SNC
LOCATION CPIC (TCP/IP) on local host
ERROR internal error
TIME Thu Feb 05 10:07:23 2009
RELEASE 40B
COMPONENT LG
VERSION 4
RC -1
COUNTER 1
RFC *> RfcOpen
RFC options->destination = DV2_SNC
RFC options->mode = RFC_MODE_PARAMETER
RFC options->connopt = <NULL>
RFC options->client = 000
RFC options->user = SAPCPIC
RFC options->password = secret (-:
RFC options->language = E
RFC options->trace = 0
RFC >>>> DV2_SNC : EXT 10.10.206.200 >>> CLOSE.
Group Error group 102
Key RFC_ERROR_COMMUNICATION
Message Connect to message server failed
Connect_PM MSHOST=10.10.206.200, R3NAME=DV2, GROUP=SNC
LOCATION CPIC (TCP/IP) on local host
ERROR internal error
TIME Thu Feb 05 10:07:23 2009
RELEASE 40B
COMPONENT LG
VERSION 4
RC -1
COUNTER 1
<----
>
Although, if in second variand delet settings:
SNC_MODE=1
SNC_PARTNERNAME=p:CN=SERVER
SNC_LIB=<pass_to_our_library>
and run SAPINFO DEST=DV2_SNC - it is success.
Help me, please.
Sorry for my English.Hi
May be you have some different issue other than mapping.
Set the file at source location and then check with RWB communication channel paylaod and SXMB_MONI inbound message. If it fail in mapping then too you can see the XML produced by FCC
Thanks
Gaurav -
BEx Analyzer (SAP BW 3.x) - No Applicable Data Found
Hi,
currently, i now access my BI Server remotelly and my local pc is install with Netweaver 2007s, and i try to do a tutorial on SAP BW. like create infosource, infocube and etc but when i finish creating the infocube and try to make a new query on BEx Analyzer (SAP BW 3.x), and seem like it cannot display anything the errors is as follow "No Applicable Data Found" so now i suspect is either drivers problem or access right problem.. beside that i do make an Installation Check On BEx Analyzer on Business Explorer after that i display this few red alerts.
Filename Version on PC
<b>BW Components</b>
sapbex.xla Not found
sapbex0.xla Not found
sapbexc.xla
<b>OLE for OLAP</b>
mdrmdlg.dll Not found
mdrmsap.dll Not found
mdxpars.dll Not found
saprfc.ini Not found
scerrlkp.dll Not found
<b>SAP GUI core components</b>
sapfctrl.dll Not found
sapfcust.exe Not found
sapfdraw.dll Not found
sapfewrm.dll Not found
sapfhook.dll Not found
wonder could anyone advise me on will this few components result i unable to display the data? if really i need those component how could i download it or should i reinstall it...
anyway for access right part, currently i not the super user account will it affect the query??Hi Ram,
My dimension table i check already in the Data Warehousing WorkBench the data is sufficient.
even i also check on My Fact table, it has also data loaded in.
but then problem is i unable to display data out.
as according to the book, i follow it should be display out the whole information.
Regards
Jia Jun -
RFC conn between SAP ERP and TREX not working
Hi experts,
we run a TREX instance on a Windows 2003 server and use it for our HCM portal.
The solution is in operation since 2 years but actually we face the problem that objects which have been created within the last month will not be covered by the index.
Without knowing about any changes in the setup I see the following error message when I perform the RFC connecten test in our ERP system:
Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: program Trex_UKP_20071025104543 not registered
Error Details LOCATION: SAP-Gateway on host janos / sapgw00
Error Details DETAIL: TP Trex_UKP_20071025104543 not registered
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 12906
Error Details MODULE: gwr3cpic.c
Error Details LINE: 1778
Error Details RETURN CODE: 679
Error Details SUBRC: 0
Error Details RELEASE: 700
Error Details TIME: Mon Jul 27 10:34:48 2009
Error Details VERSION: 2
In the TREX admin tool on the Windows server I see the following log message:
Source->Destination: Not set in TREX but TREX reachable -> ini file section missing?.
After reading lots of notes I guess that I have to register the server program that's used in the RFC on the gateway.
Unfortunately I have no idea how to do that.
Has anybody experiences with such a problem case or can tell me how to continue?
Is the problematic RFC realy the reason of my problem or just another side effect?
Many thanks for your really appreciated help in advance and best regards
GünterHi again,
the saprfc.ini on the TREX server look like follows:
DEST=UKT
TYPE=A
ASHOST=medos
SYSNR=00
DEST=UKP
TYPE=A
ASHOST=janos
SYSNR=00
UKT is our test system which is connected to the same TREX server and everything is fine there.
On the test system I can also see the registered server program in SMGW.
UKP is our productive system where the configuration should be the same.
Of course I do not see the registered server program in SMGW there.
Is the way described in above link (RFCACCEPT) the only correct way to register my server program?
I ask because I found information that the server program has to be developed according to this rfcaccept command and I have absolutely no idea wheather this is so.
Thanks again for your help!
Günter
Maybe you are looking for
-
IOS 7.0.3 same song but in multiple genres?
The only way I listen to music is by Genre. In the past, I've always opened the Music App, then clicked on genre, and gone from there. No issues. I have major issues with the new iOS and cannot for the life of me figure it out. Let's say I have a tra
-
Poor image quality in pdf for Aperture book
Can anyone tell me how to retain the quality of original images when I export to PDF for book production in Aperture? I am trying to produce a book with 11 pages, in large soft back format. Most of the images are black and white, and all are PNGs.
-
IPad first generation wont charge. Any idea's
Please help my Ipad g1 wont charge anymore!! Is this a common fault ?
-
Changing Period Indicator not allowed in numbering series setup
Hi to all dear experts... and happy new yaer!!! I need a little help to solve thi s issue. Today i create a new posting period for year 2015 (sub peridos => months) After that, i try to change the period indicator in ADMINISTRATION => SYSTEM INIZIALI
-
i have taken pictures with my camera they are i photo how can i show these in lookbook pdf format, just like presentations, thank you