This usually occurs when multiple Solomon business rule violations are encountered.
There is a builtin-debug mode that will log the errors to a .txt file on the server. This is usually kept turned-off for performance reasons.
To temporarily enable debugmode logging:
On the web services server: (Where the CTAPI is installed)
1. Edit the following file in notepad:
b. Change the following application key (at the bottom) from FALSE to TRUE
i. <add key="debugMode" value="FALSE"/>
ii. <add key="debugMode" value="TRUE"/>
2. That will enable logging of the order processing service. This writes output to the log file path specified in the "errorLogFile" application key:
ex: <add key="errorLogFile" value="C:\\Inetpub\\OCData\\OPerrorLogFile.txt"/>
b. Open the logging output file in notepad
i. Clear any existing data and save and close the file.
c. Try to place the order that is running into the problems via a webbrowser.
d. Re-open the logging output file.
i. Look for any instances of:
1. RaiseBusRuleViolation or
2. Message -
ii. You should see the relevant business rule violation in there
1. Ex: Message - The header salesperson ID is required.
3. Make sure to Re-edit the web.config file and disable debug mode.
b. Change the following application key (at the bottom) from TRUE to FALSE
i. <add key="debugMode" value=”TRUE"/>
ii. <add key="debugMode" value="FALSE"/>
a. Paths above are just examples and may be different than
b. The web application (Network Service user) by default must have write access to the errorLogFile path specified in the orderProcessing web.confi