HTTP Error 500.37 - ANCM Failed to Start Within Startup Time Limit

Answered
Mahesh asked on April 6, 2022

Hi Flexmonster support team,
We are calling FM dataserver indexes from angular and when ever we are trying to call those indexes we are getting following error.
HTTP Error 500.37 - ANCM Failed to Start Within Startup Time Limit
Common solutions to this issue:
ANCM failed to start after 120000 milliseconds
Troubleshooting steps:

  • Check the system event log for error messages
  • Enable logging the application process' stdout messages
  • Attach a debugger to the application process and inspect

For more information visit: https://*********.scm.azurewebsites.net/detectors?type=tools&name=eventviewer and https://go.microsoft.com/fwlink/?LinkID=2028265
 
 
We tried to increased time also for timeout( using StartupTimeLimit) but still we are getting same only. please provide your suggestions/advise
 
Thanks in advance!

Attachments:
Error.PNG

4 answers

Public
Maksym Diachenko Maksym Diachenko Flexmonster April 7, 2022

Hello, Mahesh!

Thank you for writing to us.

We would like to have more information about this error. Do you see an empty Flexmonster grid on your webpage or Flexmonster error pop-ups? This information would greatly help us to understand the reason of the issue.

Looking forward to hearing from you.

Best Regards,
Maksym

Public
Mahesh April 7, 2022

Yes Maksym, we are able to get error as 500 internal server error and return as above attached error. 
And we hosted FM Data server app in azure. When ever if we go thought the following link we are getting as error (attached also) following
https://*******azurewebsites.net/detectors?type=tools&name=eventviewer
 
Error: the environment block used to start a process cannot be longer than 65535 bytes. Your environment block is 101055 bytes. Remove some environment variables and try again.
 
Do we have any limitations to create few indexes only?
 
Best Regards,
Mahesh

Public
Maksym Diachenko Maksym Diachenko Flexmonster April 8, 2022

Hello, Mahesh!

Thank you for quick response. 

Flexmonster Data Server has no limitations on amount of created indexes. The only limit is your server's RAM, as FDS loads and processes data in an operative memory. To sum up, the Data Server is limited by your server hardware, the performance is mostly affected by the amounts of data processed, not in quantity of indexes.

As for now, our team can not see how the exact reason of an error you are dealing with and how it is related to Flexmonster. The possible reason of this error may be too big amount of environment variables. If you are using the Data Server as DLL, the Flexmonster configurations are stored in appsettings.json file, possibly creating a big amount of indexes there may be responsible in exceeding the env block size limit.

Please refer to this thread we have found on Microsoft forum, it contains the information, which may be helpful in fixing Error: the environment block used to start a process cannot be longer than 65535 bytes. Your environment block is X bytes. error.

We also want to make sure which project you are deploying on Azure:

This would be a great help for better understanding of your case.

Hope you will find this answer helpful. Looking forward to hearing from you.

Best Regards,
Maksym

Public
Maksym Diachenko Maksym Diachenko Flexmonster April 20, 2022

Hello, Mahesh!

Just checking in to ask if you solved the issue with the environment block's size limit. 
Also, could you please let us know what are you deploying on Azure:

  1. Your custom project using FDS DLL.
  2. Custom API data source: https://github.com/flexmonster/api-data-source/.
  3. Our example project using FDS DLL: https://github.com/flexmonster/flexmonster-data-server-dll?

Best Regards,
Maksym

Please login or Register to Submit Answer