I am trying to create a template in OME and I keep getting this result:
Starting configuration file export on the target : .101.xxx.210.yy
Network share IP for this task: 101.xxx.4.yy
Retrieved the file share settings.
Extracting config XML from target: (101.xxx.210.yy)
LC023 : Cannot access network share.101.xxx.4.yy\ServerConfig
What do I need to do to fix that?
For serverconfig to work, you need to provide the share credentials under File Share settings option in the deployment tab. You can get more help from the OME 2.0 Server Configuration Tutorial Videos published at en.community.dell.com/.../1989.openmanage-essentials
This does appear to be a file share credential permission problem. Try to reenter the file share credentials. If that still doesn't work, you can check the share on the network and file system to make sure the user was added to the folder security.
I'm getting this too - even tried Everyone:Full Control and it still won't work.
Any more logs I can look at, or is this a bug in 2.0.1?
Very frustrating as always with OME...
Thanks for the post.
Just to reiterate, Pupul’s comment (the last one on that item) is the correct approach when looking into this type of share issue.
The error that Dwayne is getting is being generated by the LifeCycle Controller on the server which is trying to export its configuration. For some reason, that server cannot access the file share (which is located on the OME Server). So for Dwayne, we need to figure out why the target network share (on 101.xxx.4.yy) is not visible (accessible) from the other server (101.xxx.210.yy). Most of the things to check have been mentioned in the thread – verifying that the correct IP address and password have been specified for the share, verifying that it isn’t blocked by a firewall,
The best advice I can offer is that visibility to the share, from the server that’s been told to export, can (and should) be verified independently of OME. In 101.xxx.210.yy, open Windows Explorer, specify “\\101.xxx.4.yy\ServerConfig”, and enter the same credentials as entered in OME for the file share. If the file share can be accessed that way, then the LC should also be able to create a file in that file share and export its configuration to it. (The user may have to also try adding a file to the file share from the Windows Explorer window in the remote server, to verify the creation capability.)
In this case, OME has asked the iDRAC on another server to do something (export its configuration to a file in a specified file share), and the other server says that it cannot access the specified file share. So OME is reporting what the iDRAC/LifecycleController says. If the file share can be accessed via Windows Explorer (as indicated above) from the server that’s supposed to export its configuration, but the LC on that server cannot access the share, then it’s something we’ll have to investigate further.
And as always, feel free to open a ticket at 800-945-3355 so we can get support to take a closer look if needed.
Seems that SPN Target Name Validation in the Windows security policy will prevent the RAC from being able to connect. Also using special characters in the password fails as well.