Opening Error
Moderators: Tyler, Scott, PWB v2 Moderator
-
- Contributor
- Posts: 25
- Joined: Wed Oct 12, 2005 2:38 pm
Opening Error
I just updated to 2.09 and get the following error when trying to open PWB: Failed to create empty document.
What's causing this?
Simon
What's causing this?
Simon
Simon
-
- Contributor
- Posts: 25
- Joined: Wed Oct 12, 2005 2:38 pm
Error
I am using 2.0.9.2
Windows XP Pro SP2
Using a batch to lauch PWB: "C:\Program Files\TeamSoftware Solutions\Public Web Browser v2\PWB.exe" "wisdom.biola.edu/ill/index.cfm"
Simon
Windows XP Pro SP2
Using a batch to lauch PWB: "C:\Program Files\TeamSoftware Solutions\Public Web Browser v2\PWB.exe" "wisdom.biola.edu/ill/index.cfm"
Simon
Simon
-
- Contributor
- Posts: 25
- Joined: Wed Oct 12, 2005 2:38 pm
Error
I copied over the new executable. Still got the same error. What else could cause this error?
Simon
Simon
Simon
Opening Error
I am having the same problem with any of the versions above 2.9.
I have it installed on both XP SP2 and Win 2k SPK4 with IE v.6
I have also tried uninstalling Public Browser and reinstalling it with 2.9
still the same problem.
My shortcut only points to the ini file on the server, with the exe running locally.
If a solution was found for the earlier reports, or if further information is needed let me know.
Thanks,
Morgyne
I have it installed on both XP SP2 and Win 2k SPK4 with IE v.6
I have also tried uninstalling Public Browser and reinstalling it with 2.9
still the same problem.
My shortcut only points to the ini file on the server, with the exe running locally.
If a solution was found for the earlier reports, or if further information is needed let me know.
Thanks,
Morgyne
Try removing the quotes from around the path to the INI file.
L:\TEAMSO~1\PUBLIC~1\PWB.exe /s /ini=\\lib5\pbrowser\version2\first\pwb-l-restart.ini
Is this on a Windows XP or Windows 2000 computer?
If you copy the INI file locally, rename it to PWB.INI, and remove any command line switches do you still get the error?
What happens if you disable Deepfreeze?
--Scott
L:\TEAMSO~1\PUBLIC~1\PWB.exe /s /ini=\\lib5\pbrowser\version2\first\pwb-l-restart.ini
Is this on a Windows XP or Windows 2000 computer?
If you copy the INI file locally, rename it to PWB.INI, and remove any command line switches do you still get the error?
What happens if you disable Deepfreeze?
--Scott
I still get the error with DeepFreeze in a thawed state, local ini file, and with the quotes removed from the shortcut.
I also tried it when I am logged in as local administrator, and I get the error.
Any further suggestions, this seems so strange to me and have never had
any problems with earlier versions.
This is on XP SPK2 and also my work computer which is a 2K SPK4 machine.
Morgyne
I also tried it when I am logged in as local administrator, and I get the error.
Any further suggestions, this seems so strange to me and have never had
any problems with earlier versions.
This is on XP SPK2 and also my work computer which is a 2K SPK4 machine.
Morgyne
Are you running PWB from a shortcut or from a batch file?
Please zip the shortcut or batch file and send it to support@team2s.com.
If you right click on the PWB EXE file and select Properties, on the Version tab, what is the full file version (2.0.9.4)?
--Scott
Please zip the shortcut or batch file and send it to support@team2s.com.
If you right click on the PWB EXE file and select Properties, on the Version tab, what is the full file version (2.0.9.4)?
--Scott
Well, found the fix to the opening error and it seems to work just fine now.
The problem was in the .ini file, in previous versions the setting for
shellbar didn't cause errors, and was left blank, but in these later versions you had to put in the location name in the .ini file.
[FILES]
...
ShellBar=
(leaving it blank causes opening error even if
ShowShellBar=False in the Browser section is set.)
[FILES]
...
ShellBar=ShellBar
(just adding the name after the = stops the opening error.)
Hope this helps others.
Thank you for all your help and attention to the problem.
Morgyne
The problem was in the .ini file, in previous versions the setting for
shellbar didn't cause errors, and was left blank, but in these later versions you had to put in the location name in the .ini file.
[FILES]
...
ShellBar=
(leaving it blank causes opening error even if
ShowShellBar=False in the Browser section is set.)
[FILES]
...
ShellBar=ShellBar
(just adding the name after the = stops the opening error.)
Hope this helps others.
Thank you for all your help and attention to the problem.
Morgyne