www.kreslavsky.com

Error c1038a21 appears when you try to view properties of public folder system folder – Schedule + free busy or offline address book folder

Microsoft have a article on how to fix it , but in there guide they recommend usage of Information Store Viewer (MDBVu32).

I prefer to use PFDAVAdmin that can be downloaded from here it is much easier .

1. Run PFDAVAdmin
2. Press on file>connect
3. Fill your DC settings like on screenshot bellow (don’t forget to select public folders)
   
4. Navigate to problematic folder – schedule free busy for example
   
5. Right click on it and chose “property editor”
   
6. Select PRF_PF_PROXY from property dropdown
   mark clear and press execute.
   

That’s it, that should fix the problem.

• Leave a comment... (0)

• Leave a comment... (3)

• Leave a comment... (0)

• Leave a comment... (0)

Apple Senior VP Phil Schiller shows in a demo, how the iPhone will support Microsoft Exchange

• Leave a comment... (0)

The issue occurs when you are trying to create mailbox for new user using ADUC in Exchange 2003
By Microsoft the reason for the issue is : After upgrade of the forest to a 2003 native mode functional level, the Recipient Update Service may overwrite the value of the homeMDB attribute for new Microsoft Exchange Server 2003 users.

To fix the issue:

1. Open ADSI Edit.
2. Double-click the Configuration container
3. Expand CN=Services
4. Expand CN=Microsoft Exchange,
5. Expand CN=<Your ExchangeOrganizationName>.
6. Click CN=System Policies.
7. In the right pane, right-click CN=Mailbox Enable User, and then click Properties.
8. Scroll down to select the purportedSearch attribute, and then click Edit.
9. Clear the attribute, and then use the following filter to configure the attribute:
   (&(objectCategory=person)(objectClass=user)(mailnickname=*)(homeMdb=*))
10. Click OK .

Solution was been created with the help of the following article:http://technet.microsoft.com/en-us/library/aa998426.aspx

note:You must enter the attribute without any spaces, exactly as it is.

• Leave a comment... (0)

It is a common task in corporate environment

1. You need to open a user with new meeting room name
2. Open new user’s mailbox
3. Go to tools> Options >Calendar options>Resource schedule
4. Mark the sections bellow

That is .

NOTE: In Exchange 2007 there is ability to create resources (Not Users) You can also set the resource capacity now! Eg: in one of your meeting room, only be able to fit 10 people, you can type in resource information, under the property of the object.

• Leave a comment... (0)

Users Not Receiving Messages to Handheld After Mailbox Move

BlackBerry server maps user mailboxes by using a process called worker treads. Blackberry version [4.0.4.5], is capable of mapping worker treads back to a user mailboxes when a mailbox gets moved to a different store by scanning the GAL for changes in the Server DN.BES users may not receive messages to their handheld device after a mailbox move .

After mailbox move the BES server should pick up the new mailbox location and start sending again within 15min.

The only thing you have to watch is moving the BES service account mailbox, Also be sure the BES service account has the appropriate permissions on the new Exchange server Information Store before you start moving user mailboxes, full send as/receive as. I would suggest moving the user mailboxes and then the service account

To move user mailboxes:

Move them as you normally would, use the Exchange mailbox move wizard.

RIM suggests you run the mailbox cleanup utility on the BES server after mailbox move

Restart BES Services:

* Mailbox move within the same server are not updated by BES and messages are not received by BB devices until BES services are restarted. This is because BES scans user’s mailboxes for changes in the Server DN. Since mailboxes are moved within the same server, BES is unaware of the mailbox move.

Using Cleanup Utility:

* Run C:\Program Files\Research In Motion\Blackberry Enterprise Server\Utility\handheldcleanup -u

Move BB Service Account:

* Log in to Blackberry Enterprise Server as the blackberry system account
* Stop all Blackberry Enterprise Server services
* Move the blackberry system mailbox to Exchange 2003
* On the blackberry Server: Go to Start-> Programs-> Blackberry Enterprise
* Server-> Edit the MAPI Profile for the Blackberry Server
* Type “new Exchange server name” in the Microsoft Exchange Server field
* Type “blackberry service account name” in the Mailbox field
* Run Handheld Cleanup utility on BES Server “C:\Program Files\Research In Motion\Blackberry Enterprise Server\Utility\handheldcleanup -m”
* Start Blackberry Enterprise Server service

• Leave a comment... (1)

User can’t receive meeting requests ,updates and cancellations in exchange 2003/2007
However user can send and receive emails.
It can happen if users legacyExchangeDN attribute is wrong.

In order to fix the problem
Open ADSIedit.msc
Open Domains, dc=domain,dc=com , double click on problematic user.
And confirm if parameter ‘/cn=’ after ‘/cn=Recipients’. Is missing

Ms Article regarding Exchange 2007 http://support.microsoft.com/kb/556074
Ms Article regarding Exchange 2003 http://support.microsoft.com/kb/556073

Also yo may need hotfix 913579 if problem is related to recursive meetings.

• Leave a comment... (0)

On errors:

Mapi session “/o=COMPANY/ou=Europe/cn=Recipients/cn=User1? exceeded the maximum of 32 objects of type “session”.

Task “Microsoft Exchange Server” reported error (0×80040115): “The
connection to the Microsoft Exchange Server is unavailable. Outlook must be
online or connected to complete this action.”

Task ‘Microsoft Exchange Server’ reported error (0×8004011d): ‘The server is
not available. Contact your administrator if this condition persists.’

Don’t waste your time on profile recreation … It doesn’t help!!!

Things to check .

1.      Ping to exchange server by short name and FQDN

a. If no ping check connectivity and name resolution.

b. Consider adding exchange name/ip to hosts file

2.      Go to file and check if “Work Offline” is not checked

a. If it is uncheck it.

3.      If you have check point client try to

a. Disable security policy

b. Stop Vpn client

c. Remove checkpoint secure remote “v” on local area connection properties ( do it only for testing – remember if you remove the “v” user will be not able to dial VPN.

4.      Run Outlook.exe with rpcdiag switch “outlook.exe /rpcdiag” see where is hanging

5.      On exchange system manger open user related mailbox store in logons section check if user exceeded maximum of 32 connections to the store.

a. If do : To solve this problem for this user, download the sysinternals tool called TCPView and run it on your Exchange server. You will see a whole bunch of connections. Work out the IP address of user, and then using TCP view terminate all sessions to that IP address.

b. Other option is to mount / unmount store – not recommended

6.      In order to Increase default 32 MAPI connections limit do the following things

a. Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry sub key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem

If the Maximum Allowed Sessions Per User entry does not exist, do the following:

On the Edit menu, point to New, and then click DWORD Value.

Type Maximum Allowed Sessions Per User as the entry name, and then press ENTER.

Right-click the Maximum Allowed Sessions Per User entry, and then click Modify

Click decimal, type the value that you want to set in the Value data box, and then click OK.

Exit Registry Editor.

Click Start, click Run, type services.msc in the Open box, and then click OK.

Click the MSExchange Information Store service, and then click Restart Service.

Didn’t solve the problem ? Read Related Microsoft solutions

http://support.microsoft.com/kb/842022

http://support.microsoft.com/kb/830836

http://support.microsoft.com/kb/840835

http://support.microsoft.com/kb/821188

http://support.microsoft.com/kb/821188

http://support.microsoft.com/default.aspx?scid=898060

• Leave a comment... (4)