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

System generated usernames

manish_rathi

TS671, Win Server 2003
--------------------------

In a workarea, I see files modified by a user name as S-1-5-21-221471938-1439873204-426373432

There is no such user. From where does, such a name come from ? WHen I am trying to invoke a workflow using new_job, I am get error "Workflow owner S-1-5-21-221471938-1439873204-426373432 is not a valid user
Error :00925 : No such user
Error:925 : No such user"

It looks like a system generated number. But how come there is a system generated number, when TS knows that who is modifying this file or which role is accessing file or WA or branch ? Anyone in an enterprise environment can access TS after credential check. So even if someone is using a common name, still in TS that user is registered as an authorized user. So why such a weird user name is there ?

If I am logging in with authorized credentials (which is common for 5 users), then why do I still get such a number ? When I am trying to initiate new_job, because of such a number, I am getting error "No such user". Please explain this behavior and show me solution. I was able to use another wf.

Find more posts tagged with

Comments

Rohan_t1

There are plenty of posts in devnet on this. Try searching for "iwidmap" and reading it in manuals. One such post

manish_rathi

I found from knowledge base that if a user is deleted, then this SID will display as an owner. But the username I am using is not deleted, then why am I getting such an error ?
What shall I do in this case ?

Thanks

nipper

Did the backingstore get migrated from another server ?

Was the user deleted and added again ? Did you go from local logins to domain ?

Try removing the user form TS and adding them again.

Somehow the SID changed, that is more of a MS issue than TS

Adam Stoller

Is the owner of the workflow hard-coded to a userid that no longer exists (on this server)?

mart2001

Was the user a local user or a domain user?

Vendim Birbili

Is the owner of the workflow hard-coded to a userid that no longer exists (on this server)?

I read that when use workflow to trigger a deployment from one environment to another the owner appear to by System instead of the user that trigger the workflow. is there anywhere to handle that so the owner appear correctly on the receiving side?

thanks

afterBlacking.png

beforeBlacking.png

ISCBorisB

the owner appear to by System...

That depends on how WF Model (or Template) of this job set relevant Task Owner. Task owners may of course differ from Job Owner and from each other.

is there anywhere to handle that...

Both Workflow owner and Tasks owners are configurable, WFM's label is well, "Owner". What's the problem?

map.png

map1.png

Vendim Birbili

That depends on how WF Model (or Template) of this job set relevant Task Owner. Task owners may of course differ from Job Owner and from each other, Group Task owner is identified during flow and may differ for multiple passes, etc...
Both Workflow owner and Tasks owners are configurable, WFM's label is well, "Owner". What's the problem?

The Owner is set as $IW_USER but when the files get deployed the owner on the receiving end show as SYSTEM...
attached is the .ipm file

ISCBorisB

It *seems* that you have some issues with Open Deploy that have nothing to do to Workflow proper.
It also *seems* that you use Windows. If that's indeed the case, you'll have to play with your
Deployment configuration, WF Model won't help you.

Remember, upon Deploy Target Files get created/modified by the OD Receiver Process. Receiver OS
and corresponding processes will have different SIDs/ACLs (as long as it is indeed Windows).

So... Take a look at OD Configuration "transferRules" Tag, attribute "preserveAcls", see if it helps.
If it doesn't, read [post=191885]this post[/post] and create dedicated Thread following these guidelines.

Vendim Birbili

Remember, upon Deploy Target Files get created/modified by the OD Receiver Process. Receiver OS
and corresponding processes will have different SIDs/ACLs (as long as it is indeed Windows).

So... Take a look at OD Configuration "transferRules" Tag, attribute "preserveAcls", see if it helps.
If it doesn't, read [post=191885]this post[/post] and create dedicated Thread following these guidelines.

sorry my bad,
it is windows and TS7.3.2. i tried the preserveACL but that doesn't work either.