Can't close PST files

[Russ Valentine [MVP-Outlook]]

Much of the time, however, we can figure out where the problem occurred.
Many times it arises from improper data file migration or storage by the end
user. Other times it arises from exit hangs by Outlook many of which are
caused by add-ins or synch software. It's always worthwhile trying to figure
out the cause when we can. It's better to treat angina with a coronary stent
than to do a heart transplant, too.
--
Russ Valentine
[MVP-Outlook]

Actually, while checking through the kb, msdn and this newsgroup it
appears that Outlook does indeed get into an inconstent state by itself
for no apparent reason quite frequently. It stores a lot of state in the
registry, since that is not transacted I can see why it get's itself into
out of sync quite frequently. If it didn't there wouldn't be much use for
all of the profile and registry fixer upper tools that people come up with
to solve it's problems. They don't seem to need to know how it happened.

Since Outlook does not do this all by itself for no reason, the steps
that lead up to the problem would have been helpful to provide a more
specific solution for you and to help you avoid the problem again.
Creating a new profile is a sledgehammer approach that fixes a whole host
of problems but leaves you having to recreate a lot of settings. It's
nice not to have to do it if you don't have to.
--
Russ Valentine
[MVP-Outlook]

You had all the information I had. Sometimes you have to deduce a
problem from forensic evidence. In this case since I see that these
types of profile issues are pretty common, I'm not really sure how what
led to it is relevant, as the solutions never mention it.

Fortunately the other user's suggestions cleaned up the problem.

 

[Bob Provencher]

Certainly more information is always better than less, so next time "feel
free" to ask politely and not assume the guy on the other site is an idiot
with a sarcastic comment like "Feel free to provide some actual
information." What I gave WAS ACTUAL information and happened to be more
than sufficient for a qualified individual to solve the problem.

 

[Russ Valentine [MVP-Outlook]]

OK. I see. Sorry. Yes, I'll ask for the requisite information more politely
next time. Sometimes it gets tiring when the initial post is as vague and
uninformative as yours was because we then have to take a lot of time to
drill down into the problem. This site is worth a look when you use
peer-to-peer newsgroups for help:


Sure, "create a new profile" will fix this and many other problems. I
assumed you were looking for a more specific solution if one were available.
In the end, you managed to be far more insulting through the thread than I
was impolite at its start. I apologize.

 

[Christian Goeller]

Bob Provencher, you wrote on Tue, 3 Jul 2007 12:32:36 -0400:

WOW! There were a ton of unused entries in there, after using it, it not
only fixed my issues but start up is in less than a second now which used to
take 30 seconds... very cool.

Do I understand correctly that everything is ok?

 

[Bob Provencher]

Yes

Bob Provencher, you wrote on Tue, 3 Jul 2007 12:32:36 -0400:


Do I understand correctly that everything is ok?

 

[Christian Goeller]

Bob Provencher, you wrote on Tue, 3 Jul 2007 21:38:07 -0400:

Yes

Fine .

 

[Bob Provencher]

Actually, the solution was not to create a new profile, if you followed the
thread you'd have know that.

I've been debugging software sinec the early 80's and been on usenet since
the 90's so I know what information is necessary and what is a good post and
what is an obnoxious response.

I got some good responses that answered my question very quickly from the
complete informaiton I gave, and one obnoxious one asking for irrelevant
information.

Hopefully that individual is not planning on making a career out of tech
support.

 

[Russ Valentine [MVP-Outlook]]

No risk of that. You really haven't been paying attention. I have no plans
for a career in tech support. However, when you need a stent in your LAD or
a heart transplant, you will be using me or one of my colleagues.