We have 8 Exchange 2016 servers with version CU22, KB5007409.
On 2/17 we started getting reports that users could not connect to the ECP portal.
On further investigation I found that if I used the server's url (https://server-01/ecp) and connected to the server from my computer it worked for 4 servers and failed for the other 4 (Tried from Different computers and different browsers - Same issue). I know that this was working for all 8 servers.
If I remote into any of the problem servers and run the ECP Portal locally it works.
The error message is "Something went wrong. We can't get that information right now. Please try again later".
I just discovered that If I use https://server-01/ecp/?ExchClientVer=15 on the problem server that works. How do i get this fixed so that navigating to https://server-01/ecp/ works.
There were no updates to the server since Nov 21 and no changes since.
We ended up opening a Microsoft case.
It appears that the Exchange patch we had deployed at the end of 2021 caused the problem on some of the servers which were in a different region - A redirection issue.
We just installed the Jan 2022 patch and that fixed the issue.
https://support.microsoft.com/en-gb/topic/owa-redirection-doesn-t-work-after-installing-november-2021-security-updates-for-exchange-server-2019-2016-or-2013-9dc8f203-351e-4527-b9b6-794a2c947d44
Is there a more detailed exception message on the ECP available?
Did you try run UpdateCas.ps1 on the affected server ? Consider to do this in off times as the IIS is temporarily unavailable while the script is executing.
Related
I've got an simple asp.net core 2.2 API. It is configured to deploy to azure as soon as we check-in into the master branch.
Azure devops release pipeline is configured to deploy it to an staging slot first. Then it does an smoke web test (by going to one end-point) and if that is successful then it swap the slot with production.
When the slot is swaped it does the same smoke web test (by going to the same end-point on production) to check if it still works. A lot of times i then get an HTTP Error 500.30 - ANCM In-Process Start Failure.
Deploying the same build again fixes this problem most of the times. But i cannot find any logs or details why this error occurds and how to fix this.
Any idea how to debug an HTTP Error 500.30 - ANCM In-Process Start Failure on a Azure Web App?
Turns out Azure has an internally known (I guess they are not eager to share the news about this) problem with 'Application Insights'.
So turn that feature off (if it's on), and see if it solves the issue. That step solved the problem for me.
I had the same error with an Azure ASP.Net Core 2.2 that was running fine for several weeks and suddenly started generating this error from Oct 15 to Oct 17.
Microsoft tech support folks tried to help for a couple of days but they couldn't figure out why the stdout logs were blank. Then, after 2 days, it turned out that it was a known problem on Microsoft's side and they promised to fix. Indeed, after about 8 hours the application started working again (no change or redeployment of the application on my side!).
I asked for an explanation but they told me it was too sensitive.
Today, after 2 weeks of working well, the same application is back to showing the same exact error: "HTTP Error 500.30 - ANCM In-Process Start Failure"
So, most likely, the problem is not in your code or deployment procedure. Instead, the problem is Azure (perhaps how they provision the .net core 2.2 runtime). But for some odd reason Microsoft is not willing to share the details of the problem with their user community (or permanently solve it). Very disappointing!
I installed Microsoft Exchange 2010 SP3 on Windows Server 2008 R2 successfully but when I try to expand the Microsoft Exchange On-Premises the initialization fails with the error
Initialization Failed
The following error occurred when retrieving user information for 'Domain\User': The operation could not be performed because Domain\User could not be found.
Initially I thought it to be the issue related to KB982639 but that doesn't seems to fit here, other then this I have no clue to what the issue could be.
Any lead is appreciated.
Well, such issue is probably due to the same SID of the domain machines or the AD/DC and one of the machine or all of the three. For me when I faced this issue the problem was that I cloned all the 3 machines from the VM Template and did not run sysprep properly which caused the conflict. As the AD recognizes the machines from SID it couldn't recognize the machine and this could not retrieve the user information causing the "Initialization Failed".
Solution
Run sysprep on all the 3 machines with generalize option checked. sysprep can be found in C:\Windows\System32\sysprep\. Unfortunately, you have to destroy the current setup you have as you have messed up with the user info in Active Directory.
We have been using servicestack version 3.8.5.0 for a few years.
We noticed an occasional error where one of the web services returns 404. This service is part of an assembly where the other webs services all work.
This service has not been modified for a number of years and if we restart IIS the service works as expected.
Any ideas where to look on what might have caused the 'registration' to fail?
Edit:
Just found that this issue happens consistently on rebooting the server. So if I restarted IIS a number of times and I do not see the issue. However on rebooting our server, the issue appeared.
I've been successfully using Azure for months. Today I'm getting the following error when I publish from via Web Deploy from Visual Studio 2013
Error 5 Web deployment task failed. (Could not connect to the remote computer ("waws-prod-hk1-001.publish.azurewebsites.windows.net"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.)
I tried downloaded a new Publishing Profile from the Azure Dashboard and turning off my firewall - no change.
I can't ping the listed server.
It seems to be the same issue as http://social.msdn.microsoft.com/Forums/windowsazure/en-US/83d4e635-2851-4526-b21b-31101d00aa86/web-deployment-task-failed-errorcouldnotconnecttoremotesvc?forum=windowsazurewebsitespreview
Any ideas? Thank you.
I had the exact same problem for a couple of days (sometimes I could published and sometimes not).
The problem was my internet configuration (not related to Microsoft or Azure in anyway).
To solve this issue I disconnected my modem (its actually modem+router) for 10 min and reconnect it and it was fixed!
Hope it will help someone someday...
Nevermind. It would appear that Azure was in a 'challenged' state.
It's working fine now..
What worked for me was disabling and re-enabling my network adapter.
The reasoning is, quite possibly naive, that having Fiddler running during a deployment will fail but it also changes the network state and that state continues
to exist even after exiting Fiddler (which disables the proxy).
I just started receiving this error in Visual Studio 2012 while trying to check in my project to VisualStudio.com . I don't know what is causing it, I have tried rebooting the computer but it has not solved the problem. Has anyone ever seen this before?
I am using the Team Foundation Service Preview.
C:\Users\rjs3261\Documents\Visual Studio 11\MvcApplication2\MvcApplication2\MvcApplication2.csproj: The server encountered an unknown failure: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
The Team Foundation servers are down, you can check the status here:
http://www.windowsazure.com/en-us/support/service-dashboard/
And here is my source:
http://blogs.msdn.com/b/tfservice/archive/2013/02/22/service-interruption-2-22-2013-update.aspx
I am getting the same error. Tried to check-in for the past couple of hours and every attempt results in this error.
There is a forum response on tfs.visualstudio.com. Looks like there is an Azure storage problem that is causing the issue.
http://social.msdn.microsoft.com/Forums/en-US/TFService/thread/00965fe0-462e-4b73-8894-b263bbd25642
I also found the hosted TFS status dashboard: https://tfs.visualstudio.com/en-us/support/current-service-status