SAS Data Integration Studio, DataFlux Data Management Studio, SAS/ACCESS, SAS Data Loader for Hadoop and others

SAP BW Gateway error

Accepted Solution Solved
Reply
Occasional Contributor
Posts: 8
Accepted Solution

SAP BW Gateway error

I'm using Data Surveyor for BW and when I run jobs against SAP I am intermittently getting a GWY_MONITIOR_DISABLED error which kills the job. Has anyone else experienced this and if so is there an easy fix?

 

Thanks


Accepted Solutions
Solution
‎11-08-2016 04:56 AM
Occasional Contributor
Posts: 8

Re: SAP BW Gateway error

There's now a hotfix for this if you are running the M3 release of Data Surveyor.

 

http://support.sas.com/kb/58/319.html

View solution in original post


All Replies
Super User
Posts: 5,256

Re: SAP BW Gateway error

Sounds like a SAP error/message, so try to talk the SAP admin people first.

 

Example on a SAP thread:

https://scn.sap.com/thread/1098966

Data never sleeps
Solution
‎11-08-2016 04:56 AM
Occasional Contributor
Posts: 8

Re: SAP BW Gateway error

There's now a hotfix for this if you are running the M3 release of Data Surveyor.

 

http://support.sas.com/kb/58/319.html

Established User
Posts: 1

Re: SAP BW Gateway error

Hello,

 

All jbs that receive info from SAP are crashing. The error is:

ERROR: Another RFC server is registered at the gateway (sapbxxxxr:sapgw02) with the program id (RFC.SAS6) assigned to this server.

       Check the RFC destination setup.

 

From SAP the error is:

 

Error when opening an RFC connection ("CPIC-CALL: 'ThSAPOCMINIT',

communication rc: CM_RESOURCE_FAILURE_RETRY (cmRc=27), taskhandler rc:

GW_TIMEOUT_REG_PRGM (thRc=677)#Timeout while waiting for a connection to be

established                 ").

 

Can you tell me what can be the issue ?

Occasional Contributor
Posts: 8

Re: SAP BW Gateway error

Check on SAP the /SAS/DESTS table and see if there are any destinations that remain in use even when there are no SAS sessions running.

 

Also check to see if there is an RFC process sitting in a "Waiting" state on BW (RFC.SAS6 in your case). this can be removed using the "delete client" option. - See example below where RFC.SAS3 is giving a similar error to the one you're experiencing.

 

rfc.sas3.png

 

☑ This topic is SOLVED.

Need further help from the community? Please ask a new question.

Discussion stats
  • 4 replies
  • 442 views
  • 0 likes
  • 3 in conversation