Skip to main content
A
Anonymous
May 27, 2009
Question

Problem establishing a database connection in RoboHelp 8.0

  • May 27, 2009
  • 2 replies
  • 1893 views

I'm attempting to configure RoboHelp 8.0 to use RoboSource Control 3.1 with RSC Server being on one server and the SQL database being on another server.

An SQL Server 2005 Standard Edition database named cg_help_test was created for me on our corporate SQL server sql-pdpw01.

I installed RSC 3.1 Server on our virtual corporate Windows 2003 Server robo-pavw01.  I then used RoboSource Server Configurator to successfully register the cg_help_test database with the connection string server=sql-pdpw01;database=cg_help_test;User ID=cgadmintst;Password=RoboTest;persist security info=False;  I set the RSO3 Server Service to logon with our tech support team's domain account xxoats.  And I verified that RSO3ServerRemoting.config specifies port 8039.

I installed RH 8.0 on Windows XP workstation pc50410.  I set the RSO3 MiddleTier Service to logon with our tech support team's domain account xxoats.  And I verified that RSO3MiddleTierRemoting.config specifies port 8042.

However, when using RSC 3.1 Explorer on pc50410, I am unable to create a new connection to the cg_help_test database.  Here's what I've entered in the fields on the form:

Connection Name: cg_help_test (also tried test)
Port No.: 8039
Server: robo-pavw01 (also tried the IP address)
Port Type: TCP
Database: cg_help_test

When I click the Create Connection button, I receive a RoboSource Error window that says Invalid object name 'NG3Node' with a link to Show Stack Trace, which doesn't help me at all.

Does anyone know what's not working here?

Brian

This topic has been closed for replies.

2 replies

Gravenstein
Gravenstein
Inspiring
May 28, 2009

Hi Brian -

The procedure you described is different than what we do.  We found a way that works, and have stuck with it, so I don't know if your approach works and just needs a tweak or two, or if it won't work.

For reference, here's what we do:

1. Set up an admin login on both the SQL server and the RSC server. (Same login/password for both. This is important.)

2. From the RSC server, use the configurator to create a db on the SQL server.

    - For the connection string, use;
       server=sqlservername;integrated security=SSPI;database=oh_service;persist security info=False;
      Note that this is only slightly changed from the default string.

    - For the admin name, use the admin login name specified in step 1.

3. Open RSC Explorer. You must still be logged on to the RSC server with the same admin password, or you won't be able to access the new db.

4. Open the new db, and set up your User Library accounts.

5. From RH, open the project and upload it to the DB.

We did not make any changes to the RSO3 MiddleTier Service configuration, allowing Windows authentication to handle access permissions. We use RSC 3.0, but I expect that 3.1 is going to be similar.

The critical thread in this process is logging with a consistent admin account all the way until you have your user library accounts set up. Whenever I've forgotten and used a different account somewhere in the process, I end up being unable to access the db.

Sooo...after that windy setup, I'd say that I'm particularly suspicious of your connection string and your login/permissions configuration.

HTH,

G

A
Anonymous
May 28, 2009

Thank you, G.

I think the issue here is that I asked our DBA to create the database and, however she did it, she did not use the RSC Configurator. I will ask her to delete the database she created, and I will work with her to create a new one using the procedure you described.  And I will make sure to use the same Admin ID and password throughout.

Brian

A
Anonymous
May 29, 2009

G,

Our DBA had not used the scripts, didn't know about them (and neither did I).  Once the database was deleted, creating it correctly using the Configurator was a breeze.

Thanks for your help.

Brian

A
Anonymous
May 27, 2009

The SQL Server 2005 Standard Edition database named cg_help_test that was created for me on our corporate SQL server sql-pdpw01 was created by our DBA, and I don't believe that (per something I saw in Notes on Creating a Database) she ran "the scripts CreateDB2.sql and CreateDB3.sql to create the tables and stored procedures", nor do I believe she "edit(ed) the user account placeholders in CreateDB3.sql".  Could that be the issue?  (I'm really not sure how she created the database.)

Brian

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices