Trying to connect Oblisync (content transfer) to a remote install returns an error of a bad URL, Username, or Password.
search cancel

Trying to connect Oblisync (content transfer) to a remote install returns an error of a bad URL, Username, or Password.

book

Article ID: 44327

calendar_today

Updated On:

Products

CA Business Service Insight

Issue/Introduction

If I go into the Content Transfer Environments window and try to add a remote environment, I get an error that it cannot connect and to check the URL, username, and password.

This may also occur if you try to edit the default LOCALHOST environment.

 

Environment

CA Business Insight

All Supported Operating Systems

Cause

  1. The first potential cause is of cause a bad URL, username, or password. To verify this. Open a second tab in the browser and see if you can manually login to that site from the machine you are on using the URL, username, and password you are trying to use.
  2. This may be caused by a problem with the certificate which will be discussed below.

Resolution

See if you are able to connect to the local machine (not the remote box) where Oblisync is running using the path:

http://<machine name>/oblisync/api/ObliSyncRepository.svc

If you get any kind of certificate error then re-register the certificate by doing the following:

  1. Run MMC on the Web Server where Oblisync is running to bring up the Microsoft command console.
  2. Click on File and Add/Remove Snap-in
  3. Choose Certificates under available snap-ins and click Add
  4. When prompted, be sure to select "Computer Account". This is not the default and must be selected.

  1. On the next screen choose the default of local computer.
  2. click OK.
  3. Now on the MMC console you should be able to tunnel down to trusted people and certificates as shown below:

  1. If you have an existing Oblisync certificate then remove it.
  2. Right-click on the right side of the screen and under all tasks select "import"
  3. Browse to %OG_HOME%\Oblisync\Cert
  4. Select "All Files" so that you can see the pfx certificate file and not just the cer file:

  1. Select the .pfx file and NOT the .cer file.
  2. When prompted for the password, it is: oblisync
  3. Place the certificate in the "Trusted People" store which should be the default. Continue until you get a prompt that it was imported successfully.
  4. Check the path again and make sure it does not return an error. It should look like:

 You should now be ready to go back and add your environments to Oblisync.

Attachments

1558721811566000044327_sktwi1f5rjvs16w6t.jpeg get_app
1558721809683000044327_sktwi1f5rjvs16w6s.jpeg get_app
1558721807232000044327_sktwi1f5rjvs16w6r.jpeg get_app
1558721805289000044327_sktwi1f5rjvs16w6q.jpeg get_app
1558721803413000044327_sktwi1f5rjvs16w6p.jpeg get_app