Archive for category Windows Server
OCS 2007 Protocol Stack Error Event ID 14517 When Starting Services
Posted by Sheen in Windows Server on January 15, 2010
You may come across this error message when you install Office Communications Server 2007 for the first time in your environment. This error generally is seen after you run through the initial steps and are trying to start the OCS services for the first time.
This event ID will contain the following message:
ERRORS:
Two server roles at FQDN [server.domain.com] have different ‘Treat As Authenticated’ options. First server has GUID {58BDE507-1C48-4BA4-BCDF-06FB59ADF9CE} and role ‘Enterprise Edition’ (option is set). Second server has GUID {BD77F03B-4451-4171-A035-FC7FB264383D} and role ‘A/V Authentication Service’ (option is not set). Two server roles at FQDN [server.domain.com] have different server version numbers. First server has GUID {58BDE507-1C48-4BA4-BCDF-06FB59ADF9CE} and role ‘Enterprise Edition’ (version 3). Second server has GUID {BD77F03B-4451-4171-A035-FC7FB264383D} and role ‘A/V Authentication Service’ (version 0). Two server roles at FQDN [server.domain.com] have different ‘Treat As Authenticated’ options. First server has GUID {58BDE507-1C48-4BA4-BCDF-06FB59ADF9CE} and role ‘Enterprise Edition’ (option is set). Second server has GUID {1719A023-DDB4-5170-836D-3299D4F067C6} and role ‘Edge Server’ (option is not set). Two server roles at FQDN [server.domain.com] have different server version numbers. First server has GUID {58BDE507-1C48-4BA4-BCDF-06FB59ADF9CE} and role ‘Enterprise Edition’ (version 3). Second server has GUID {1719A023-DDB4-5170-836D-3299D4F067C6} and role ‘Edge Server’ (version 0).WARNINGS:
No warningsCause: The configuration is invalid and the server might not behave as expected.
Resolution:
Review and correct the errors listed above, then restart the service. You also wish to review any warnings present.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
This error can be misleading. The primary reason you see this error is simple – You have had a previous installation of OCS in the domain and there are still a few entries in Active Directory that haven’t been cleaned up even though you did a clean uninstall of OCS.
This is what you need to do to fix the error:
How to Backup and Restore Active Directory
Posted by Sheen in Windows Server on October 7, 2009
There are many documents written about backing up Active Directory but I didn’t find enough documentation that would help us restore Active Directory. So here is a guide aimed to provide insights into correctly backing up and restoring Active Directory.
Here is my mini how to – I have tried to keep it as simple as possible:
Dude, where’s my mailbox stats?
Posted by Sheen in Windows Server on July 20, 2009
One of the most frequently used Exchange 2003 mailbox management administrative features was the mailbox size, total item count, last logon time, log off time etc. For some strange reason, this convenient feature has been left out of Exchange Server 2007. If you are reading this blog then you probably are looking for a way to get these stats back.
The Exchange 2007 power shell is power packed to deal with this drawback and you can get all the info you need (displayed just like ESM 2003) in a jiffy by running this command (you will need to substitute MailboxServer01 with your server name):
Get-MailboxStatistics -Server MailboxServer01 | Sort -Property TotalItemsize | Format-Table DisplayName, LastLoggedOnUserAccount, ItemCount, @{expression={$_.totalitemsize.value.ToMB()};label=”Size(MB)”}, LastLogonTime, LastLogoffTime | Export-CSV ExMBXInfo.csv
All this info would get written to a csv file with the filename ExMBXInfo.csv (Edit the file name in the command if you want to call it something else)
The variables used here are DisplayName, LastLoggedOnUserAccount, ItemCount, TotalItemSize, LastLogonTime, LastLogoffTime. There are a host of other variables that can be used to get more information. Here are some of these variables that can be used:
AssociatedItemCount
Database
DatabaseName
DeletedItemCount
DisconnectDate
DisplayName
Identity
ItemCount
LastLoggedOnUserAccount
LastLogoffTime
LastLogonTime
LegacyDN
MailboxGuid
ServerName
StorageGroupName
StorageLimitStatus
TotalDeletedItemSize
TotalItemSize
Drop me a line if this article helped you!
The WinRoute tool
Posted by Sheen in Windows Server on July 18, 2009
WinRoute.exe is a tool that can be used to view and easily understand a complicated Exchange email routing topology. This tool is a recommended first step towards troubleshooting Exchange Email routing issues.
To install the tool, go through the following checklist:
Exchange 2007 Recreate OWA folders
Posted by Sheen in Windows Server on June 18, 2009
If you face an issue where OWA in Exchange 2007 stops working, there is a pretty cool powershell command you can run to recreate the OWA virtual directory. The following commands will get you going:
This command will list all the current virtual directories.
Get-OwaVirtualDirectory
This command will delete the “owa” virtual directory under the Default Web Site.
Remove-OwaVirtualDirectory -identity "owa (Default Web Site)"
This command will re-create the “owa” virtual directory under the Default Web Site.
New-OWAVirtualDirectory -OWAVersion "Exchange2007" -Name "owa (Default Web Site)"
When you run this command, if you get an error as follows, it is possible that IIS is set to work in the 32 bit mode and not the required 64 bit mode.
New-OwaVirtualDirectory : An error occurred while creating the IIS virtual directory ‘IIS://mailserver.somewhere.com/W3SVC/1/ROOT/owa’ on ‘mailserver’.
At line:1 char:24
+ New-OWAVirtualDirectory <<<< -OWAVersion "Exchange2007" -Name "owa" -Website "Default Web Site"
To make IIS work in the 64 bit mode, you need to run the following command:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
Just in case you do not have the adsutil.vbs script in your adminscripts folder, you can download it from here.
Drop me a line to let me know if this post has helped you!
-
You are currently browsing the archives for the Windows Server category.
Recent Comments