Error when trying to create/update tickets in new service (Onsite 10.2.9)

lock
push_pin
done
Beantwortet
1

Hello, one of our customers have a problem with the new service in an onsite enviroment, everytime when they try to save a ticket in the new service does the creation fail and they´ll get this error.

MicrosoftSQL Server Native Client 11.0SQL ServerThe conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.

They can still create new tickets in the old service.

We tried the database on our local machine (We tried creating and updating tickets in the new service), and it worked there which was why we first thought it might have to do with user permissions.

We also thought this had to do with user permissions since we could get the ticket list but not create or update tíckets so we tried adding a new copy of the database with new user permissions but that had no effect.

We have also tried installing a new Sales&Marketing endpoint but that has not worked out aswell.

We have verified that the versions are correct in the SM/CS and the database.

There is also another issue when you first try to load in the tickets which generates a 403 error.

Onsite Error
But when you choose a ticket in the list, the ticket information shows up fine.

Have anyone else encountered these problems before?

Regards
Fredrik

8. Jan. 2024 | 12:59 PM

Alle Antworten (1)

Difference between the old service client and the new request functionality is that the new request functionality goes through NetServer for retrieving tickets/saving tickets, the old service client does not.

Few questions based on the issue your described:

- ServerSetup has been ran correctly and all dictionary steps have been performed? (you can check in the productversion table)

- Both NewServiceRequest and NewTimezoneHandling feature toggles are enabled for all netserver installations?

- NetServer can communicate with Service correctly? (Things like CRMScript triggers do work in CRM?)

- Do you have any date/datetime extra field configured on ticket level that is required? or missing a default value setting?

- If you click open the response object of the Axios error, there is propably some more information there

- Anything logging in the CRM.Web log folder?

 

 

8. Jan. 2024 | 01:12 PM

Antwort hinzufügen