Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12 REPLIES 12
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hi,
following are the steps to configure,
- SDW needs to be installed with the DFM server settings like DFM server name/ IP Address, User name, PWD. ( The Username should at the least have DFM.Core.AccessCheck in the global scope on the DFM )
are you sure you have given the user name with the DFM.Core.AccessCheck permission.
then try to set SDW with the information.
thanks, Prabu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
the User has DFMGlobal Full Control.
EU.BSHG.COM\MCH-sds_tdfm | GlobalFullCo... |
regards Soeren
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Is the hostname (mchwtdfm01 ) of DFM is pingable from the SDW machine?
-KJag
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Its on the same System, and i tried also with IP. And yes its pingable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
DFM Zapi failed to connect to the DFM server 'mchwtdfm01'.
To me this means that the user who is running the SDW service is not able to connect to the DFM server.
Can you please check the below points on the DFM server
Make sure DFM server is running & using port no. 8088
(Run the below commands & check
dfm service list
dfm option list serverHTTPPort)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
well, all services running and http port is 8088
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
if DFM is windows machine,
make sure you have created a same user under Local Users and Groups in windows.
creating a user in DFM doesnt create a user in windows,
also you can use the following command.
sdcli dfm_config set -host mchwtdfm01 -user MCH-sds_tdfm -pwd XXXXX
no need to give domain name too. try this hope it works.
thanks, Prabu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
DOH! i forget this Point, i will do it after Eastern and try again and give then full pts. Thanks for the hint.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
DFM authenticates users based on the operating system it is installed on and expects an existing user in the environment.
Solution
Windows environment:
Specify a user local to the Windows Server, a Domain user or group.
Anyway, i createt a user local on the System and put him direct to the Administrators. dfm user add username
But i still get the error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
you mean still you are facing the issue ????
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yes.
Creating ConfigManagement web service client...
A FaultException<SDResult> occurred:
DFM Zapi failed to connect to the DFM server 'mchwtdfm01'.
The operation completed successfully.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just encountered the exact same error when running the command: "sdcli dfm_config set -host <dfm_server> -user <domain>\<user_name>"...
A FaultException<SDResult> occurred:
DFM Zapi failed to connect to the DFM server '<dfm_server>'.
The operation completed successfully.
I tried adding my user acct to the local admin group on the Windows server, my user also has GlobalFullControl to the DFM server... didn't seem to work. So, I re-read this thread and removed the Domain name from the cmd as suggested by Prabu and it worked.
