Zoltan
I think the problem is the colon in the file name.
Windows has the capability to write multiple streams to the same file. The
streams are differentiated by a colon and the the stream id.
At least that’s the gist of it. See
https://www.owasp.org/index.php/Windows_::DATA_alternate_data_
Hi Arnaud,
did you run tsm server instrumentation.
It could help to identify where the issue is.
We have tsm server that is connected to FS900 and vtl with v5k and no perf.
issues.
Best regards
Chavdar
On Wednesday, April 11, 2018, PAC Brion Arnaud
wrote:
> Dear Stefan,
>
> Thanks a lot for yo
Has anyone seen these kind of errors? A user has been having these errors
for a long time (they manage their own box and thus din't notice these
errors for 9+ months)
TSM return code : 104
TSM file : ..\..\common\winnt\psmech.cpp (6583)
04/10/2018 22:58:04 ANS0361I DIAG: NTNamedS
Since there is no command in the log, this is not a adm. script. Maybe it's a
enterprise configuration. (search words: configuration manager, profile).
I assumed that the problem is in replication, because you can really forget to
remove the server from replication before delete server.
Efim
>
Very interesting - especially since none of these servers had anything to
do with replicating to each-other. All of my servers, including the one we
shut down, were source replicas - not target. I am guessing that since we
did "export to server" for the nodes we moved from the one we shut down, i
Hi
I think you forget to remove this server from replicating server list.
REMOVE REPLSERVER
Use Query REPLServer to see the guid
Efim
> 11 апр. 2018 г., в 14:47, Zoltan Forray написал(а):
>
> We just decommissioned an ISP server (1 of 6) and now 2 of the other ISP
> servers are constantly iss
Dear Stefan,
Thanks a lot for your very kind offer !
Without underrating the power of this list, I however doubt that we will able
to find a solution that easily : we opened a case with IBM and involved
EMC/Dell as well, so far without much success, even after 5 months intensive
monitoring a
We just decommissioned an ISP server (1 of 6) and now 2 of the other ISP
servers are constantly issue these messages and we can't figure out how to
get them to stop:
4/11/2018 7:41:41 AM ANR1663E Open Server: Server HADES not defined
4/11/2018 7:41:41 AM ANR1651E Server information for HADES is no
