Logging user added to group is written differently to TS_AdminChanges whether one uses the web admin or the System Admin Tool. For example if a user is associated with 10 groups and is then added to an 11th, the action as logged from the System Admin tool will only add one line to the TS_AdminChanges. Whereas if the action is carried out from the Web Admin, lines are logged for removing the user from all 10 groups and then adding them and the new group again.
In Business Mashups 2009 R1, when you invoke aewebservices71 from a Notification, and use the UpdateItemWithName, the webservices executes properly, however, you receive a series of errors in the Application Event Log . The errors in the Application Event Log would contain phrases similar to the following: Error occurred in file:
When you create a notification you can have it call a web service as its action and map return fields from the web service to your sbm item. These can be tricky to troubleshoot because there isn't a lot of logging that takes place. The log for these events should show in the ns.log file.
You can use the attached registry keys to enable some very basic logging about the soap request and response that gets sent and received from notifications or other web services. This can be particularly helpful when a soap request or response is too large and gets chopped of in the Common log . This logging will show the entire request and response envelope.
Try to perform transition with web service action again ( as at step 2.6 ) If you look at the SLM log , you will see that there was a licence checked-out to the user at the server-name running the Web -Service rather than at his actual client machine. The only way to avoid this issue is not to leave a session open and unused for longer than about 30 mins or avoid limiting users to a single concurrent licence only.
Get the following error in ns. log when scheduled report takes over a minute to run. Exception occured during invoking AE web service 'RunReportXML': Read timed out
