S
Steve
We have multiple installations of Project Server. on all but the original
instance, the 'Print Grid' link below any grid does not work. It causes a new
page to be opened with an HTTP 403 error (You are not authorized to view this
page). The URL is also wrong
(http://myserver/ProjectServer/Library/PWAPrint.asp).
I think I've traced the problem to the file IIS Virtual
Root\LIBRARY\PWAPRINT.INC, line 117. The line is hardcoded with this:
var const_PWA_PRINT_PAGE_URL =
"/ProjectServer/Library/PWAPrint.asp";
The path is hardcoded with /ProjectServer. But it looks like when EditSite
created the new instances, it set this virtual directory to not run scripts.
So my question is this: Can I edit the virtual directory in IIS to let
'ProjectServer' execute scripts, or does the code need to change to work with
non stadnard names created by EditSite?
Thank in advance for your help.
Steve
instance, the 'Print Grid' link below any grid does not work. It causes a new
page to be opened with an HTTP 403 error (You are not authorized to view this
page). The URL is also wrong
(http://myserver/ProjectServer/Library/PWAPrint.asp).
I think I've traced the problem to the file IIS Virtual
Root\LIBRARY\PWAPRINT.INC, line 117. The line is hardcoded with this:
var const_PWA_PRINT_PAGE_URL =
"/ProjectServer/Library/PWAPrint.asp";
The path is hardcoded with /ProjectServer. But it looks like when EditSite
created the new instances, it set this virtual directory to not run scripts.
So my question is this: Can I edit the virtual directory in IIS to let
'ProjectServer' execute scripts, or does the code need to change to work with
non stadnard names created by EditSite?
Thank in advance for your help.
Steve