Connection not available error

[Guest]

I've created a remote database and am trying to upload a RoboHelp project. From RoboHelp 7 I do the following:

File >> Version Control >> Add to Version Control >> RoboSource Control 3.1. From the Configure Source Control wizard window, Connection >> Create new connection.

I enter all of the data in the fields and select Create and Connect. I get the following error message:

Connection 'new connection' is not currently available, please ensure that the RSO3Service is running and that the machine is addressable on the network. (A network error has occurred. The full error text was 'An existing connection was forcibly closed by the remote host'.)

The service is running. What else could be wrong?

Thanks in advance.

Bill

[Gravenstein]

On the machine from which you are trying to do the upload, open RoboSource Control Explorer, and open the database from there. Once you've done that, close RSC, and try again from RH7.

Does that help?

G

[Guest]

No, I can't even open the database from the explorer. I get an Invalid User or password error. My connection string looks like this:

server=servername;database=database;User ID=username;password=passwordname;persist security info=True;

I use the same user name and password that is in my connection string.

Bill

[Gravenstein]

I did a comparison, and your connection string is different than mine. Mine does not show any password/userid entries, but perhaps that's the difference between using SQL and SQL Express. (I'm using SQL.) I am, of course, assuming that you have actual values for "servername," "database," etc.

Given that you can't get in from RSC Explorer, it would seem that either you are not using the same userid/password as the one you set up for the administrator when you created the DB, or else there's something wrong with the DB itself.

Try creating a test DB. Be careful to specify the same administrator name and password as the login you use to get on the RSC server. After you've created the test DB, open it up from RSC Explorer. If you can do this successfully, then everything ought to be working OK. From that point, I'd start over and create a new DB, and upload to that one. (In fact, I've actually gone through exactly that total exercise before. )

G

[Guest]

Since RoboSource wouldn't let us create a DB on the DB server (SQL Server), the DB administrator took the following RoboSource files:

CreateDB0.sql
CreateDB2.sql
CreateDB3.sql
CreateDB.sql

And ran the scripts from his machine and created a DB on the SQL server with the user name and password that is in the connection string. Then we went to create a DB through RoboSource giving it the name the DB supplied when he created the DB. We got a message saying the DB already existed so we selected the "Register Existing" button and it registered the DB. Now that the DB was registered, we cannot log back onto the DB.

Bill

[Gravenstein]

Does the administrator username/id have SQL server permissions to create databases? If not, that may be your problem.

Beyond that, I'd recommend contacting Support. Sorry.

G