nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

.NET pages not rendering in TeamSite.

System

We just installed the .NET framework on our TeamSite server and tried a few very simple .aspx pages. However, we receive the following error when trying to view a page in a workarea (e.g., Default.aspx):

"Access denied to 'Y:\default\main\uam\WORKAREA\load\\iw-mount\default'. Failed to start monitoring file changes."

The error page is also attached to this post.

I also followed the suggestions of the following KB articles:

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=49613
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=49473

In short, the articles say that you have to add the “ASPNET” user to the “TeamSite Web Preview” group, but that didn't seem to help. Any hints would be greatly appreciated.

Environment: We have TeamSite 5.5.2 on Win2K Server (.NET framework installed).

Thanks,

Dan Pike
Portland General Electric
dan_pike@pgn.com

Find more posts tagged with

Comments

Migrateduser

Funny that one article starts "TeamSite supports .NET" and it doesn't really, and certainly doesn't give any best practices. So you even get marketing **** on the support site.

I remember that it does something different if you install the .NET framework before TeamSite, but I can't remember what the problem was (might be worse than this one).

We hacked it on my last project. I believe the issue is that .NET wants to write caching files or some kind of status indicators to a directory that was really a branch (maybe Y:\default), which is readonly. So rename the iw-mount virtual directory in IIS, create a new one that points to a filesystem that is writeable, and create a new one within that that points at Y:\default. Or something like that, it eventually worked.

I bet that this is just the tip of the iceberg for you though. At GearUp some guy from Scandanavia gave an entire presentation about how TeamSite doesn't support .NET and they are waiting for engineering to provide a fix.

Edited by john on 02/06/03 10:23 AM (server time).

Migrateduser

Thanks, John. I really appreciate your insight. Very interesting! I was always under the impression that TeamSite was 100% compatible with the .NET framework (at least that’s what Interwoven seems to indicate).

I tried the hack that you suggested:

1) Renamed iw-mount to iw-mount-backup
2) Created a new “iw-mount” virtual directory and pointed it to C:\temp
3) Created another virtual directory under the new iw-mount called "default" and pointed it to Y:\default.

.asp and .htm pages render just fine. However, .aspx pages product a similar error as before:

"Access denied to 'Y:\default\main\uam\WORKAREA\load\\iw-mount'. Failed to start monitoring file changes."

I will keep fiddling with it. Failing that, I will escalate this to IW support.

Thanks again,

Dan Pike
Portland General Electric
dan_pike@pgn.com

Migrateduser

I found my exact notes. You may just have to play with it for a while to get it to work, maybe even reboot.

In the IIS configuration panel rename the iw-mount virtual directory to something that indicates that it is the default iw-mount.

Restart IIS.

Create a new virtual directory named iw-mount, pointing to an empty directory that the ASPNET user has full control of.

Within the new iw-mount virtual directory create a virtual directory named default aimed at Y:\default (note that Y is in uppercase and default is in lowercase).

The ASPNET user should be added to the TeamSite Web Preview group.

Adam Stoller

"Access denied to 'Y:\default\main\uam\WORKAREA\load\\iw-mount\default'. Failed to start monitoring file changes."

The part in bold looks very suspicious - Can you post your iw.cfg file? I'd be curious to see what you set for your proxy settings?

Also what is the full path to the aspx file? (just so we can use it to visually figure out what proxy might be doing)

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

Install the .NET framework, put an ASPX page in any directory in any workarea, and click on it.

Migrateduser

Hi, Fish. Thanks for the reply.

I tried John's hack. It did work on a simple .NET web. I still need to verify with a "real" site. However, it's a hack that we'd like to avoid if possible.

I've attached our iw.cfg just in case there's a nugget of information that might help. We're proxying other branches, but not the .NET one.

I have escalated this to Interwoven Support. I'm hoping that they have some answers.

Thanks,

Dan Pike
Portland General Electric
dan_pike@pgn.com

Migrateduser

Problem solved (we think). This is one of those situations that makes you kick yourself for not seeing the obvious. Thanks to John and Fish for responding to this post.

If you set the workarea as an "Application" directory, then the .aspx pages render just fine.

1) From within the IIS console, navigate to the workarea (In our case "\iw-mount\default\main\uam\WORKAREA\load")
2) Right-click on the workarea and click on "Properties"
3) Under "Application Settings" click on "Create"

The only issue that we ran into after this was that the .NET site could not find the "C:\Inetpub\wwwroot\aspnet_client" directory. This directory contains some key javascript files used by .NET, and is automatically installed with the framework. To fix this, we had to add a virtual directory at the root of the workarea:

1) Right-click on the workarea
2) Select New -> Virtual Directory
3) Enter "aspnet_client" as the Alias
4) Enter "C:\Inetpub\wwwroot\aspnet_client" for the Directory
5) Use the default permissions

Sorry for the fire-drill, and I hope this helps others who are using .NET with TeamSite. Smiley Happy

Dan Pike
Portland General Electric
dan_pike@pgn.com

Gregg Faus

Well I just took the plunge as well and I need some assistance. After installing the 1.1 framework, I'm getting the following error when a previewing a test page:

Server Error in ''/iw-mount/default/main/projects/demos/dotnettest/WORKAREA/common/web' Application.
------------------------------------------------
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: CS0016: Could not write to output file 'c:\WINNT\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\iw-mount_default_main_projects_demos_dotnettest_workarea_common_web\ffea9148\5c7f82ff\mlkehyvl.dll' -- 'The directory name is invalid. '

Source Error:
[No relevant source lines]

This is after putting an inline helloworld.aspx page in a test workarea. This is the full url to the page:
http://machinename/iw-mount/default/main/projects/demos/dotnettest/WORKAREA/common/web/helloworld.aspx

Here is what I've done so far:
1) Installed .NET Framework 1.1
2) Added ASPNET user to TeamSite Web Preview group
3) Renamed my iw-mount VD to iw-mount-default
4) Restarted IIS
5) Created new VD under website called 'iw-mount', pointed it to a temp directory called 'c:\temp\iw-mount\' (see cacls statement below)
6) Created new VD under iw-mount called 'default'. Document root is 'Y:\default'
7) Executed the follow cacls statments to ensure proper ASPNET user permissions:
cacls "C:\WINNT\Microsoft.NET" /T /E /C /P ASPNET:R
cacls "C:\WINNT\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files" /T /E /C /P ASPNET:C
cacls "C:\WINNT\temp" /T /E /C /P ASPNET:C
cacls "C:\WINNT\assembly" /T /E /C /P ASPNET:R
cacls "C:\temp\iw-mount" /T /E /C /P ASPNET:C
8) Created application space under the above workarea
9) Rebooted

Any help would be appreciated. I'll post more information in a while.

Gregg Faus

I've resolved my problem. It wasn't TeamSite related. Through some information I found on the newsgroups, I had one of my Windows temporary system variables (TMP) set to a path the ASPNET user didn't have rights to. I just changed the path of this variables to "C:\WINNT\temp\", rebooted, and everything is working great.

Hopefully my previous post provides an installation guide (thanks to john).