After the upgrade to CU3 on all my Exchange Servers, some of the end users started complaining about username and password popups. Password was entered but the box kept on appearing.
Check credential manager and all seemed fine. I then went and had a look at my Exchange Server. After running the command: Get-OutlookAnywhere I noticed my main server had the correct settings but the rest were mixed with Basic, Negotiate and NTLM.
I removed Negotiate and set them all to Basic,NTLM and ran an IISReset on each server. After this all outlook clients connected fine. Here is the command:
- Set-OutlookAnywhere -Identity ‘<ServerName>\rpc (Default Web Site)’ -IISAuthenticationMethods Basic,NTLM
Hope it helps!
Today I upgraded all my exchange servers to CU3. All of them went well except for one. The transport service started and stopped after 1 minute and would log 3 event errors straight after each other:
The main error was complaining about one of my custom connectors. After that error another error 7001 logged with a TCP/IP error.
I removed the custom connector that worked on CU1, CU2 and CU2v2 and started the Exchange Transport Service, this time it started and did not log any of these errors again.
Hope it helps
Today MS released the much awaited CU3 for Exchange 2013. The download is 1.5GB almost as big as the previous versions. The major fix/factor here is the calendar forwarding issue that MS say has been fixed that was a problem with the release of CU2 and CU2v2.
Lets start. First I will put one of my Exchange Servers in Maintenance Mode. Best practice as I have seen if you don’t do this DAG copies give problems. Here are the 4 commands I will be running. You can make this a PS1 script but I like making sure each command has successfully completed. Start Maintenance Mode:
- Set-MailboxServer <Server Name> -DatabaseCopyActivationDisabledAndMoveNow $True
- Set-ServerComponentState –Identity <Server Name> –Component HubTransport –State Draining –Requester Maintenance
- Suspend-ClusterNode –Name <Server Name>
- Set-MailboxServer –Identity <Server Name>–DatabaseCopyAutoActivationPolicy Blocked
(**You need to open up the Exchange Management Shell as Administrator or point 3 will give you a permission error**)
Now we need to first prepare the Schema and AD before we can proceed with the installation.
From an elevated prompt you can run the following commands:
- Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
- Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
(**Note you need to have RSAT tools installed to prepare AD etc. You can do so by running the following command from the Exchange Management Shell: Add-WindowsFeature RSAT-ADDS)
Once both commands have run and finished you can now run the Exchange 2013 CU3 setup. It will check for any updates which you can skip and the proceed to the upgrade screen. (Screen captures included below)
Now that the setup has completed we need to take the server out of maintenance mode to resume normal operation. We need to run 4 commands again to Stop Maintenance Mode:
(**Remember you need to run these commands as an administrator from an elevated Exchange Management Shell)
- Set-MailboxServer –Identity <Server Name> –DatabaseCopyAutoActivationPolicy Unrestricted
- Resume-ClusterNode –Name <Server Name>
- Set-ServerComponentState –Identity <Server Name> –Component HubTransport –State Active –Requester Maintenance
- Set-MailboxServer –Identity <Server Name> –DatabaseCopyActivationDisabledAndMoveNow $False
Now that everything is online you can check the DAG Status etc.
Hope it helps
Yesterday I did some cleanups and move mailboxes to the new databases I created. I think created Mailbox Copies (More on how to do this: http://technet.microsoft.com/en-us/library/dd335158(v=exchg.150).aspx).
In the event log I started to receive the following warning:
“RPC request to the Microsoft Exchange Information Store service for log truncation failed for database (DB Name). Error: Failed to notify source server ‘Server Name’ about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file.”
This warning will clear with the next full backup of the Database and when all the log files are truncated.
Hope it helps
Yesterday I downloaded System Center Data Protection Manager 2012 R2. I extracted the ISO file and started the splash screen.
Upon clicking the link to install DPM another screen similar to the earlier versions appears and you click next. With this install you have the option to install using SQL local or clustered.
If you choose local it defaults to the SQL instance created by DPM 2012 (unless you changed it)
When I clicked Check and Install the checks run through and then DPM 2012 R2 fails with an error that the SQL instance is not valid.
When I checked the logs I noticed it was complaining about the protocol TCP. I went to SQL Configuration Manager and I got the same WMI error saying it couldnt open. I then opened up and elevated prompt and ran the following:
mofcomp.exe “C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof”
After that I could open up SQL Configuration Manager, I enabled TCP for the SQL instance and then restarted all the services. I then went back to the DPM 2012 R2 install and clicked the Check Again button and voila, DPM 2012 R2 upgraded my existing DPM installation and completed successfully.
Hope it helps.
Last week I upgraded one of my test servers from Windows Server 2012 to Windows Server 2012 R2. The upgrade went successfully except for one service. The SQL Server Reporting Services. I wanted to pull a report and the app I was using reported the service wasn’t started.
I clicked start only to get the famous error that some services stop and start if they have nothing to do. Okay, time to check the logs. Here was the error reported:
Service cannot be started. System.IO.FileLoadException: Could not load file or assembly ‘ReportingServicesNativeServer, Version=126.96.36.199, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ or one of its dependencies. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. (Exception from HRESULT: 0x800736B1)
File name: ‘ReportingServicesNativeServer, Version=188.8.131.52, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ —> System.Runtime.InteropServices.COMException (0x800736B1): The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. (Exception from HRESULT: 0x800736B1)
at Microsoft.ReportingServices.Library.ReportService.OnStart(String args)
Quite a long error. I simply opened up Programs and Features and ran a repair on SQL. After that the service started without any issues.
Hope it helps
Yesterday I downloaded the new System Center Configuration Manager R2 Setup files. I extracted the ISO and started the setup.
Pretty straight forward as SCCM has to download newer updates etc. The Assessment and Deployment Tool kit has to be updated to support Windows 8.1. This download is quite large, didn’t take too long (depending on your connection)
After the Toolkit updated itself I ran the check on the SCCM R2 install and the following error was produced:
“The User State Migration Tool component of the Assessment and Deployment Kit (ADK) 8.1 is required and must be installed before Setup can continue.”
To fix this open up an elevated command prompt and navigate to the ADKSetup file and then execute the following command:
Adksetup.exe /quiet /features OptionID.DeploymentTools OptionID.WindowsPreInstallationEnvironment OptionID.UserStateMigrationTool /norestart
Once you press enter it seems like nothing is happening but the setup is running in the background, give it about 5-10 min then run the checks again on the SCCM R2 Upgrade/Install and the error will be gone.
Hope it helps.
Today I tested an upgraded on my CRM system running server 2012. I first upgraded CRM Dynamics 2011 to RU15, after that I did a restart.
I ran the upgrade from Server 2012 to Server 2012 R2 (Note that CRM Dynamics 2011 is not supported on Server 2012 R2)
After the upgrade IIS issued an error saying that the WSS service was disabled as the server is running IIS 7.5 and not IIS 7.0.
When I checked my site was gone. No sweat, I navigated to the CRM Dynamics folder under programs files and ran the ServerSetup. It gave me 3 options, I chose repair and pointed to the install files. After it had finished I did an IISReset and navigated to the CRM URL only to be met with the following error:
“HTTP Error 500.19 – Internal Server Error
The requested page cannot be accessed because the related configuration
data for the page is invalid.
`Detailed Error Information`
Module IIS Web Core
Handler Not yet determined
Error Code 0x8007000d
Config File \\?\C:\wwwroot\web.config
Requested URL http://localhost:80/Default.aspx
Logon Method Not yet determined
Logon User Not yet determined
Quick check, IIS 7.0 uses the URL Rewrite Module and IIS 7.5 does not. I downloaded the file (http://www.microsoft.com/en-za/download/details.aspx?id=7435) and ran the install, did an IIS reset and went back and CRM Dynamics 2011 was now running fully on Windows Server 2012 R2.
Hope it helps.
Yesterday I ran CU3 upgrade for Lync Server 2013 on my Front-End Server. After the upgrade I noticed that the Front-End Service was stuck starting.
In event viewer the errors were just rolling over like informational alerts. I ran a repair, that did not work. I rebooted again, nothing.
I then uninstalled all components of Lync (You might be thinking where are your backups, I do have them). Rebooted the server and then started the install again. Step 1 was pretty easy as I still had my DB’s. Step 2 became tricky. All prerequisites were satisfied until it came time to install Server.MSI. This is the error I got:
“Lync Server Installation Error. Error installing Server.msi feature (Server.MSI) code 1603”
The error 1603 means a permission error. I verified the account I was running was an Admin account, nothing really changed. Made sure that none of the windows features got uninstalled (you never know with updates). All seemed fine.
I then stumbled across 2 installs that were still sitting under programs and features. Microsoft Unified Communications Managed API. I uninstalled these 2 components, went back to my Lync Server 2013 installation and Server.MSI plus everything else installed perfectly.
I proceeded to Step 3, assigned my Certs and voila, Front-End Service started like a charm and all Lync clients started connecting again.
Hope it helps.