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; } } }

Virtual Y: Drive on Win2k3

rpollock

Does anyone know if you can install Teamsite 6.5 on Win2k3 to without using the default install mount of the virtual Y: drive? Can you use the base OS to mount a Y: and point to it? Can it be a separate partition?

Any and all input is appreciated.

Find more posts tagged with

Comments

Migrateduser

You can change the location of iw-mount with an option in iw.cfg, but it sounds like you are after something a bit different than that.

I understand you to say that you have an existing drive containing real files that you want to somehow use as your content store and point TeamSite to it. That won't work. Can you perhaps elaborate a little bit on what your goal is?

rpollock

The long and the short of it is that we are noticing that Win2k3 is not liking the Y: drive. It is becoming unavailable although we can see the actual files in the iw_mount directory. We are trying to get around using the Teamsite default Virtual Drive install and manually configuring a Y: Is it possible? I'm not sure. Just exploring to see if it would eliviate or problem.

We also have a support call in place on the error, but I figured no harm or foul in checking out here on Devnet.

Migrateduser

Now I'm very confused... On windows, you set iwmount to a particular drive letter (or leave it as the default Y Smiley Happy

and that's where the IFS driver will mount the virtual filesystem. Where is this iw_mount directory that you are speaking of?

rpollock

My question is esentially why do we need to use the virtual file system. Can we setup teamsite without it? What is it really doing? To be honest it seems like poor design to me.

Adam Stoller

The virtual file system is allowing you to have 500 workareas on a single branch without having to waste a ton of diskspace on 500 copies of every single file within the branch.

If you don't want to use the virtual file system - I suggest you find a different product.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

In reply to:

If you don't want to use the virtual file system - I suggest you find a different product.

Absolutely. When you get right down to it, the virtual file system is TeamSite. Everything else is just icing on the cake. Now, admittedly, the way it is often deployed, users don't get the benefits of the virtual filesystem, but that is an indication that they either chose the wrong product for their needs, or that they deployed it incorrectly, not that there is anything wrong with TeamSite itself.

The original poster really needs to review the architecture section of the Administrator Guide. Until you grasp the way the various pieces of TeamSite fit together, you are going to spend a whole lot of time fighting with it, getting it to do things that it isn't intended to do. Now that we have definitively identified what you wanted to do and decided that you can't, we might want to start looking at when/why your Y: drive is disappearing.

First, under what circumstances does it occur? Secondly, are there any useful tidbits in iwserver.log or iwtrace.log? When the Y: drive is down, what does iwstat -c return?

rpollock

Thanks for all the input. From a architectural point of view I am not a big fan of 'hard coding' a drive, but I can see the value of the virtual space. My question was originally more in line to get it to play nice with us. I'm sure it will be of benefit moving forward. Once we get a solution to the gpf problems, I'll post it on here. As this is my first experience with Devnet and the product I am keeping my nights busy reading ;~)...

Adam Stoller

Let's start over here.

Is the problem that you have an issue with "Y" being used as the drive for TeamSite?
- or you have a problem with *any* drive being used?
- or you don't mind using "Y" but it's not working reliably for you?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

He's a step ahead of you there, Adam. See the third post on the thread...

rpollock

Sorry for the long delay in updating this thread, but it has been this long working with support to identify and fix the problem. It appears that the crashing of the Y: and the ultimatelty the server is a result of Microsoft's tightened security policies in Windows 2003 which results in the problem arising on multi-CPU boxes. Interwoven has mentioned that they are working on a fix.

Thanks for all the input guys.

Migrateduser

Hi,

I am running 6.1 on Windows 2003 box. I never experienced any issue with the Y drive. Have you tried using 6.1 on Windows 2003 box? What kind of security setup issues are you having on Windows 2003 with 6.5?

Regards,

aga1296

Hey,

We are having the same issue. Wanted to know if you have a ticket number that we can tell IWOV support to reference? If so, please respond with ticket number and name of support rep.

Could you send version and service pack info for win2k3 and iwov also.

We are running win2k3 service pack 0

IWOV 6.1.0 Build 33333

no IWOV service packs installed.

Thanks,

rpollock

We have been told that this is a 6.5 with Windows 2003 issue, but that doesn't mean it isn't a 6.1 issue either. You will have to check with your support person.

Currently it is on a Win2k server with no SP
IWOV 6.5 with no service packs.

As for the support #, I will post the resolution when we receive it. (i.e. Fix) I would mention to your sales/support rep that you know the issue is being looked at by some of the fine folks in Bethesda(I believe). I'm not comfortable posting the support number in an open forum.

Wendy

We installed Teamsite 6.5 on Windows 2003 several weeks ago and we're having troubles that I'm hoping someone can help me with.
Teamsite will freeze up now and then, sometimes logging us off. When/if it comes back up the client machines that have a drive mapped to the Y drive can no longer get to their drive. For some reason the mapped drive becomes unavailable. When we try clicking on it a window pops up saying the 'Parameter is incorrect'. When we log onto the Teamsite server the Y drive is there and functional. It's only those drives on the Client PC's that are mapped to the Y drive that become unusable. We rely on those mapped drives for editing and importing files. The only way we can recover from this is to reboot the server.
Has anyone else experienced this? Does anyone have a solution?

rpollock

That is very similar to our problem. We have been told by support that we might expect a patch this week to solve this problem. As mentioned it apparently has something to do with the Teamsite coding and its ability to 'get along' with the windows 2003 security and multiple CPU boxes. Call support, as I am not sure on the status of the 'fix' myself.

I wish I could be of more assisitance.

rpollock

We haven't tested it yet - that is today's fun task - but Patch 1557 is supposed to fix the problem.

rpollock

Sorry for the long delay on the followup, but the patch did resolve this issue for those of you who read this thread in the future.

ProfessorX

same problem here going to apply the patch

Thanks in advance!
win2k3 TS 6.5 sp1; OD 6.0.1; DD enabled
The Professor-

ProfessorX

Found out taht I have TS 6.5 sp1
Should sp1 include the patch?
Can I still install the patch even with sp1 installed

Thanks in advance!
win2k3 TS 6.5 sp1; OD 6.0.1; DD enabled
The Professor-

anisha

You might want to refer to the support site and Release Notes.

rpollock

The SP1 should have taken care of the problem, well at least it did for us. I'd open a support ticket as they will review all the logs and diagnostics.