Publisher crashing constantly

[Jeremy Drake]

I have recently purchased Publisher 2003 and started to use it today. Every
time I attempt to insert any kind of object to create my documents, it
crashes asking to send the error report and restart the program. I thought
it was the service pack, so I reinstalled it to its previous state and still
get the same problem. I even tried closing out every TSR to no avail. I
don't know if it could be because the rest of my Office suite is version
2002, but Visio 2002 Pro and FrontPage 2002 work fine as far as I know. Do I
need to upgrade my Office suite to 2003 for Publisher to stop crashing
non-stop? Any help is appreciated.

 

[John Inzer]

Maybe some of the following ideas will help...

Have you installed the updates from the
Office Website?

http://office.microsoft.com/en-us/officeupdate/default.aspx
click the "Check for updates" button

There's a possibility that you need to
update your printer driver.

Also...have a look at these articles:

(329820) How to use Office programs with
the Norton AntiVirus Office plug-in
http://support.microsoft.com/?kbid=329820

(289508) How to view error signatures if an
Office program experiences a serious error
and quits
http://support.microsoft.com/?kbid=289508

Also might help to disable Script Blocking...

How to disable Script Blocking
in Norton AntiVirus 2002 or 2003
or 2004
http://tinyurl.com/3tfo7
(also works for 2005)

 

[Jeremy Drake]

I did mentioned that I tried the service pack (from the office downloads
site) and I don't have any Norton Applications installed. But I will try to
follow the information in article 289508 that you listed.

| Maybe some of the following ideas will help...
|
| Have you installed the updates from the
| Office Website?
|
| http://office.microsoft.com/en-us/officeupdate/default.aspx
| click the "Check for updates" button
|
| There's a possibility that you need to
| update your printer driver.
|
| Also...have a look at these articles:
|
| (329820) How to use Office programs with
| the Norton AntiVirus Office plug-in
| http://support.microsoft.com/?kbid=329820
|
| (289508) How to view error signatures if an
| Office program experiences a serious error
| and quits
| http://support.microsoft.com/?kbid=289508
|
| Also might help to disable Script Blocking...
|
| How to disable Script Blocking
| in Norton AntiVirus 2002 or 2003
| or 2004
| http://tinyurl.com/3tfo7
| (also works for 2005)
|
| --
|
| John Inzer
|
|
| | >I have recently purchased Publisher 2003 and started to use it today.
Every
| > time I attempt to insert any kind of object to create my documents, it
| > crashes asking to send the error report and restart the program. I
thought
| > it was the service pack, so I reinstalled it to its previous state and
| > still
| > get the same problem. I even tried closing out every TSR to no avail. I
| > don't know if it could be because the rest of my Office suite is version
| > 2002, but Visio 2002 Pro and FrontPage 2002 work fine as far as I know.
Do
| > I
| > need to upgrade my Office suite to 2003 for Publisher to stop crashing
| > non-stop? Any help is appreciated.
| >
| >
|

 

[Jeremy Drake]

This is what I read in 'Event Viewer': I'm assuming the files are currently
unstable, probably because Office 10 is re-writing the dll.

Event Type: Error
Event Source: Microsoft Office 11
Event Category: None
Event ID: 1000
Date: 6/25/2005
Time: 6:35:09 PM
User: N/A
Computer: NOMAD
Description:
Faulting application mspub.exe, version 11.0.6255.0, stamp 405f8718,
faulting module gdiplus.dll, version 6.0.3264.0, stamp 4040f72a, debug? 0,
fault address 0x0005700e.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

 

[Frank]

This is what I read in 'Event Viewer': I'm assuming the files are currently
unstable, probably because Office 10 is re-writing the dll.

Event Type: Error
Event Source: Microsoft Office 11
Event Category: None
Event ID: 1000
Date: 6/25/2005
Time: 6:35:09 PM
User: N/A
Computer: NOMAD
Description:
Faulting application mspub.exe, version 11.0.6255.0, stamp 405f8718,
faulting module gdiplus.dll, version 6.0.3264.0, stamp 4040f72a, debug? 0,
fault address 0x0005700e.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

