This page contains information to help troubleshoot Projectwise Publishing Server.
The first thing to do is understand how PW Publishing Server is being used. There are three main scenarios:
Whatever the scenario, the information in the stand-alone publishing section is always relevant.
In this mode PW Publishing Server is used to publish file to the web using either the provided example web pages of a custom web application that may use the Vpr control.
Please look at the product readme for specific information.
Before searching any further, we must determine what type of problem we are facing. The most common ones are connectivity and publishing problems.
Projectwise Publishing Server is an http server, similar to IIS but specific to publishing engineering content. It can run in two main "modes":
If you have problems reaching the server or the server does not answer, you should follow the normal tcp/ip network troubleshooting tasks.
If you have 404 not found errors, verify that your logical paths / virtual directories correctly point to the files you want to publish.
Note that you cannot use mapped network drives in path mappings as these are only valid when the user that created the mapping is logged into the machine. The windows services of Publishing Server will not have access to the mappings. You can however use UNC paths.
This is when the server can be reached but does not correctly publish the data. There are a few possible symptoms. You could be getting an error from the Vpr control saying that it cannot load the specified URL, or your web page could show an "Engine could not generate image file" message for example.
Here is a quick list of requests that you can type directly in your Internet Explorer browser to test for publishing problems. Change the server name and port accordingly. It is suggested to do these from a Windows XP client machine as the enhanced security settings under Windows Server 2003 could cause additional problems.
If all those queries work fine, basic publishing works. In that case the problem may be specific to your data.In all cases, a very good tool to help you diagnose the problem is the Publishing Server log. You can obtain the log by using a DOS shell to navigate to the main Publishing Server directory and type "publogdump.exe > log.txt". You can then open log.txt in notepad.
Here is a list of things to check if you have publication problems.
As a note, reinstalling the server or downgrading to an earlier version will most probably not fix the problem.
In this mode, PW Publishing Server publishes files that reside in a Projectwise datasource to either the WEL or WebParts clients. Please make sure the instructions in the "PW Implementation Guide" have been followed first. This is mandatory in order for Publishing Server to be able to communicate with the PW Integration Server.
Start by making sure that Publishing Server can work stand-alone. It will be easier to diagnose problems this way.
Look in the PW Publishing Server log. If there are any errors communicating with the PW Integration Server, they should be listed there.
The PW Publishing Server technology is also used to publish background maps in the geospatial extension to Projectwise. Therefore, two options exist to publish the background maps:
We must know what flavor we are running as troubleshooting will be different. First, an explanation of why these two options exist:
A note on workspaces
Projectwise has two mechanisms that let users configure workspace information when starting Microstation to view/edit dgn files: workspace profiles and managed workspaces. These features are supported by Projectwise Publishing Server and by the background map engine. However, the Microstation engine used internally does not have extra application extensions installed. Therefore, using workspace information referring to supplemental applications will not work and will make the publication fail. One such example is trying to use a Bentley Map workspace to publish dgn/xfm data. Make sure that the workspace configurations you have set on the Projectwise folders containing your background map files only depend on stand-alone Microstation.
When PW Publishing Server is used, it must be installed in addition to PW geospatial, on the same server or on another machine, and it requires extra installation and setup steps similar to running it with the PW Web clients. See the PW Implementation Guide" for details.
When troubleshooting this, start by verifying if basic publishing works. Background map publishing will not work if basic publishing is broken. See the Stand-Alone publishing troubleshooting section.
If PW WEL of WebParts clients are installed, you can use these clients to test PW connectivity.
Make sure the PW Publishing Gateway is installed and working.
The background map publishing engine comes with the PW Geospatial server install and needs no additional installation steps before it can be used. It requires setup in some cases however, see the PW Geospatial documentation for details.
Also see the readme for the PW Geospatial Server product. Here is an excerpt of that readme:
Product TechNotes and FAQs
ProjectWise TechNotes And FAQs
Bentley Technical Support KnowledgeBase
Bentley LEARN Server
Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!