Hi
I got an issue with triggers of an onsite customer.
Whenever I activate a trigger "before saving company" and save a company, the following error occurs:
The IIS log says
2023-01-10 11:41:05 172.18.98.20 POST /SuperOffice/api/v1/Agents/CustomerService/EventHandlerExists - 2525 - 192.168.16.50 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64;+rv:108.0)+Gecko/20100101+Firefox/108.0 https://crm-test.schaerer-surfactants.com/SuperOffice/default.aspx?contact.udef.personarchive.minimonth?contact_id=7523&person_id=4125&diaryowner_id=19 200 0 0 26
2023-01-10 11:41:06 172.18.98.20 POST /SuperOffice/api/v1/Agents/CustomerService/ExecuteEventHandlers - 2525 - 192.168.16.50 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64;+rv:108.0)+Gecko/20100101+Firefox/108.0 https://crm-test.schaerer-surfactants.com/SuperOffice/default.aspx?contact.udef.personarchive.minimonth?contact_id=7523&person_id=4125&diaryowner_id=19 500 0 0 2081
Other than that, I do not see any error.
Apart from the trigger everything just works fine.
Any ideas?
SuperOffice onsite 10.1.6 (10.1.6.838)
Bset regards, Marc
All Replies (3)
Are the SymmetricKey and Secret setup correctly? (Equal between the web config of the superoffice instance calling service and the config file of the service installation), and the Service installation is internally reachable (for the server running SuperOffice web) ?
Hi Marc,
- Verify that all SymmetricKeys/SymmetricSecrets are the same in all config-files, don't forget the BatchService-files as well. At least the NetServer used for Service needs to have the same encrypted keys as the Service config-file, to be able to communicate correctly. But my best practice is to use the same for all components, to be sure. In my experience, this is the main source of failing triggers in onsite-environments.
- If the solution is using WinAuth, verify that you have added the needed extra config settings in the config-file for all Net Servers, according to the docs, see below.
https://docs.superoffice.com/en/online/identity/single-sign-on/onsite-sso.html#superoffice-service
Hi David, hi Markus,
thanks for these hint. And yes, the keys of web config of superoffice application and config of service application are identical.
The solution does not use WinAuth either.
However, there was a mapping of 127.0.0.1 to crm-test.schaerer-surfactants.com (the external name) present in the servers hosts file. After I removed the mapping, trigger work fine.
There is a reverse proxy taking care of rewriting the external name crm-test.schaerer-surfactants.com to the IP address of the server.
Best regards
Marc