We were just setting up the SAP Extractor to a BW 7.31 environment, to load Cubes and ODS from a test and a live BW System.
Both systems are identically setup as the SAP extractor connector manual describes.
But still we face an issue by running the script with the connection to the live system. The same script works with an connection to the test system.
After running the script to live system, we see the the QTQVCEXTRACT user in the sm50 collecting the data and the job running in SM37.
At the same time on the Qlik-View side, we have an app-crash with the windows 2012 error message popup (QVconnect 11.20 SR9 has crashed). Processes in SAP keep running for several minutes until the connection lost is noticed.
In the QvSAP connector error log we found following entries:
Received Meta Data, No of Fields: 7
Information from server: INFOMSG : Started job: REQU_QTQVCEXTR1_20150609094941
If we double check the connection in the SM59 with a connection test, we see that it is connected in test system but throws an unregistered programm error message in the live system:
Error when opening the RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc
ERROR: program QTQVCEXTR1 not registered
LOCATION: SAP-Gateway on host DZSAPBWSV11.geobra.net / sapgw13
DETAIL: TP QTQVCEXTR1 not registered
Actually we think, that normally the programm registeres itself by connecting to the live system, but something seems to be preventing it by doing so.
On Qlikview side we have a successful connection test by setting up the connector and we also recieve meta-data as shown in the the above logfile, but as soon as it starts loading data, the application crashes.
Please check the document QlikView Connector for SAP - Tips and Tricks which can be found in the starting page of 'Connector for SAP', under the heading: ERROR registration of tp <program id> from host <external host> not allowed
It might be the cause of the problem.
Also check the Service log on the server where the Service is running, found in the same path as the connector log.
I believe this error is SAP related and not a connector problem. You can check if the Extraction job in SAP has finished OK in transaction SM37. Job name is 'BI' concatenated with the connector job name from the connector log, in your case BIREQU_QTQVCEXTR1_20150610160952.
You can also check the Transactional RFC in transaction SM58.