Cannot expand Microsoft Exchange On-Premises - exchange-server-2010

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.

Related

Error-Not enough storage is available to process this command When changing App Pool Process Identity

Running IIS 7.5 on Win2008. Trying to change the App Pool Identity to Administrator user. When I click OK on the dialog, I get this error: "Not enough storage is available to process this command. (Exception from HRESULT: 0x80070008)
I have tried IISRest and also Restart the sever But issue didn't fix.
Below is the error from Event Viewer
An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by EDC2010-TEST\SPDatabaseConfig, in the OWSTIMER (1172) process, on machine EDC2010-TEST. View the tracing log for more information about the conflict.
Try to re-install IIS by using the server manager. According to Microsoft, this is a machine key corruption issue, which is used to encrypt and decrypt application pool identity credentials.
https://forums.iis.net/t/1180041.aspx
This is a Microsoft system-level problem, namely running out of interrupt request stack space, which can be fixed by making a registry change to allocate a larger IRPStackSize. It is discussed in the below link.
https://support.microsoft.com/en-us/help/106167/error-message-not-enough-server-storage-is-available-to-process-this-c
https://appuals.com/fix-not-enough-storage-available-process-command/
Feel free to let me know if there is anything I can help with.
This has solved the problem for me.
So I had a similar error and I could not find a resolve in any forums.
I'm using the "WMI Provider Host" to edit bindings in IIS using VBScript.
Anyways after trying a few suggestions such as netsh http delete sslcert ipport=0.0.0.0:443 Here and editing the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters > IRPStackSize Here.
I noticed when running my application the "WMI Provider Host" was getting to ±512MB in the ram and found that C:\Windows\System32\inetsrv\config\applicationHost.config was well over that size.
That's when I found this link to increase the memory allocation to the service.
Hopefully it helps.

NuGet feed in Azure DevOps is not accessible anymore (TF246017 / TF30040)

