Author: "France, Don (Pace)" <don.france-eds AT EDS DOT COM>
Date: Mon, 3 Jan 2000 18:29:57 -0600
Andre, Your client sign-on header indicates you're running the latest GA, not the latest fix-test... you should see the letter "f", to confirm you are running the fix-test for ADSM. August APAR fix w
Hi *SM'ers, I get Error code ANS4028E during inc backup of 3.1.0.6 NT client backing up to 3.1.2.40 AIX Server running oslevel 4.3.2.0. Strange thing is, according to V3R1 Messages docu, that this er
Andre - A look in the APAR database shows an August fix to skip the bad directory to continue with the backup, and change the error msg. http://www.tivoli.com/products/index/storage_mgt/adsm/adsercl
Author: Andre Haenni [mailto:andre.haenni AT ZKB DOT CH]
Date: Sun, 04 Oct 2015 17:36:17 -0500
Hi *SM'ers, I get Error code ANS4028E during inc backup of 3.1.0.6 NT client = backing up to 3.1.2.40 AIX Server running oslevel 4.3.2.0. Strange thing is, according to V3R1 Messages docu, that this
Hi *SM'ers, Thanks a lot to both of you, Richard and Eric, for pointing me to use the latest NT client code. I now upgraded to 3.1.0.7, that's the latest, according to the Tivoli website. Alas, the b
Andre, You could try running the backup from the gui. I had this problem once before and was able to find the offending file by running the backup from the gui. The gui shows which file it is process
Hi Andre, This sounds like APAR IC24494. Most likely it is due to a directory that exceeds the Windows MAX_PATH limit of 260 characters. Instead of skipping the offending directory, the backup client
Author: Alfred Novacek <Novacek AT POP.IDV.UNI-LINZ.AC DOT AT>
Date: Wed, 29 Dec 1999 19:23:41 +0100
Andre, some time ago I had a similar problem; on a certain NT system, ADSM backup always stopped at a certain place. It turned out to be a problem with the NTFS file system (surely, NTFS does a hard
Author: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT NL>
Date: Fri, 31 Dec 1999 09:11:55 +0100
Hi Ande! As far as I can remember I suggested you to upgrade to the latest fixtest release, not the latest standard release. I encountered the same problem as you do with 3.1.07. I upgraded to 3.1.07
Author: Andre Haenni [mailto:andre.haenni AT ZKB DOT CH]
Date: Sun, 04 Oct 2015 17:36:17 -0500
Hi *SM'ers, Thanks a lot to both of you, Richard and Eric, for pointing me to use the latest NT client code. I now upgraded to 3.1.0.7, that's the latest, according to the Tivoli website. Alas, the b