Processing paths and containers with an "&" in the name

Question

So in the dark ages, someone though it was a good idea to use "&" in a storage path and in a container name.
NSM seems to be choking on this, the path errors out... any suggestions short of moving the storage and changing the ou name?

Answer 1

On 2/19/2015 3:06 PM, dbgallo wrote:
>
> NFMS Support Team;2344556 Wrote:
>> On 1/14/2015 1:36 PM, dbgallo wrote:
>>>
>>> So in the dark ages, someone though it was a good idea to use "&" in
>> a
>>> storage path and in a container name.
>>>
>>> NSM seems to be choking on this, the path errors out... any
>> suggestions
>>> short of moving the storage and changing the ou name?
>>>
>>>
>> dbgallo,
>>
>> Which version of NSM are you using? And what error do you get, in which
>> event state and action?
>>
>> -- NFMS Support Team
>
> 4.0, the ou and storage name is "PM&R"
>
> the code is from turning the logging for files up to debug:
> ~~~Begin error~~~~~
> 01 2015-02-19 13:57:25 -18000 3 8007 20045 7f1c9eb93700
> NWUDirHandleAllocate() - Called CCNWAllocTempNSDirHandle2(0x02C80016
> ["SOMESERVER-SERVER"], 0 (3), "PM&R" / [#3 L"PM&R"], 4, ..., 4),
> rc = 0x0000899c (35228), Result = 127.
> 01 2015-02-19 13:57:25 -18000 5 8006 20045 7f1c8ffff700 TM:
> TaskWorkerThread() - Processed Task ID
> "6825D5EE506FD2018E6D44BF0109FE59", final status = 0.
> ~~~~ end error
>
>
dbgallo,
We've tracked down this error, and have an updated NSM Engine build for
you to test with. Could you send us an email at
[email protected] to follow up with this? Thank you.
-- NFMS Support Team