SAP System Message: S...

Recently we were about to begin testing SAPGUI 7.20 on Windows 7 Enterprise for an upcoming roll-out, and we ran into a little trouble.  For some reason we could not get Single Sign-On (SSO) to work correctly. Whenever we tried to log onto the SAP system using SSO, we would get the following error:
"SAP System Message: S"
Not very descriptive, I know.  Apparently this is a fairly common error that will come up for various issues with GUI communication to the system.  When we finally traced the problem to the SAP instance (rather than the GUI itself) we were able to resolve it fairly quickly. The error comes up before being able to access the SAP system, so it is easy to assume the problem lies with the GUI or the network. But our trace showed that everything on the application and network side was working correctly.  SM21 showed multiple "Delete session 001 after error 044" errors. Error 044 is and error in the SNC layer.  So I looked at the instance profile for our system and noticed that the SNC_ENABLE parameter had been set with a value of 0, which disabled SNC for that instance.  All the other instances were still set to 1 based on the values in the Default profile.  Apparently this parameter lingered over from a previous upgrade, and we had just always used log on balancing in that system, so it was never noticed.
After commenting out the SNC_ENABLE parameter (so that the Default profile's values would be used) all of our troubles disappeared.
SAPGUI 7.20 patch 3 works great with Windows 7.

Hope this helps...

Client Copy ends with Error: FINB_TR_CC_EXIT_TARGET...

Okay, so we recently ran a client copy from a productive system to quality. The copy took over 21 hours, and when it was complete, an error was showing.  FINB_TR_CC_EXIT_TARGET was listed under the Table Name field, but obviously that was not a table.  Actually it is a function module, and it was being called at the time of the client copy error.
This ended up being a fairly easy fix.  Since it is apparently common for client copies to fail during the post-processing step, SAP released note 1235955.  If you follow the note it will walk you through completing the process. Worked great for us.

Hope this helps...