I recently activated the new URL in Azure DevOps, moving from
https://xxx.visualstudio.com/
to
https://dev.azure.com/xxx
Consequently, the address to my NuGet feed also changed:
https://{xxx.pkgs.visualstudio.com/_packaging/feed.xxx.ca/nuget/v3/index.json
to
https://pkgs.dev.azure.com/xxx/_packaging/feed.xxx.ca/nuget/v3/index.json
Everything works except for one thing. Now, I am unable to access my NuGet feed (using Visual Studio, Visual Studio for Mac & Rider). I end up with the following error:
Attempting to gather dependency information for multiple packages with
respect to project 'iOS', targeting 'Xamarin.iOS,Version=v1.0' Unable
to load the service index for source
https://pkgs.dev.azure.com/xxx/_packaging/feed.xxx.ca/nuget/v3/index.json.
If I type the address in a browser, I get the following error:
{"$id":"1","innerException":null,"message":"TF246017: Azure DevOps
Server could not connect to the database. Verify that the instance is
specified correctly, that the server that is hosting the database is
operational, and that network problems are not blocking communication
with the
server.","typeName":"Microsoft.TeamFoundation.Framework.Server.DatabaseConnectionException,
Microsoft.TeamFoundation.Framework.Server","typeKey":"DatabaseConnectionException","errorCode":0,"eventId":3008}
Question
How do I fix it?
Update #1
There is a similar error described in this SO question. I am not using a proxy server.
Update #2
I am not seeing this error message when accessing the index.json:
{"$id":"1","innerException":null,"message":"TF30040: The database is
not correctly configured. Contact your Azure DevOps Server
administrator.","typeName":"Microsoft.TeamFoundation.Framework.Server.AzureClientIPRestrictedException,
Microsoft.TeamFoundation.Framework.Server","typeKey":"AzureClientIPRestrictedException","errorCode":0,"eventId":3007}
I posted the same question developercommunity.visualstudio.com and got it fixed. It was due a problem on Microsoft's side as shown on the dev.azure's status page.

Azure Classic VM. How to fix Error: "We couldn't complete the updates. Undoing changes. Don't turn off your computer."

An automated Windows update this morning left my Windows Server 2012 R2 Classic Virtual Machine on Azure in a semi-crashed state. The VM is a web server, and all the files and applications in it are still accessible via the browser. In other words, IIS and a number of other services are still running. Unfortunately, however, the VM is not accessible via Remote Desktop and is unresponsive to commands from the Azure management interface on the portal.azure.com website.
This type of error is quite common and can be found reported on many other websites. The error has been happening to Windows users (not just Windows Server) for many years already, and none of the solutions online will work for Azure users, because they involve restarting from a CD, pressing shift-f8 during boot, issuing DOS commands, restoring from backup, or unchecking certain properties in VMWare or other software.
Does anybody have a real solution for this problem on Microsoft Azure?
After struggling with this for weeks, I think I was able to fix this with the help of Microsoft support! I decide to post the solution here in case it can help someone in the future. Here are the three things that you need to do to fix this:
1-Restore the VM from a backup prior to the crash. The VM with the "Undoing Changes" crash is pretty much toast at this point. Now, proceed to steps 2 and 3 to ensure that the next batch of Windows Updates won't crash it again!
2-On your new VM, ensure that the Environment Variables for TEMP and TMP both point to C:\Windows\TEMP. In my case, they were both pointing to a temporary folder in the logged in user's profile.
3-Ensure that C:\Windows\TEMP is always empty. I achieved this by setting up a scheduled task that runs a simple BAT file that deletes all files and folders inside of the C:\Windows\TEMP once a day. I spoke with a Microsoft representative who said that even though you may have plenty of hard drive space in your C:\ drive, the Windows TEMP folder is really not supposed to get much bigger than 500MB. When it gets very large you may have some issues with Windows Updates (mine was just under 500MB when the updates were failing).
I would recommend contacting Azure support as something may have to be done by an engineer to fix the issue and unfortunately classic VMs don't have the redeploy feature.
I've added only InboundPort 3389 RPD, and works well now.

Unable to access IIS Metabase

I have Visual Studio 2013 and a pretty basic MVC web application.
When I am connected to my work network (hard wire or VPN) I can open up VS without issue. However when not connected to my work network I get the following error:
---------------------------
Microsoft Visual Studio
---------------------------
Creation of the virtual directory http://localhost:54156/ failed with the error: Unable to access the IIS metabase. You do not have sufficient privilege to access IIS web sites on your machine.
---------------------------
OK
---------------------------
I've tried granting my user rights to IIS via the aspnet_regiis -ga mydomain\myuser and that did not help.
I am certainly running VS as an administrator. It works just fine when connected to the network. Our security and server teams do not seem to understand why this would behave this way.
Is this IIS Express? I (and those I work with) often get a similar error due to the domain login script encrypting My Documents. It's fixed by simply decrypting
Documents\IISExpress\config\applicationhost.config
Not sure if that's the issue here though;
Ultimately I believe this to be an issue between our network policies and the IIS and .NET installs.
When I was off network it could not access the cached user folders. Switching from having the home drives on network to having them local did not fix the issue (assuming some files were still referencing the network location).
I had my system refreshed and started with my user folders as local and have not had the issue since.
I know it's an old question, but at my location the user profile is stored on the network. When I checked to see if the IISExpress application was encrypted as Chad Schouggins suggested, I didn't even have a documents folder. Ultimately, the answer was really simple:
turn the machine off and back on again.

Keyset does not exist / Identity invalid

Note: I've found several questions similar on here, but the one's that were resolved did not work for me. So I thought I'd open a new question.
I rebooted our server 2012 box, which hosts our new .net applications. After doing so, I started receiving a 503 error. Upon investigation, it seemed like an identity problem.
Before going much further, I should state that this account has worked for several months now. I've rebooted before, and everything started fine.
So I'm getting the (quite common) 5059, 5057, and 5021 errors in the log. They boil down to this:
The identity of application pool SVFileUpload is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request. If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.
I thought I would just ensure the password and account were correct, so I go to the application pool, select identity-> custom and ensure it's set up right. I get an error:
There was an error while performing this operation. Details: Keyset does not exist (Exception from HRESULT: 0x80090016)
This was strange to me, so I tried setting the app pool to a built in account, and it worked fine. I get this error anytime I try to set to a custom account. Also, no app pools that are using custom accounts will run.
I googled a bit, unsure which error was the one I needed to track. I have tried:
registering the account on the command line via the aspnet_ tool
Making sure the user was in the IIS_IUSRS group
changing the permissions on C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys file(s)
adding a completely new user and trying to set an app pool to that users account
There was a couple other random things I tried from googling but I don't remember.
This error doesn't make sense to me, and it seems random. I need help figuring out 1) why I can't set an app pool to a custom account and 2) why the identity isn't working for my applications anymore
-Edit
I recently removed and re-added the user account I've been working with. I think that solves that problem. The problem remaining is I can't update the application pool because of the "keyset does not exist" error.
I found a couple of links that led me to a solution.
In c:\windows\system32\inetsrv\config\applicationHost.config I removed all the configProtectedData entries.
Then I removed everything in %ALLUSERSPROFILE%\Microsoft\Crypto\RSA\MachineKeys
I ran iissetup.exe /install SharedLibraries from the inetsrv directory, which resulted in a "Failed = 0x80070005"
I then was able to set up my application pools as if nothing happened.
See also https://techcommunity.microsoft.com/t5/IIS-Support-Blog/Keyset-does-not-exist-exception-from-HRESULT-0x8009000D-or-or/ba-p/342955 for a more detailed explanation
I ran the iisreset command and my problem was sovled
I had the same error-message because my user was not member of the "Local Administrators" group.
I was able to connect to the server because I was member of the "Remote Desktop Users" group.
I was able to open IIS Management and to change settings, but when I clicked on the "OK" or "Save" button - I got the "Keyset does not exist" - error message.
So my advice - check if you are an administrator.
I tried to change the Identity of Application Pool on a remote server and it failed with the above error.
I RDP into the remote machine and then tried to update the Identity using local IIS Manager and it worked.
For anyone on Windows server 2008 stumbling into this error:
this may occur when you are managing the IIS instance from another server using the remote management feature ('connect to another computer').
I resolved by managing the IIS instance from the server itself.
https://support.microsoft.com/en-hk/help/977754/-keyset-does-not-exist-error-message-when-you-try-to-change-the-identi
Since I am working on a fresh server I was able to uninstall the IIS Windows Feature and then re-add it.
I was able to change the App Pool Identity after that with no issues.
delete the rsa found here C:\Users\usernamn\AppData\Roaming\Microsoft\Crypto\RSA
MAKE A BACKUP JUST TO BE SURE WORKED FOR ME

Resources