I did find the issue. When the software installed it did not create a Default label template or a Default Media Pool. After I created both based off another installation I have, everything worked. The cause is one of two factors, the system name has a dash in it and has a long FQDN (over 65 characters). When I tried to create the default label template and used the system name as is it tried to interpret the dash as a range like 001-999. I had to create the Default label and pool with no dash in the name. After that all was well.
chadm1
6 Posts
0
June 7th, 2012 04:00
I did and got the same result.
I did find the issue. When the software installed it did not create a Default label template or a Default Media Pool. After I created both based off another installation I have, everything worked. The cause is one of two factors, the system name has a dash in it and has a long FQDN (over 65 characters). When I tried to create the default label template and used the system name as is it tried to interpret the dash as a range like 001-999. I had to create the Default label and pool with no dash in the name. After that all was well.
nmc2
268 Posts
0
June 6th, 2012 20:00
Can you try without wizard. Use normal method and see if it creates AFTD device.
Lets confirm if its related to wizard.
Regards,
Prajith