| |
| Search found 21 matches |
| Author | Message |
|---|---|
| mwagoner Replies: 22 Views: 54553 |
|
| Update:
I tried giving the GetWeb service a specific account to use and then granted that account share access to the IIS directories. I didn't have any luck but I didn't spend much time on it. For now I'm just going to use local paths so I can get up and running. Thank you for your help. |
|
| mwagoner Replies: 22 Views: 54553 |
|
| Yes that makes sense and the puzzle pieces are starting to fall into place I think. On our existing server which is working properly we originally had all the GetWeb paths set to local paths. We then created all of our groups, which would have created all the folders in Inetpub. Later on, as you can see from the post above, we decided to administer the server remotely. So we changed the paths for GetWeb to UNC paths. Just like I'm seeing on this new server any time we made changes to group memberships on the existing "working" server it properly updated the web pages. However we haven't added any new groups to this "working" server so it hasn't ever tried to create a new folder in Inetpub. I just confirmed that the "working" server is using a local system account just like this new server. I think I would find on the "working" server that it would exhibit the same behavior if I tried to create a new group.
I will play with the new server on Monday and give the GetWeb module a network account to use. I will post my findings. |
|
| mwagoner Replies: 22 Views: 54553 |
|
| The UNC path it's connecting to is on the same server GetWeb is running on. It's connecting back to itself. We had set it up this way so that remote admin clients would be able to access these directories.
See this post http://www.notepage.net/forum/viewtopic.php?p=14173&highlight=#14173 I can try giving the GetWeb service network credentials. I'll also look on our existing server and see if I had set it up that way there too. |
|
| mwagoner Replies: 22 Views: 54553 |
|
| Ahh ha! When setting it to C:\temp\ it was able to create the directories. The web pages are normally set to \\servername\Inetpub\wwwroot\. I also tried setting with web pages to C:\Inetpub\wwwroot\ and that worked as well.
So it seems it's only having trouble with the path when it's a network share. I can't remember exactly why we configured it this way but I know there was a good reason. Also the current working server here has it set this way too without a problem. I have the share permissions set to grant "Everyone" full control. I'm not certain what would be blocking the access. |
|
| mwagoner Replies: 22 Views: 54553 |
|
| I haven't been able to work on this for awhile. I'm back at it now.
I double checked file permissions on Inetpub and wwwroot. The wwwroot folder didn't look like it had inherited all permissions from Inetpub but I've forced it too. Still no change in behavior. I also compared permissions between our one working server and this one and wasn't able to find many differences. I did notice that the accounts IUSR_SERVERNAME and IIS_WPG had permissions to these folders on the working server but NOT on the trouble server. There is still no change after adding them with the same permissions to the trouble server. I used procmon to watch for any file access to the Inetpub and Inetpub\wwwroot folders and then tried removing and adding a member from a group in PGAdmin. I didn't see any file access in procmon when doing this. I would assume if it's trying to create a folder here I would at least see some errors. Do you know what process would be trying to create the folders in Inetpub\wwwroot? I'm not sure where to look next. Any ideas? |
|
| mwagoner Replies: 22 Views: 54553 |
|
| Under the webpage subsection of group2 there is a template applied. It's guilist.htm | |
| mwagoner Replies: 22 Views: 54553 |
|
| I just double checked and yest it is.
What I've done for now is manually created the virtual directories in IIS. After doing that I removed and then added a user from a group. After doing that it populated the default.htm and index.htm files in this new virtual directory. It appears that I have a work around for now but I'd still like to find out why this is happening this way. |
|
| mwagoner Replies: 22 Views: 54553 |
|
| I think I see where you're talking about. In C:\Inetpub\wwwroot\ there is a subfolder which matches the name of one of our groups (for instance C:\Inetpub\wwwroot\group1. Inside this "group1" folder there are default.htm and index.htm files. These seem to update ok. When I add a new group though it's not creating a new subfolder. For instance I create "group2" and add some recipients but it doesn't create the folder C:\Inetpub\wwwroot\group2. | |
| mwagoner Replies: 22 Views: 54553 |
|
| Where would the web paging subfolder be? | |
| mwagoner Replies: 22 Views: 54553 |
|
| That is correct, even when making changes on the server itself, the web pages are not updating. | |
| mwagoner Replies: 22 Views: 54553 |
|
| I verified that I have full modify permissions on these folders. I also temporarily granted all users modify access. I'm still not seeing the folders created in IIS. This is happening even when I log on to the PageGate server with administrative credentials. | |
| mwagoner Replies: 22 Views: 54553 |
|
| The Web Pages Path is \\servername\Inetpub\wwwroot\
The CGI Data Path is \\servername\Inetpub\Scripts The CGI URL is http://servername/scripts/webgate.exe |
|
| mwagoner Replies: 22 Views: 54553 |
|
| We are running PageGate 5 on Server 2003 and using IIS 6. I set this server up about 4 months ago and it seemed to be working as expected. One of my coworkers created several new groups and users from a remote PGAdmin client. When I went in to look today, none of these groups had a corresponding folder in IIS. It's similar to the issue in this post:
http://www.notepage.net/forum/viewtopic.php?t=7569264&highlight= The main difference is that even when making a change to a group membership directly on the server (through RDP) it's not updating IIS. I manually created a new virtual directory by copying an existing one and then changed group membership. Doing this successfully updated the webpage. We don't create groups all that often so I can manually create the virtual directories but I'm not certain what's causing this problem. We have two separate pagegate servers (the other server is working fine) and I compared permissions in IIS and ntfs permissions of Inetpub and I don't see any differences. I'm not sure where to look next. |
|
| mwagoner Replies: 4 Views: 13828 |
|
| Changing to UNC paths did the trick. Thanks for you help! | |
| mwagoner Replies: 4 Views: 13828 |
|
| They are set to local paths:
C:\Inetpub\wwwroot\ C:\Inetpub\Scripts\ |
|
All times are GMT - 5 Hours |