Highlighted
Absent Member.
Absent Member.
1666 views

163 : An illogical condition has occurred.

Hi,

we're trying to migrate home directories from a OES2 server to a windows (AD) file server. Most of the homedir is copied, but after a while we get the "163 : An illogical condition has occurred". Is there a way to figure out what this is?

--
Frode
0 Likes
2 Replies
Highlighted
Absent Member.
Absent Member.

fsjovatsen;2235156 wrote:
Hi,

we're trying to migrate home directories from a OES2 server to a windows (AD) file server. Most of the homedir is copied, but after a while we get the "163 : An illogical condition has occurred". Is there a way to figure out what this is?

--
Frode


This is more than likely to do with Storage Manager trying to migrate folder(s) which have non-standard characters in the foldername. We have gone through a similar exercise of migrating from eDirectory to AD and hit this problem on several occasions. We are a university with international students so can probably guess the extent of the problem! Interestingly, right clicking the home directory on the Novell side and choosing 'Novell/NetWare Copy' the folders migrated with no problem. I did raise this issue with Condrey who sent several updated versions of the NSM Client and Agents but none were able to resolve the problem. In the end I just had to copy the failed homedirs by hand.
In addition, some very deep folder structures will not copy from eDirectory to AD because of the maximum path length of 256 characters on the AD, although this can be confirmed as the cause because 'Novell/NetWare Copy' will also fail!

Mike
0 Likes
Highlighted
Absent Member.
Absent Member.

On 10.12.2012 18:26, cczpolak wrote:
>
> fsjovatsen;2235156 Wrote:
>> Hi,
>>
>> we're trying to migrate home directories from a OES2 server to a
>> windows (AD) file server. Most of the homedir is copied, but after a
>> while we get the "163 : An illogical condition has occurred". Is there a
>> way to figure out what this is?
>>
>> --
>> Frode

>
> This is more than likely to do with Storage Manager trying to migrate
> folder(s) which have non-standard characters in the foldername.


Yep, most likely character issue..

See the NSM agent log files for more details, it will tell you the
filename that has this Illogical condition.. fix that and continue.

I migrated 12M files last summer, and got plenty of these.. most were:
- last character of folder was empty space " " - can happen when u
copy&paste names
- some special characters.. from foreign students or unzipping some
weird packages

I made enhancement requests for NSM that it would continue the migration
process even when getting these 163 errors - just log them to errorlog
somewhere.
Now it just halts jobs 😕

sk

HAMK University - OES, NW, GW, NCS, eDir, Zen, IDM, NSL - www.hamk.fi
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.