MS SQL Server 2014 installation and .NET 3.5 problem.

I was installing MS SQL Server 2014 on Windows Server 2012, and when running installation wizard I ran into following error:net35_install_1

So, my first thought was:

That would be eeeasssy as eating a banana!

know_how _to_fix_it

So I went to the server manager and I ran feature installation from there, and there was a little surprise:

Installation of one or more roles, role services, or features failed.
The source files could not be found. Try installing the roles, role services, or features again in a new Add Roles and Features Wizard session, and on the Confirmation page of the wizard, click “Specify an alternate source path” to specify a valid location of the source files that are required for the installation. The location must be accessible by the computer account of the destination server.

35_failedWell…I didn’t expect that…

thug_lifeSo I engaged uncle Google to that, and what I found was:

https://support.microsoft.com/en-us/kb/3002547

I have downloaded that NDPFixit-KB3005628-X64.exe file, double click on that, CMD window appeared for like a second and disappeared- that was quick!

Tried to run installation one more time – same error…

still_badGoogled a little bit more and found that:

https://social.technet.microsoft.com/Forums/en-US/5a786052-38a1-46f9-add2-e6487bc6a8aa/net-framework-20-and-35-feature-install-fails-on-windows-server-2012-rc?forum=winserver8setup

So firstly I ran a command:

dism.exe /online /enable-feature /featurename:NetFX3 /Source:D:\sources\sxs

That went good, but said I need to enable those features separately – no problemo!

dism1After that I still saw no .net 3.5 installed…

I_will_kill_you

So I have read deeper and actually there was a switch that was needed to be there in the command, the proper one should be:

dism.exe /online /enable-feature /featurename:NetFX3 /Source:D:\sources\sxs /LimitAccess

So I was missing “/LimitAccess” switch, what MSDN is telling under:

https://msdn.microsoft.com/en-us/library/windows/desktop/hh824737.aspx

limitaccess

BTW. I was installing Sharepoint 2013 application on W2k12 later and encountered similar error, so command that worked there was:

dism.exe /online /enable-feature /featurename:NetFX3 /Source:D:\sources\sxs /All /norestart

So, being honest I am not sure what is all about /LimitAccess why it was not working for me previously.

After that, I saw that .net 3.5 feature appeared in the installed features:

windows_feature1And installation of MS SQL Server 2014 also went well 😉

sql_prerequisites

all_done

Check mailbox replication network

Have you even wondering how to check over which network your mailbox replication is running?

Below command allows you to check that easily:


Get-MailboxDatabaseCopyStatus wrodb01 -ConnectionStatus | fl Name,OutgoingConnections,IncomingLogCopyingNetwork

replication_network2

Here is a nice article telling now to deal in a situation when after network outage replication network is suddenly changed to the MAPI one:

http://sparesomeexchange.com/exchange-2010-databases-replicating-over-wrong-network/

Enjoy 🙂

Removing mailbox database, word about arbitration mailboxes, and mailbox move statuses.

I was doing some work on my lab and re-configuring DAG on Exchange 2013, after creating new databases I decided to remove the old ones that were created along with exchange installation. I have moved all mailboxes, also I have checked if any archives are there, but surprisingly I got below error when trying to remove mailbox database through a PowerShell:

This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, public folder mailboxes or
arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database
<Database ID>. To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of
archive mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Archive. To get a list of all
public folder mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -PublicFolder. To get a
list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Arbitration.
To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox
<Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox
<Mailbox ID> -Archive. To disable a public folder mailbox so that you can delete the mailbox database, run the command
Disable-Mailbox <Mailbox ID> -PublicFolder. Arbitration mailboxes should be moved to another server; to do this, run
the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command
Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox.
Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID>
-Database <Database ID>.
    + CategoryInfo          : InvalidOperation: (Mailbox Database 0027173074:DatabaseIdParameter) [Remove-MailboxDatab
   ase], AssociatedUserMailboxExistException
    + FullyQualifiedErrorId : [Server=WROEX13A,RequestId=70a73e2f-b187-4e19-879d-67f6978b2d68,TimeStamp=8/29/2015 5:44
   :21 PM] [FailureCategory=Cmdlet-AssociatedUserMailboxExistException] E6FCD23B,Microsoft.Exchange.Management.System
  ConfigurationTasks.RemoveMailboxDatabase
    + PSComputerName        : wroex13a.zaic12.local

remove_mailboxdatabase2

Same was with Exchange Administrative Center:

remove_mailboxdatabase

I must admit it was a…

Zvet0h

…for me.

I was pretty sure I’ve moved everything:

move_mailboxes

Buuut… after getting into the actual message, noticed it was saying about one thing I haven’t checked – arbitration mailboxes.

More information about arbitration mailboxes can be found on Technet:

https://technet.microsoft.com/en-us/library/dd297936.aspx

This one and many others are really nice described on this blog:

https://justaucguy.wordpress.com/2013/01/25/special-mailboxes-in-exchange-2013/

So after reading the actual error I have moved the mailboxes to a different database and removal worked properly:

move_mailboxes2

giphyWhat you may have noticed are statuses of move requests above. “Finalization”, “Reliquished”, “Cleanup” and “InitialSeeding”, being honest I have never been patient enough to look on those statuses when working on production 🙂

So seeing those I was curios as previously all I remember to see were just a few statuses, decided to check help for that, unfortunately Technet is not explaining those under:

https://technet.microsoft.com/EN-US/library/3f8aa1a6-ed8c-4220-9cc7-dd615203f5c5%28EXCHG.150%29.aspx

The only statuses described there are:

movestatuses_technet

InitialSeeding” I guess is the first status that move is getting after being “Queued“, later status might go to “InProgress“, “Finalization” I guess is something that happens just after “CompletionInProgress” and “Cleanup“.

Here we can find even some more…:

http://exchangeserverpro.com/moving-exchange-server-2013-mailboxes/

…like “CopyingMessages” or “LoadingMessages“.

Status “Reliquished” was received while restarting “Microsoft Exchange Mailbox Replication” service (MRS) whilst mailbox was queued, or maybe I thought it was queued but changed to “InProgress” just a second after I checked that (or maybe I was just a little bit impatient :P)

Anyway, would be great if there was as article with explanation for each step within the move mailbox operation, also with those that have been mentioned here as we see that Technet is missing some of these.