Mid Web services extension listener is not starting

[sukran]

Mid server extension event listener is struck with starting status , it should be in started

any idea why its struck with starting? it seems it been a day in same status

[AJ-TechTrek]

Hi @sukran 

You should restart the mid server, that can help to resolve your issue, also sometime due to misconfiguration that can be stuck.

Refer the below Article, will help to resolve your issue.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0853579

https://docs.servicenow.com/bundle/vancouver-it-operations-management/page/product/event-management/...

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

[Rahul Priyadars]

How is the Authentication is configured for this mid extension?

I assume mid server is started ? Also please check Mid Server Logs?

Regards

RP

[Doci1]

HI @sukran ,

did you find out what was the issue? Seems I have the same problem... 

[Doci1]

@sukran based on the syslog there is one entry: 

Access Denied. MID user: "mid.ACC-DMMY-1" with MID server role, cannot create an output record with topic: "MIDExtension:WebServerExtension" for agent: "mid.server.ACC-DMMY-1" with name: "Mid Web Server:mid_webserver_ACC-DMMY-1(a7b0e1a887548a10654e33fd3fbb35ef)" ; logged in as: "mid.acc-DMMY-1". 

I couldn't find out to which error it is related to, however my issue was caused by automatical MID serve upgrade and we do suspect, that the MID server user in [sys_user] table was with lower cases letters and on the MID server with capital letters. But it is just an assumption, I cannot simulate that behavior for testing. As I have 5 MID servers for ACC, which are using MID Webserver Extension context and the affected one was the only one with capital letters as username on MID, we made such a conclusion. Hopefuly it will help.