Sage 100

Sage 100 2014 Advanced e-WebServices, website has been working for couple of years, no changes we are aware of. Sending the order thru to the webservice we are getting the following message back saying it failed [""faultstring""]=> string(57) ""Could not clear SO_SalesOrder_Bus: An exception occurred."" [""faultcode""]=> string(14) ""a:WS_Exception"" [""detail""]=> object(stdClass)#3 (1) { [""MasFault""]=> object(stdClass)#4 (4) { [""ClassName""]=> string(17) ""SO_SalesOrder_Bus"" [""ErrorCode""]=> string(12) ""WS_Exception"" [""ErrorMessage""]=> string(22) ""An exception occurred."" [""MemberName""]=> string(5) ""Clear"" } } The webservice appears to be working, responding, searched the KB and have not found much information. Any thoughts are appreciated.

Chris, I wish I could tell you exactly what's going on. Have you done the simple things: 1) restart EBusiness Web Services (IIS) 2) Stop and restart the Sage 100 app server and 3) reboot the Sage 100 server? Chances are pretty good that this is just some transient event and finding the exact cause could be pretty time consuming and not worth it if has only happened once in years.

Thanks for the response. I had tried all those things to no avail. What was discovered by query the activity log was an error #88 in SY_Maint.pvc saying Invalid/unknown property name [Extended Error Information: Type mismatch: 'oSession.AsObject' (err/ret=2/0)]. Well after much thinking and I went into the sales order header/detail and reviewed and found user defined scripts, and wrapped all them in the check for the masui and if it wasn't in the masui don't run the code. An order just came thru the webservice so it may have been a script causing it to fail.

Well done! That had to have been hard to figure out, but it makes sense. Just make sure you're not excluding execution of scripts that are intended to execute in the bus object only. I'm sure you've already taken that into consideration. This is a good tidbit of information to store away.