Can't open My Publisher after failed mandatory upgrade

[lolo]

I've been working on a new book for some time now. Today I clicked to open the My Publisher software to continue work on it and I was forced to do a mandatory upgrade/update or close the program. No othe options, so I chose to do the upgrade. It seemed to complete ok, but then it said that bookmaker.exe can't open. I've rebooted, but each time I try to open it, I get the mandatory upgrade thing again and can't get past it. What's going on? I'd like to get this book done - I'm more than half way through!

[Jemclau]

I had difficulty loading it after the upgrade. I clicked 'Run as Administrator' and it loaded (Vista).
However, My Publisher has closed abruptly twice since the upgrade with no warning.
There is definitely a problem with this upgrade.

[kfreeman]

I am having this very same problem. So frustrating!!

[MyPublisherQA]

lolo:

The message you are saying is odd, because the new program is called MyPublisher.exe and no longer is bookmaker.exe. I wonder if you are just trying to run a shortcut that still exists to the old software?

Look if you have a MyPublisher shortcut to launch the software. If you do not,
please go to our website at: http://www.mypublisher.com/newGetStarted.php and try downloading the upgrade from our website instead of the update message.

[MyPublisherQA]

Jemclau:

Do you recall which product (Book, Jacket, Card, or Calendar) you were in when the crash happended, also what you were doing at the time?

[MyPublisherQA]

For anyone who has problems the best way to get support would be to submit a request at: http://www.mypublisher.com/support.php. This is monitored 24/7. We also check here periodically, but nowhere near as often. This is mostly for user to user support.

[anonymouse]

Same thing here. Launched the software today and it forced me to upgrade, then after some upgrading activity the program bombed with this in the (Vista) log:

Faulting application BookMaker.exe, version 0.0.0.0, time stamp 0x47ff17fd, faulting module BookMaker.exe, version 0.0.0.0, time stamp 0x47ff17fd, exception code 0xc0000005, fault offset 0x00049e24, process id 0x2abc, application start time 0x01c9092e987c5340

I also got this in the event log 2 seconds later:
Diagnostic module {50e3b0eb-5780-49de-9eb5-8d53a51fd146} (%windir%\system32\pcadm.dll) encountered an error while handling scenario {d113e4aa-2d07-41b1-8d9b-c065194a791d}, instance {6f47ca01-dfb9-4d5f-a685-b8b1f07efe44}, original activity ID {00000000-0000-0000-0000-000000000000}. The error code was -2147024882

Retrying a couple of times did not work - each time the application prompted to start the mandatory update, then crashed almost immediately after I asked it to continue, writing the same messages as above into the event log.

The issue appears to have gone away, and I have opened my book again, by installing the 3.0 verson from the website.

[Jemclau]

I was in the book section.

[tjcav]

if i download from your web site and install will I lose what I have done so far. I have almost completed my book. I do not want to lose it.

[MyPublisherQA]

Downloading from the website should not cause you to lose your books. It just skips the part that is messaging you to upgrade and appears to crash for some people.

[awongd]

I downloaded MyPublisher 3.0 from the website as suggested but now when I open it, and try to open book, it doesn't show the book I was working on. Please tell me I didn't lose all my work!

[MyPublisherQA]

If it appears your books are missing try the following we have done this with a few people and it has worked for them.

During the install there is a folder called BookMaker that simply gets renamed to MyPublisher as part of the install process. All your books are inside this folder. If the rename does not happen the program can't find the books, but it is easy to just rename the folder so it can find them.

If you are on Windows XP or Windows 2000 do the following:

1) Make sure you are not inside MyPublisher 3.0 before starting. Next, click on Start.
2) Then click on run.
3) Enter %APPDATA% in the run dialog and hit enter.
4) From there find the MyPublisher folder and double click it. Inside there you should notice a BookMaker and MyPublisher folder. If you do not see both these folders please do not proceed instead contact customer service.
5) Rename the MyPublisher folder to MyPublisherOLD.
6) Rename the BookMaker folder to MyPublisher.
7) Start the software your books should be back.

If you are on Windows Vista the instructions are the same except in step 2) click in the white box that you can type in just above the start button.

------

If this works successfully for you, you can safely go back and delete the folder called MyPublisherOLD, just be very careful about not accidentally deleting anything else instead!

[awongd]

Thank You so much.... It worked!!!

[MyPublisherQA]

Great! I will be away till Tuesday, so anyone else who has trouble please email customer service ( http://www.mypublisher.com/support.php ), since I will not be posting any responses till then.

[pollywog]

I am having the same problem. I was forced to download a mandatory upgrade, and then it seemed like there was no problem - my half-finished book was able to launch. But the minute I click on anything on the page, it just closes automatically. I have done this about 10 times now.

I have tried re-downloading bookmaker 3.0 from the mypublisher website and the same thing happens. This is getting really frustrating!

Not sure I understand from the help messages below how to fix this.

[Rescue Amy]

I've run into a similar problem. I've installed Bookmaker 2.3 from a download from Costco. I'm installing it on MS Vista using an administration account. The program appears to launch. However, when I launch the program through an non-administrative account or standard account, I get the pop-up box referring to a mandatory upgrade. I had proceeded with the upgrade and it failed.

I'm getting the impression that Bookmaker 2.3 may not be Vista compatible.

I've used an earlier version on a different computer running MS 2000.