This is a common problem in Pub 2003 that MS seems not to want to fix.
The work around is to turn down your hardware acceleration 3 clicks from
full until directdraw and direct3d acceleration are disabled.
Go to:
display properties/settings/advanced/troubleshoot and turn that sucker down.
That should do it!
Frank

 

[John Inzer]

I did mentioned that I tried the service pack (from the office downloads
site) and I don't have any Norton Applications installed. But I will try
to
follow the information in article 289508 that you listed.

========================================
OK...I thought you might be referring to WinXP SP2...

Still might be worth a try to update your printer
driver...and your video driver.

Anyway.....have a look at this article:

(836855) Publisher 2003 stops responding
with an error message that references the
Mspub.exe file
http://support.microsoft.com/?kbid=836855

 

[Ed Bennett]

This is a common problem in Pub 2003 that MS seems not to want to fix.

This is NOT a problem in Publisher, it is a fault with the video drivers.

The work around is to turn down your hardware acceleration 3 clicks
from full until directdraw and direct3d acceleration are disabled.

The fact that turning down hardware acceleration works around the problem
demonstrates the fact that the problem lies with the video drivers and not
with Publisher.

Would you have Microsoft code drivers for every piece of hardware ever
released by any hardware manufacturer, ever, so that they would work with
Publisher?

 

[Frank]

This is NOT a problem in Publisher, it is a fault with the video drivers.




The fact that turning down hardware acceleration works around the problem
demonstrates the fact that the problem lies with the video drivers and not
with Publisher.

Would you have Microsoft code drivers for every piece of hardware ever
released by any hardware manufacturer, ever, so that they would work with
Publisher?

Not to worry Ed as they (MS) fixed the problem in Longhorn.
Frank

 

[Mike Koewler]

Ed,

Why isn't this problem reported in the Illustrator, InDesign, Quark,
PhotoShop, Serif or any other NGs. I've argued with Brian K, for years,
that MS seems to walk their own path, that Pub really doesn't care about
users and their software. To this day, I see posts that people running
XP need to upgrade their video driver so Pub 2000 will run on it. Ditto
for printer drivers.

This is lunacy and arrogance run amok. I haven't read the spec sheet for
Pub, even though I have the last three programs. Do any of the versions
say that I may need a driver released in 2004 so I can run a program
released in 2002? Why doesn't MS release a program that will run on
current, or near current, machines? No need to answer - I know. They
really do not care about users. Sell mass copies and charge users $35 to
tell them why it won't run on their computer.

Mike

 

[Frank]

Ed,

Why isn't this problem reported in the Illustrator, InDesign, Quark,
PhotoShop, Serif or any other NGs. I've argued with Brian K, for years,
that MS seems to walk their own path, that Pub really doesn't care about
users and their software. To this day, I see posts that people running
XP need to upgrade their video driver so Pub 2000 will run on it. Ditto
for printer drivers.

This is lunacy and arrogance run amok. I haven't read the spec sheet for
Pub, even though I have the last three programs. Do any of the versions
say that I may need a driver released in 2004 so I can run a program
released in 2002? Why doesn't MS release a program that will run on
current, or near current, machines? No need to answer - I know. They
really do not care about users. Sell mass copies and charge users $35 to
tell them why it won't run on their computer.

Mike

As I told Ed, it's been fixed in Longhorn.
Frank

 

[Ed Bennett]

Do any of the
versions say that I may need a driver released in 2004 so I can run a
program released in 2002?

Yeah, Microsoft can really release a program in 2002 and guarantee that it
will run on drivers for hardware released in 2004.

It takes a while for the driver manufacturers to iron out all the bugs or
inconsistencies in their drivers.

I haven't seen the Publisher source code and so have no idea what driver
calls Publisher makes, but they're obviously not the same ones as
Illustrator, InDesign, Quark, PhotoShop, Serif, or any other applications
whose forums or newsgroups you frequent.

