"Failed to create empty document"

For general issues related to PWB v2.

Moderators: Tyler, Scott, PWB v2 Moderator

Post Reply
jpapier
Contributor
Contributor
Posts: 39
Joined: Thu Apr 17, 2003 10:15 am

"Failed to create empty document"

Post by jpapier »

Hello PWB-ers,

We have a few library catalogs still running some version of PWB 2.08, and
we want to upgrade them to 2.09.3. We ran the .ini updater program,
downloaded from this website, and converted the ver 2.08 pwb.ini to ver
2.09. Or so we thought. When we try to run the 2.09.3 version of pwb.exe with the new pwb.ini file, we get "failed to create empty document."

Can anyone (Scott!?) shed some light on this?

Thanks,

Jeff
Jeff Papier
Senior Network Librarian
South Brunswick Public Library
Monmouth Junction, NJ 08852

Scott
Site Admin
Site Admin
Posts: 2539
Joined: Mon Dec 16, 2002 12:31 pm
Location: Rochester, MN
Contact:

Post by Scott »

What is the command line you are using for PWB?

--Scott

jpapier
Contributor
Contributor
Posts: 39
Joined: Thu Apr 17, 2003 10:15 am

Post by jpapier »

Hi Scott,

We actually invoked PWB just by double-clicking on its icon, right from the folder where all of the PWB files live. We did this just to test how things would work out before propagating the updated exe and ini files to the other OPACs. JP
Jeff Papier
Senior Network Librarian
South Brunswick Public Library
Monmouth Junction, NJ 08852

Scott
Site Admin
Site Admin
Posts: 2539
Joined: Mon Dec 16, 2002 12:31 pm
Location: Rochester, MN
Contact:

Post by Scott »

What version of Windows are you using?

If you wouldn't mind, zip all the files together and send them to support@teamsoftwaresolutions.com.

--Scott

jpapier
Contributor
Contributor
Posts: 39
Joined: Thu Apr 17, 2003 10:15 am

Post by jpapier »

Will do, Scott
Jeff Papier
Senior Network Librarian
South Brunswick Public Library
Monmouth Junction, NJ 08852

Scott
Site Admin
Site Admin
Posts: 2539
Joined: Mon Dec 16, 2002 12:31 pm
Location: Rochester, MN
Contact:

Post by Scott »

Change the following line in your INI file to correct the problem.

[Files]
...
ShellBarFolder=Shellbar
...

--Scott

Post Reply