Translate

donderdag 3 juli 2014

Exchange diagnostic error 1006

Every quarter of an hour it's bigtime the 1006 diagnostic error appears in our log files.

What does it do en why it's bothering my eventlog with this message.

The drive space checker is checking if enough drive space is left to function. If it's getting full the database is getting dismounted before corruption could happen to it. Also the mailflow will be stopped.

Always separate the log files from the database, also a best practice from Microsoft will help.

But back to the logfiles messages. Why does it happen? It's malfunction from Microsoft that should be fixed with the first CU..... But you guess it right, they didn't fix it.

Even with CU 5 installed it ain't fixed.

Hereby the errors:

Log Name:      Application
Source:        MSExchangeDiagnostics
Date:          6/02/2014 03:24:01 PM
Event ID:      1006
Task Category: Triggers
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER.DOMAIN.local
Description:
The performance counter ‘\\SERVER\LogicalDisk(HarddiskVolume2)\Free Megabytes’ sustained a value of ‘108.00′, for the ‘15′ minute(s) interval starting at ‘6/02/2014 3:38:00 AM’. Additional information: None. Trigger Name:DatabaseDriveSpaceTrigger.

Instance:harddiskvolume2
Log Name:      Application
Source:        MSExchangeDiagnostics
Date:          6/02/2014 2:55:49 PM
Event ID:      1006
Task Category: Triggers
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER.DOMAIN.local
Description:
The performance counter ‘\\SERVER\MSExchangeIS Store(Test 2 MBX Database)\Logical To Physical Size Ratio’ sustained a value of ‘0.00′, for the ‘10′ minute(s) interval starting at ‘6/02/2014 3:45:00 AM’. Additional information: None. Trigger Name:DatabaseLogicalPhysicalSizeRatioTrigger. Instance:test 2 mbx database


So you choose:

Disable it and take care of enough drive space yourself or let it happen and fill up your logs/disk.

Disable steps:

  1. Go to the path C:\Program Files\Microsoft\Exchange Server\V15\Bin
  2. Locate the Microsoft.Exchange.Diagnostics.Service.exe.config file and open it with Notepad
  3. Locate the line that starts with “<addName="Microsoft.Exchange.Diagnostics.Service.ExchangeJobs.Triggers.DatabaseDriveSpaceTrigger"  and at the end of the line you will see Enabled=”True”.  Change it to be Enabled=”False
  4. If you have the second error above then also locate the line that starts with <add Name="Microsoft.Exchange.Diagnostics.Service.ExchangeJobs.Triggers.DatabaseLogicalPhysicalSizeRatioTrigger" and change the Enabled=”True” to Enabled=”False”
  5. Save the file
  6. Restart the Microsoft Exchange Diagnostics service and the errors should be gone.


dinsdag 20 mei 2014

Installing MUI and OMUI on your server, after reading it's simple

It was quite hard to get all the info from Microsoft to install MUI and OMUI for Office.

But after a while it installed and ran!

First download and copy all the LP files to a network share.

Then copy in the next line to proceed:

lpksetup /i cs-cz de-de es-es fr-fr nl-nl /r /s /p \\Servername\Systemlangpacks

The desired languages, que them like above. If you need other languages just change the phrases fr-fr to the desired language.



For Office it ain't that hard too.

Open Notepad++ or any other textr editor, copy and paste the text below. Save it as czech.xml for example. If other languages are needed just change cs-cz to en-us or whatsoever you need.

For Office:   OMUI.**-**
For Project: PMUI.**-**
For Visio:    VISMUI.**-**

<Configuration Product="OMUI.cs-cz">
 <Display Level="basic" CompletionNotice="no" SuppressModal="no" AcceptEula="yes" />
 <Logging Type="verbose" Path="%systemroot%\Temp" Template="Microsoft_Office-Multi-Language-Pack-2010.log" />
 <AddLanguage Id="cs-cz"/>
</Configuration>

In the script the're some commands for detailed view like "Display Level= none, basic or full" The rest is "yes" or "no" for some troubleshoot reasons you can set SuppressModal to no like above. If all is running you can set it back to yes.

The same step for DisplayLevel to none. But sometimes you want to see what's going on. But when you know it works shut it off. The most things you want to install run silent ;-)

The command to kickoff the languagepacks is: (below command is splitted due screen width limitations, just divide the command with a space and paste it in a command prompt.)

\\servername\Office_2010_langpacks\setup.exe /Config \\servername\Office_2010_langpacks\czech.xml

For example it's czech again, edit the command to run a XML wit another language.

Don't try to stack the installation, the command can only run once per language. After the first is finished, kickoff the next one.


vrijdag 17 januari 2014

Inplace upgrade server 2008 R2

Inplace upgrade Server 2008 R2 to Enterprise or Datacenter Edition

Hereby some steps to upgrade the server version 2008 R2 from Standard Edition to Enterprise or Datacenter Edition.

If you're using VMware just create a snapshot before the upgrade process, while the VM is offline is the advise. If the VM is holding some application that needs consistency power it off. The advise for AD/SQL/Exchange/DFRS is do not roll-back you destroy the data.

You can process the upgrade while the VM is online, after the upgrade a reboot is needed to apply the just amde changes.

Open up a elevated Command Prompt:

DISM /Online /Get-CurrentEdition

Aboven command will show you the current version.

This will return
http://richardstk.files.wordpress.com/2012/04/online-server-2008-r2-upgrade-11.jpg
 In the same box type: DISM /Online /Get-TargetEditions

This will give you the output of the versions where you can go at.

http://richardstk.files.wordpress.com/2012/04/online-server-2008-r2-upgrade-21.jpg

Choose the desired Server Edition and proceed with the next command:

DISM /Online /Set-Edition:ServerDataCenter /ProductKey:xxxx

 If you use KMS from Microsoft, type in the KMS key on the xxxx.

Enterprise 
489J6-VHDMP-X63PK-3K798-CPX3Y

Datacenter

74YFP-3QFB3-KQT8W-PMXWJ-7M648





After thse steps the VM will boot and apply the changes, when changes are applied the VM will boot again.

The log in and open up a elevated Command Prompt, if you're using KMS.

Then type:


Slmgr –skms kms.address.you.got.in.dns:1688
Slmgr.vbs /ato