Skip to main content
Inspiring
August 7, 2008
Answered

Connection problem to new RH database

  • August 7, 2008
  • 2 replies
  • 775 views
Here's what I do:
- Log in though Terminal Server on the database server. I log in as local administrator on this server.
- Open RoboSource Server Configurator
- Click 'Create...'
- Click 'Continue'
- Give Name, Instance, Database name
- Leave Connection string as is: server=(local)\profithelp;integrated security=SSPI;database=PH2005;persist security info=False;
- Click 'Create...'
- On the next screen I browse for some folder
- Admin user = User that I logged on with (local admin)
- Password: won't tell you...
- OK
- RH says, please wait and the dialog closes.
- Under 'Registered databases' I see the new database.
- I open RoboSource Control 3.1
- Click 'File / Open Database...
- Select 'PH2005 (local)' from the list of Existing connections (I see the value 127.0.0.1 in the field 'Server')
- Click 'Select'
- RoboSource Error:
Error - database 'PH2005' has not been configured on the server machine.

What do I do wrong?
What do I have to do to create this database?
This topic is closed to new replies. Start a new post to keep the conversation going.
Correct answer Casper_Lange
Well here's the solution.
Today I actually had live contact with 2Tier Robohelp Support, Canada. And through trial and error we bounced upon a bug-like issue in RoboSourceControl.
You cannot connect to a created Robohelp database if the database name contains numerical characters. It may only consist of letters!

2 replies

Casper_LangeAuthorCorrect answer
Inspiring
September 23, 2008
Well here's the solution.
Today I actually had live contact with 2Tier Robohelp Support, Canada. And through trial and error we bounced upon a bug-like issue in RoboSourceControl.
You cannot connect to a created Robohelp database if the database name contains numerical characters. It may only consist of letters!
Gravenstein
Inspiring
September 23, 2008
Thanks very much for posting that solution, Casper. That's an important detail!

FWIW, the old version of RSC (X5) had a problem with database names that had fewer than 4 characters. I haven't tested that with RSC 3, so I don't know if that's still the case. Apparently, names DO matter.

G