IFS-21000: Session is not connected or has timed-out

Question

Hi folks,
I am getting the error message "IFS-21000: Session is not
connected or has timed-out" when uploading the following XML
command:
<?xml version = '1.0' standalone = 'yes'?>
<SimpleUser>
<UserName>tuser1</UserName>
<Password>tuser1</Password>
<HasPrimaryUserProfile>TRUE</HasPrimaryUserProfile>
<HasHomeFolder>FALSE</HasHomeFolder>
<HasContentQuota>FALSE</HasContentQuota>
<HasEmail>FALSE</HasEmail>
<PrimaryUserProfileAcl>Protected</PrimaryUserProfileAcl>
</SimpleUser>
Why?

Answer 1

Hi guys,
thanks for the feedback, I did get a response on metalink that
answers my questions. Here it is if you are interested...
An example would something like this.
<?xml version = '1.0' standalone = 'yes'?>
<SimpleUser>
<UserName>fred</UserName>
<Password>fred</Password>
<DirectoryUserAcl reftype="name">Private</DirectoryUserAcl>
<DistinguishedName>fred</DistinguishedName>
<DistinguishedNameSuffix>.fthw.siemens.de</DistinguishedNameSuffi
x>
<EmailAddressSuffix>@fthw.siemens.de</EmailAddressSuffix>
<HasEmail>true</HasEmail>
<EmailUserProfileAcl
reftype="name">Private</EmailUserProfileAcl>
<AdminEnabled>false</AdminEnabled>
<CanChangePassword>true</CanChangePassword>
<HomeFolderRoot>/home</HomeFolderRoot>
<HasHomeFolder>true</HasHomeFolder>
<HomeFolderAcl reftype="name">Private</HomeFolderAcl>
<HasContentQuota>true</HasContentQuota>
<ContentQuotaEnabled>true</ContentQuotaEnabled>
<ContentQuotaAcl reftype="name">Private</ContentQuotaAcl>
<ContentQuotaAllocatedStorage>10000</ContentQuotaAllocatedStorage
>
<HasPrimaryUserProfile>true</HasPrimaryUserProfile>
<PrimaryUserProfileAcl
reftype="name">Private</PrimaryUserProfileAcl>
</SimpleUser>
2. It would depend on the following:
<PrimaryUserProfileAcl
reftype="name">Private</PrimaryUserProfileAcl>
<DefaultAclsBundleName>userAclBundleForClasses</DefaultAclsBundle
Name>
<DefaultAcls>MyAclBundleForClasses</DefaultAcls>
However, there is a problem with current versions (bug1736384,
unpublished) in which you can't use XML to set the default ACL
to an existing property bundle.
According to the bug the workaround is to "use Java or the Admin
utilities tasks
- "CreateDirectoryuser" to create a User
and "CreatePropertybundle" to create a Propertybundle that
represents the defaultACLs
- "CreateUserProfile" and set the DEFAULTACLS attribute to the
bundle ""