Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Outlook / New Users / February 2006

Tip: Looking for answers? Try searching our database.

Importing into Outlook 2003

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
RogerUK - 07 Feb 2006 21:36 GMT
When I try to import a .pst file into Outlook 2003 I get a message "The
operation failed. An object could not be found."  I have been using this
facility successfully for several weeks.  I have tried system restore and
scanpst, but they make no difference.  Any ideas what I should try?
Gordon - 07 Feb 2006 21:57 GMT
> When I try to import a .pst file into Outlook 2003 I get a message
> "The operation failed. An object could not be found."  I have been
> using this facility successfully for several weeks.  I have tried
> system restore and scanpst, but they make no difference.  Any ideas
> what I should try?

DON'T IMPORT - go to File-Open-Outlook Data File - don't you read replies to
your posts?
RogerUK - 07 Feb 2006 22:48 GMT
Yes.  Thanks for your reply.  Unfortunately all it does is make Outlook fall
over and send an error message to Microsoft.

> > When I try to import a .pst file into Outlook 2003 I get a message
> > "The operation failed. An object could not be found."  I have been
[quoted text clipped - 4 lines]
> DON'T IMPORT - go to File-Open-Outlook Data File - don't you read replies to
> your posts?
Brian Tillman - 08 Feb 2006 03:08 GMT
> Yes.  Thanks for your reply.  Unfortunately all it does is make
> Outlook fall over and send an error message to Microsoft.

Then 1) click Help>Detect and Repair and 2) use the Inbox Repair Tool on the
PST.  Importing from a PST is never the way to transfer data into Outlook.
Signature

Brian Tillman

RogerUK - 09 Feb 2006 21:01 GMT
Thanks.  I used the Inbox repair tool to repair the file - it found 5 errors
and corrected them.  However, Outlook 2003 still shut down when I tried to
open the file.  Looking at the other postings here, could it be because the
file I am trying to open is Outlook 2000, and needs some sort of
"translation" before Outlook 2003 can recognise it?

> > Yes.  Thanks for your reply.  Unfortunately all it does is make
> > Outlook fall over and send an error message to Microsoft.
>
> Then 1) click Help>Detect and Repair and 2) use the Inbox Repair Tool on the
> PST.  Importing from a PST is never the way to transfer data into Outlook.
Russ Valentine [MVP-Outlook] - 09 Feb 2006 21:56 GMT
No. Outlook 2000 files are perfectly compatible with Outlook 2003. There's
probably more to your story than you've told us for you to have developed
this problem.
Create  new profile.
Signature

Russ Valentine
[MVP-Outlook]

> Thanks.  I used the Inbox repair tool to repair the file - it found 5
> errors
[quoted text clipped - 11 lines]
>> PST.  Importing from a PST is never the way to transfer data into
>> Outlook.
RogerUK - 09 Feb 2006 22:48 GMT
The only other bit of information I can think of is that when I open Outlook
I get a dialogue box called Microsoft LDAP Directory with a tab called
Connection Details.  Server is "NULL", Port is a 4 digit number, User Name is
"NULL" and Password is blank.  I simply click the "OK" button and it goes
away.  Is this relevant?  I do not want to use Outlook 2003 as my email
vehicle - I am quite happy with Outlook Express - I am simply using it to
transfer my electronic diary from my work computer to my PDA.

> No. Outlook 2000 files are perfectly compatible with Outlook 2003. There's
> probably more to your story than you've told us for you to have developed
[quoted text clipped - 15 lines]
> >> PST.  Importing from a PST is never the way to transfer data into
> >> Outlook.
Russ Valentine [MVP-Outlook] - 09 Feb 2006 23:07 GMT
I suspect there is more you've left out.
Did you do an in place upgrade from Outlook 2000 IMO mode?
If so, my recommendation is even more compelling: Create a new profile!
Signature

Russ Valentine
[MVP-Outlook]

> The only other bit of information I can think of is that when I open
> Outlook
[quoted text clipped - 28 lines]
>> >> PST.  Importing from a PST is never the way to transfer data into
>> >> Outlook.
RogerUK - 12 Feb 2006 09:07 GMT
Thank you.  The upgrade from Outlook 2000 was done using Microsoft CD ROMS.  
However, I have created a new profile, and in combination with using SCANPST
I can now get my work calendar onto my home computer.  Many thanks.

> I suspect there is more you've left out.
> Did you do an in place upgrade from Outlook 2000 IMO mode?
[quoted text clipped - 31 lines]
> >> >> PST.  Importing from a PST is never the way to transfer data into
> >> >> Outlook.
Brian Tillman - 11 Feb 2006 17:48 GMT
> The only other bit of information I can think of is that when I open
> Outlook I get a dialogue box called Microsoft LDAP Directory with a
> tab called Connection Details.  Server is "NULL", Port is a 4 digit
> number, User Name is "NULL" and Password is blank.  I simply click
> the "OK" button and it goes away.  Is this relevant?

It's not relevant, but that particular probem is easily fixed.  Tools>E-mail
Accounts>View existing directories or address books>Next.  Remove the LDAP
server.
Signature

Brian Tillman

RogerUK - 12 Feb 2006 09:08 GMT
My new profile is not being used for email, so I don't get this problem any
more.  Many thanks for your help.

> > The only other bit of information I can think of is that when I open
> > Outlook I get a dialogue box called Microsoft LDAP Directory with a
[quoted text clipped - 5 lines]
> Accounts>View existing directories or address books>Next.  Remove the LDAP
> server.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.