I had a 956 error during the build phase on a Windows dev server. I use the build to make things a bit faster, don’t know if the faster alternatives are already working, so many things to check, so little time 
I reverted from 4.7.2 back to 4.5.0 but the error remained, so it could be a Windows update that is causing this new behaviour.
I looked up the error on the forum and found an article where Todd pointed out that the max API session limit can be changed in C:\Program Files\FileMaker\FileMaker Server\Admin\FAC\config\config.js
I changed “MAXIMUM_API_SESSIONS” to 25 instead of 5 and the build succeeded.
FYI.
Thanks for the report Peter!
That error can happen when too many admin sessions are live. I added some new changes in 4.7.1 which should make this error less likely, but it is difficult to get rid of completely. I will also call out for those who might hit this later that restarting your FMS Admin server will fix the issue temporarily, although increasing the limit like Peter did is the only way to avoid it fully.
I’m on the look out for more ways that OttoFMS can avoid this error, and if you are using the admin API from elsewhere, I will say that using the OttoFMS Admin API proxy will reduce the likelihood of this issue, as OttoFMS manages a single session.
-Kyle
1 Like