Project Server 2003 Outlook Integration Error

S

Steve Miele

Hello,

I recieve this error when I click on the Import New Assignments in
Outlook 2003 with the PWA Add-in.

" Please reload the Project Add-in for Outlook by click Option on the
tools Menu. From the other tab, click Advanced Options and then COM
add-ins. On the COM Add-ins dialog , ensure that Microsoft Project
Server Add-In is checked, and then Click OK. If this does not resolve
the issue, you may need to repair or reinstall the add-in via Add or
Remove Programs from the control Panel."

I have tried both of the solutions listed above several times. Gone
into the registery and deleted any signs of the MPSAddin.dll which is
the Dll that PWA Add-in uses. Reinstalled again and still get the same
error. Uninstalled Office 2003 and reinstalled office and then the
add-in and I still get the error.

Everytime I get the error there is an event logged in the Eventlog
which says:

"The Desciption for Event ID [1] in Source [MS Project - Outlook
Intergration] cannot be found. The local Computer may not have the
necessary registery information or message DLL files to
displaymessages from a remote computer. You may be able to use the
/AUXSOURCE = Flag to retrieve this desription; see Help and Support
for details. The folowing information is part of the event

Component: AppointmentCollection.cls
Procedure: SelectedAppointments
Error Number: 429
Error Source: MPSAddin
Error Description: ActiveX componenet can't create Objecct"

I have played around with every setting in Outlook Security settings
ActiveX to no avail.


Any thoughts would be greatly appreciated. Thanks For your time in
advance

Steve
 
S

smiele

Finally, after exhausting all my resources had to shoot the $250 and
call Microsoft. They where of no immediate help. Finally, fixed the
problem with the two users in almost the same way.

One user, I just created a new mail profile and assigned the same
mailbox to the same user. Creating this new Profile seemed to have
resolved the issue for the user.

The other user that was experiencing the issue. I finally determined
that it was thier mailbox that was causing the problem. So I created a
new Mialbox with a slightly different name. Dave instead of David and
then linked his NT account to the the new mailbox and gave him access
to both mailboxes. Setup his oulook profile to look at the new mailbox
and then had him copy important mail from the old mailbox to the new
mailbox. At least the stuff that was important. This finally worked.
Steve Miele
 
S

smiele

Finally, after exhausting all my resources had to shoot the $250 and
call Microsoft. They where of no immediate help. Finally, fixed the
problem with the two users in almost the same way.

One user, I just created a new mail profile and assigned the same
mailbox to the same user. Creating this new Profile seemed to have
resolved the issue for the user.

The other user that was experiencing the issue. I finally determined
that it was thier mailbox that was causing the problem. So I created a
new Mialbox with a slightly different name. Dave instead of David and
then linked his NT account to the the new mailbox and gave him access
to both mailboxes. Setup his oulook profile to look at the new mailbox
and then had him copy important mail from the old mailbox to the new
mailbox. At least the stuff that was important. This finally worked.
Steve Miele
 
Top