Hello!
I am checking the server manager log to help diagnose server issues. In my watching, I have noticed a couple Severe errors that I cannot find help with addressing.
We are on 10.8.
Message:
Exception in Put(): 31152 Put exception: the client id 31152 already has a value Attendance/MiddleAttendance_2021_2022.MapServer31152 checked out.
Code: 393939
Method Name:
DynamicServiceCache::GetService
I also receive the same code/method name with an Exception in Get().
Then it will follow with warnings and severe for the "System/DynamicMappingHost.MapServer"/Error code: 8001
Any help will be greatly appreciated!!
Heather.
Hi @HeatherHamilton,
So a put command is where you write data to a attribute, so it is saying that it can not edit the attribute because some one else is working with it, I think this will occur in a versioned database.
Kind Regards
Henry
Thank you!!
I see the exact same errors in my log files. But I also get a message that the layer is not versioned:
"supportsOidReservation = false; Layer: NstBeskyttedeKulturspor_flade. It is not registered as branch versioned or is not connected to a branch versioned workspace."
Do you know why one service gets to "check out" another one, as this is how I understand the Get() error, after which i also receive the above mentioned Put() and 8001 error.
Exception in Get(): _GetItemIterator exception: client id 48308 is trying to check out autonom/NstBeskyttedeKulturspor_flade.MapServer but it already checked out ekstern/BiologiskeAnbefalingerKU_AU.MapServer48308
I hope you can point me in the right direction.
Best regards
Sarah
Hi,
we have the same issue here.
Any news about this problem?
Regards
Oliviero
Our organization is also seeing this issue. Has anyone found a resolution?
Our organization is also receiving this error on our 10.9.1 deployment on a map service. This seems to coincide with all of the layers disappearing from that service.
Anyone find a solution to this? I, too, am seeing these errors. I am able to edit data and sync back but these errors keep coming up.
Hi all! This never got resolved. The best I can tell you is that I worked with ESRI and upgraded from 10.8.0 to 10.8.1. This has helped with the performance....
Thank you!
I'm on 10.9.1 and am still having these errors. The performance is just OK.