23Kev
commented
6 years ago Turns out this is an environmental issue. Worth calling out that this is sensitive to authentication configuration. We had a couple of missing SPN's that needed to be reviewed.
Open 23Kev opened 6 years ago
23Kev
commented
6 years ago Turns out this is an environmental issue. Worth calling out that this is sensitive to authentication configuration. We had a couple of missing SPN's that needed to be reviewed.
tsharp
commented
6 years ago Good to know. Do you know what the specifics of the errors were or the exact resolution?
When creating a new autonumber record to configure autonumbering on any built in entity one of either two errors will occur.
Environment is D365 v8.2.1.176 on-premises. Autonumber solution version is 1.2.0.0. No other solutions have been installed in this environment. All SDK steps and workflows in autonumber solution are activated/enabled. The error occurs in 2 environments (Prod and UAT) but works fine in 2 others (Dev and SIT).
---some info removed as not needed---