A recent hiccup with my Windows server necessitated an IIS re-install, but I then found I couldn't access any NP sites, although the service was running and NP was serving the sites. Cause - the IIS rebuild destroyed NP's virtual folders. To save a re-install of NP, here's how to re-build the virtual folders:
Open the IIS Admin Window (Control Panel - Administrative Tools - Internet Services Manager).
If the web site you are using (normally 'default' for single users) has a 'res' and 'netpub' folder, you should be fine, otherwise:
Action menu, New, Virtual Folder. You need to make 2 - #1 and #2 below. We will cover both in one walk through the new virtual directory wizard.
Step 1 - Virtual Directory Alias
#1 'res'
#2 'netpub'
Step 2 - Website Content Directory
#1 'C:\Program Files\Extensis\Portfolio NetPublish Server\WebRoot'
#2 'C:\Program Files\Extensis\Portfolio NetPublish Server\WebRoot\app'
Step 3 - Access Permissions
#1 - tick 'read' and 'Run scripts'
#2 - tick 'read' and 'Run scripts'
Complete the wizard
#1 - open the properties panel for 'res', at the 'Virtual Directory' tab. In the 'Local Path' section (middle), only 'Read', 'Log Visits' and 'Index this resource' should be ticked. In the 'Execute Permissions' drop-down (centre bottom) select 'None' , if not already selected. You're done with #1.
#2 - open the properties panel for 'netpub', at the 'Virtual Directory' tab. In the 'Local Path' section (middle), only 'Read', 'Log Visits' and 'Index this resource' should be ticked. In the 'Execute Permissions' drop-down (centre bottom) select Scripts and Executables' , if not already selected. Now click the 'Configuration' button, and view the 'Application Mappings' tab. If '.np' is not listed, click the 'Add' button. In the next dialog click the 'Browse' button and find "C:\WINNT\SYSTEM32\isapi_fcgi.dll" - noting that the Open dialog defaults to only showing EXEs, so you need to alter that to show DLLs. In the 'Extension' box type '.np' and click OK twice to close the Add dialog and the 'Application Configuration' dialog. You're done with #2.
Note that if you already have these folder but when you try to open an NP page you get the browser asking to download the NP file, most likely you need to check the 'netpub' folder properties as the '.np' association with isapi_fcgi.dll has probably not been made or has been deleted.
I'm uncertain is there are extra steps needed with II6 - if there are please let me know via the 'Report Error' web form link in the menus at the foot of this page.
On a different tack, if you need to un/reinstall NP, you would do well to save the 'sites' folder inside the NP app folders. You might want to copy the whole 'WebRoot' folder if you've made customisations to things like editable '.np' libraries (those written in JavaScript in the 'libraries' folders). When restoring, you should be able to copy the sites folder straight back. If you've saved other customisations (i.e. the whole 'WebRoot' tree) then add back the edited NP files as needed, testing as you go.
Keywords (to assist indexing/searching):
Question: Rebuilding NP associations after IIS re-install [FAQ00364.htm]
Last Update:- 31 May 2006
Site and articles © Mark Anderson 2001-2007 - Visit my home page