I for one have seen video drivers as a commonly-cited cause for problems
with many other software applications (I can't remember them offhand, but
IIRC in 24hoursupport.helpdesk, a video driver upgrade is one of the first
generic fixes to be suggested to any unknown problem

Why doesn't MS release a program that will
run on current, or near current, machines?

Maybe they do, but you just don't notice.

No need to answer - I
know. They really do not care about users.

To see you make that remark saddens me.

Sell mass copies and
charge users $35 to tell them why it won't run on their computer.

Ah yes, I mean it's not like they offer a free newsgroup at which they can
receive exactly the same information free of charge from other users.

 

[Ed Bennett]

Not to worry Ed as they (MS) fixed the problem in Longhorn.

I'm glad to hear it. Which version of Longhorn have you tested this with.

Evidently Longhorn's new driver architecture mechanism thingummy works
around the driver problem somehow.

 

[Frank]

I'm glad to hear it. Which version of Longhorn have you tested this with.

Evidently Longhorn's new driver architecture mechanism thingummy works
around the driver problem somehow.

#4079 & 5048
Frank

 

[Mike Koewler]

Ed Bennett wrote:

Yeah, Microsoft can really release a program in 2002 and guarantee that it
will run on drivers for hardware released in 2004.

It takes a while for the driver manufacturers to iron out all the bugs or
inconsistencies in their drivers.

Ed, that's not what I meant. It was not unusual to read where someone
was using Pub 2003 and it wouldn't run on a new computer bought in 2002.
The standard answer is to upgrade the video or printer driver. I posit
that MS could just as easily provide a program that runs on current
machines as do other major software developers.

I haven't seen the Publisher source code and so have no idea what driver
calls Publisher makes, but they're obviously not the same ones as
Illustrator, InDesign, Quark, PhotoShop, Serif, or any other applications
whose forums or newsgroups you frequent.

My point!

I for one have seen video drivers as a commonly-cited cause for problems
with many other software applications (I can't remember them offhand, but
IIRC in 24hoursupport.helpdesk, a video driver upgrade is one of the first
generic fixes to be suggested to any unknown problem




Maybe they do, but you just don't notice.

I notice the plethora of posters who have trouble with display or printing.

Ah yes, I mean it's not like they offer a free newsgroup at which they can
receive exactly the same information free of charge from other users.

Sarcasm noted, but not everyone who buys Pub knows about this NG.

Maybe I'm spoiled by companies like Serif who go out of their way to
help customers without charging.

Mike

 

[Ed Bennett]

#4079 & 5048

Let's hope that it makes it through to release

 

[Ed Bennett]

My point!

Well, would you have the Publisher team spend all their time recoding the
Publisher application to use the same API calls as all other applications,
instead of repairing broken features?

I notice the plethora of posters who have trouble with display or
printing.

But do you notice the plethora of posters who don't have trouble with either
display or printing?

Sarcasm noted, but not everyone who buys Pub knows about this NG.

Microsoft is trying their very best to alleviate this problem (as bad as it
may seem, they actually don't want everyone to phone their paid technical
support line for very common issues).

Maybe I'm spoiled by companies like Serif who go out of their way to
help customers without charging.

Serif doesn't have as large a user base as Publisher, and to be perfectly
frank, I think that Serif customers have a little more intelligence and
technical capabillity than the average Microsoft customer.
If Microsoft offered free support, then every Average Joe Microsoft user who
had access to a Microsoft product and Internet connection would start
emailing idiotic and inane questions without going anywhere near the help
file, manual, knowledge base, or Google. Microsoft may be a multi-billion
dollar company, but I doubt even Microsoft would be able to afford to staff
such a "technical" support facility and keep it to anywhere near an
acceptable standard.

 

[JoAnn Paules [MSFT MVP]]

I can tell you that AutoCAD is even pickier about video drivers. And it used
to be as fussy about printer drivers. I don't know if that still holds true
but at one time it was a real pain in the arse.

 

[Jeremy Drake]

|
| Maybe I'm spoiled by companies like Serif who go out of their way to
| help customers without charging.
|
| Mike
| >

I have so much time on my hands that I actually use it to search for even
the wierdest of NG's. Some of them I decided to unsubscribe from because of
the constant bashing of products and others for not getting a response for
months. You'll never find me doing that, I'll just ask how to fix the
problem.

 

[JoAnn Paules [MSFT MVP]]

For which some of us are grateful. I hate when I'm looking for help or
suggestions and all I see is why I should be using something else.