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

Issue with Teamsite install

JS1

Hello,

We have installed Teamsite 7.1 on Windows 2003. After install was successfull we installed IIS Manager.

Once we installed IIS Manager, we are working on configuring it with iw-mount data but now we are no longer seeing "Y" drive. Can you let know what can be done to be Y drive back ?

Thanks,

Janhavi

Find more posts tagged with

Comments

Adam Stoller

Why would you install the IIS Manager after TeamSite?

If you don't see the Y drive - it's usually an indication that one or more of the TeamSite services aren't running - have you tried rebooting the server?

JS1

Is it a problem to install IIS manager later Teamsite ? do we have to go again through Teamsite install in that case ?

Yes we rebooted server, all services are coming up except Interwoven Utility Daemon service, it is not coming up. we are getting error on trying to bring it up.

Thanks,

Janhavi

Schermafbeelding 2015-08-20 om 15.30.26.jpg

RamaPS

Try this:

net stop iwserver

start TS as a domain user (by default it runs as system)

disable virus scanner

disable DEP (enable it for only windows essential services

net start iwserver

Snap 2015-08-20 at 09.32.42.png

Snap 2015-08-20 at 09.34.22.png

Adam Stoller

RamaPS wrote:
Try this:

net stop iwserver
start TS as a domain user (by default it runs as system)
disable virus scanner
disable DEP (enable it for only windows essential services
net start iwserver

Why would you want to start TeamSite as a domain user, and what do you mean by "start TS as a domain user" as distinct from "net start iwserver"?

The disabling of virus scanners and DEP are important though. In addition - locating any error messages in IWHOME/local/logs/*.log and IWHOME/local/logs/iwui/*.log might help shed some light on why the iwutild isn't starting up.

Rick Poulin

Why would you want to start TeamSite as a domain user, and what do you mean by "start TS as a domain user" as distinct from "net start iwserver"?

I'd guess he meant "configure the TS service to run as a domain user".. not that this should be required under normal circumstances.

RamaPS

Yes, I meant, start TeamSite Service as domain user, if you have access to Autonomy / Interwoven KB articles, look at KB # 49040.

Some ADs doesn't allow anonymous binds (system) and hence we need to use a domain user with certain privileges (mentioned in KB) to start TS Service.

Adam Stoller

Hmm - the support site doesn't seem to be very helpful to finding a KB article by number - I can find all sorts of references to KB 49040 - but not the actual article itself.

My recollection of the use of domain accounts for running the TeamSite service was for dealing with cases where the iw-store was mounted on a SAN / NAS device rather than on a local drive of the server. Perhaps 49040 is for a different purpose.

GoingMyWay

Try this link for the KB: https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=49040

-David

Adam Stoller

GoingMyWay wrote:
Try this link for the KB: https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=49040

-David

Thanks - this is, I think, the same KB I've used before in the past to allow for putting the backing store on a separate storage device for Windows - and I don't recall that being stipulated in the original posting on this thread - hence my confusion about why it was being suggested.

RamaPS

Given the fact that some Active Directories doesn't allow anonymous binds to get the user / groups information using a windows system account (By default TeamSite Service uses system account). This KB is originally intended to provide alternative to this issue.

However, I have seen cases where Y:\ drive doesn't come up because of lack of privileges & above trick worked out to bring Y:\ drive up. Again, this is one of the causes, there are several other reason why Y:\ drive doesn't come up, like DEP, running anti-virus on iw-store as well as Y:\ drive to name a few..

JS1

Will it matter if server is 32 bit or 64 bit ?

Rick Poulin

JS1 wrote:
Will it matter if server is 32 bit or 64 bit ?

It won't change anything in the install procedure, if that's what you're asking.

Dan_Rivizzigno

Before reconfiguring the TS service to run as a domain account, look at iwtrace.log and iwserver.log as well as the Windows event logs to see if you can figure out WHY the Y:\ drive is not coming up. You can't really do anything until you know why it's not working.

Dan

JS1

We reimaged the server and started over again. this time it worked fine, we are able to see Y drive created.

Thanks all for help on this.