Wednesday, May 26, 2010

Test-ActiveSyncConnectivity - The remote server returned an error: (403) Forbidden

Today I troubleshoot an issue where the test-activesyncconnectivity didn't work.
The following error was given when running the test:

PS] C:\Windows\system32>Test-ActiveSyncConnectivity
CasServer LocalSite Scenario Result Latency(MS) Error
--------- --------- -------- ------ ----------- -----
CASServer Default-Fi... Options Success 15.60
CASServer Default-Fi... FolderSync Failure [System.Net.WebExcept...

With the | FL we can see a more specific error message:

RunspaceId : 64768a1f-b8cc-49cd-bd76-ee70de43c728
LocalSite : Default-First-Site-Name
SecureAccess : True
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 0
ConnectionType : Plaintext
ClientAccessServerShortName : CASSERVER
LocalSiteShortName : Default-First-Site-Name
ClientAccessServer : CASSERVER.FQDN
Scenario : FolderSync
ScenarioDescription : Issue a FolderSync command to retrieve the folder hierarchy.
PerformanceCounterName : DirectPush Latency
Result : Failure
Error : [System.Net.WebException]: The remote server returned an error: (403) Forbidden.

HTTP response headers:

MS-Server-ActiveSync: 14.0
Content-Length: 5355
Cache-Control: private
Content-Type: text/html; charset=utf-8
Date: Wed, 26 May 2010 13:50:19 GMT
Server: Microsoft-IIS/7.5
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET

UserName : extest_3650257c296a4
StartTime : 26.05.2010 15:50:20
Latency : -00:00:01
EventType : Error
LatencyInMillisecondsString :
Identity :
IsValid : True

The reason for this is becase the default ActiveSync Mailbox Policy has been changed and does not support non- provisionable devices.

Solution is to create a new ActiveSync mailbox policy which allow non-provisionable devices and assign this to the extest_3650257c296a4 user.

Tuesday, May 25, 2010

Eventid 200 Database headers have been successfully validated.... Dirty shutdown

Today I've troubleshoot some issues with backup of an Exchange 2010 DAG installation. Some databases were partially backed up according to the backup software (Symantec Netbackup).

I came over the information event:

Source: Storage Group Consistency Check
Event ID: 200
Level: Information
Instance X: Database headers have been successfully validated. All Databases are in a dirty shutdown state. Tobring these databases to a clean shutdown state, log generation xxxxx(0x0xxxx) to xxxxxx (0x0xxxxx) will be required.

As it says this is only for information, and there is no need to be worried and is as expected when the database is online.

When the database is online it has logs in memory or open logs etc. that are not committed yet.

So, don’t worry, this is expected, and this check is done on online backup.

On the other hand, if your database is offline and you get Dirty Shutdown when running eseutil /mh (DBpath+filename) then you might have a bigger issue, and have to do a repair / restore and log replay job.