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

6.1 Imports files as SYSTEM

lhdavis

We have recently upgraded our Windows 2000 Development environment with W2K SP4 and from TeamSite 6.0 to 6.1. Now when I import a file, it lists SYSTEM as the owner rather than the user doing the import. As a result, all of my imported files do not show up in my CCS WIP component. As the WIP is what most of our users use to submit workflows and deploy content, this is a big issue for us.

Am I missing a setting somewhere that says to set the owner of imported files to the user doing the importing? Has anyone else on 6.1 seen similar behavior?

Other information that could be beneficial is that we use LDAP for our user authentication. Also, our TeamSite 6.0 Production environment does pick up the user doing the importing rather than SYSTEM. Any and all information is much appreciated.

And I do have a support case open on this Smiley Happy

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

Find more posts tagged with

Comments

Adam Stoller

Open a support case - I believe there's already a bug report open on this as I know of at least one company that determined they could not use CCS because of this problem (I wasn't directly involved, so I'm not naming names - sorry)

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

Migrateduser

I don't see this behavior, but if you import and are in the Windows
Administrators group on the server, the files will not be owned by
the TeamSite user that imports them, but rather they will be owned
by Administrators. That's a Windows-ism.

Is that what you're seeing, by chance? I know you explictly
said user SYTEM, but ...

There weren't any changes of consequence between 6.0 and
6.1 to file import on the back end CGI, that I can recall..

Regards,

Jason Heirtzler
Interwoven Engineering

Migrateduser

Could it be a W2KSP4 thing, unrelated to the IW patch? Which botch of windows is running in the working environment?

mgal

I tested this on Windows 2000 sp4 TeamSite 6.1 (with and without sp1) could not reproduce the issue. But iam not using LDAP. I would suggest to test this with local users and see if you(Luke) can reproduce this issue.

Thxs,
Mohammed Gazal.

lhdavis

I will create a local domain TeamSite user in the morning and see if that helps.

I also will test with an LDAP account that is not a member of the Administrator's group (as I am on our Development server). Thanks everyone for your responses!

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

lhdavis

Some additional information for you after this mornings test. To clarify the issue the OWNER is correct but it is the MODIFIED BY value which is incorrect.

I tried my two test cases and both are still showing the imported file as last modified by SYSTEM. Again these two test cases were the following:

1) I will test the file import behavior with an existing LDAP user who is not in the local server's Administrators group.

2) I will create a local account on the server and see what happens when they import a file (to see if it is related to LDAP)

When I view the properties of the imported file in both cases, the owner of the file is correct so it seems like it is just the "modified by" value which is incorrect. I have tried this in multiple workareas.

I know for a fact that when we imported files in this Development environment prior to our 6.1 upgrade that it listed the user doing the import as the "modified by" value because imported files showed up in their WIP.

Again, any assistance is much appreciated.

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

elseIf.rptdesign

Migrateduser

Is it only for new files being imported, or does it also happen for files being uploaded after edit/download?

Just curious.

iwovGraduate

Does this happen for all users ?
The domain that TS server is a member of and the domain users belong to are same ?

lhdavis

While logged in as my LDAP authenticated account that is part of the local Administrator group, I downloaded a .jpg file owned by a local domain account, TSDEMO_TEST_USER, edited the file in Paint and saved it, kept it as a Work In Progress, and the file was uploaded back into TeamSite.

Now the file is owned by BUILTIN\Administrators rather than the original local domain account and has been modified by SYSTEM.

So it does seem to occur with files that are uploaded after the edit/download process.

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

lhdavis

So far I have identified that it occurs for the following sets of users:
1) AD authenticated users in the local Administrators group
2) AD authenticated users NOT in the local Administrators group
3) Local domain users NOT in the local Administrators group

I am unclear as to what you are asking in the second question though. Here's what I can tell ya though:
The server domain is WBDT for example. The domain users I've tested with are WBDT\TSDEMO_TEST_USR (log into TeamSite as TSDEMO_TEST_USR and select WBDT as your server). I also have a WBDT\TSIMP_WBDT account that is a member of TeamSite Web Preview and the Users group.

Did that provide you with the information you wanted?

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

lhdavis

After working with Support, I ended up having to add our local "TeamSite_Admin" and "IUSR_<server>" accounts to the TeamSite Web Preview group and everything works fine now. For some reason, only the "TSIMP_<server>" id was in this group.

So keep an eye on this if you upgrade because it's not something I configured myself. Thanks everyone for the test cases and ideas!

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

lhdavis

One final follow up to this.

I have since removed my local "TeamSite_Admin" user from the TeamSite Web Preview group, rebooted the server, and everything continued to work as expected.

Then I removed my local "IUSR_<server>" user from the TeamSite Web Preview group, rebooted the server, and everything continued to work as expected.

So I think that net-net all I had to do was reboot the box one more time after doing the upgrade. Weird.

Anyway, thanks again!

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

Migrateduser

Sounds more like a Windows issue than an IW issue, unless IW is caching bad data.