import using the gui or the blcli ?
Both give the same error
How did you create the file? does it have dos control characters in it?
Tried creating file in different ways - on local server using notepad, wordpad etc and when I ran from blcli I created a file on the appserver (windows) using vi from nsh - definitely no control chars
It now only consists of the header line and one server
I think I remember this now.. if you look in the property dictionary, in the server class there are a bunch of properties w/ the ‘required’ option checked. You are required to set a value for those iirc.
I've had to leave the site now, but I'll check that thanks
One tihng - we can add servers individually without any problem - not sure if that has any bearing on your suggestion ?
I believe that works differently than the bulk imports.
ok thanks. Will let you know the result....
I was just looking at the Server class on my VMs, and I notice that there are a quite a few properties (about 38) set to Required, yet I can add servers via a csv file with just the hostname specified. So with the issue we are seeing should I be looking for a specific property being set to required do you think?
I'm not on site for next few days, but I've asked an engineer there to send me details of which properties are set to required.
IIRC, The thing about required properties in BBSA, is that they always have a default value. That is why you can add a server and not have to set any properties. I can give it a try on my VM later today.
I tried the import with csv file and it works, below is the format of my csv file
All the servers were imported successfully and I did not set any properties.
Are there any errors in the appserver log when you do the import?
Also, look for properties that are not intrinsic but required. I’m not convinced that’s it for your case, but I saw that at another customer.
We've managed to resolve this (or at least get a work around). There were two issues all around permissions.
- The users we were using for the bulk import did not have permissions on the server area on the property dictionary.
- DISA properties in 'server' were forcing a variable component that for some reason when targeted comes up with a permission issue as well.
Work around for now was to add the permissions to the server area in the property dictionary and then remove the 'Required' flag and the default value on the DISA properties.
Thanks everyone for you time and help.
Which DISA properties?