Highlighted

RoboHelp Server 10 Users: Have you configured an external db using JDBC?

Explorer ,
Aug 31, 2016

Copy link to clipboard

Copied

I'm trying to configure a new installation of Server 10 with SQL Server 2014 Standard Edition but I can't get past the RoboHelp Server Configuration Manager.

  • I think I've created a correct database URL
  • I think I've specified the correct JDBC driver class
  • I'm using a database username and password that I created in SSMS, so I know it's correct
  • I'm rather certain I've specified the correct path to the sqljdbc_4.1.jar file

And when I click "Test Connection," all I'm getting is "Connection failed."

Calling the RoboHelp Server 10 docs on this subject "sparse" would be generous. Are there additional undocumented steps that I need to do first?

Has anyone out there even gotten this to work?

I finally succeeded in this. The problem was two things:

  • The user credentials did not have the correct permissions on the SQL Server instance
  • The database URL was needlessly complex. All that was required was jdbc:sqlserver://localhost (specifying a databaseNAME property actually prevented it from working, for some reason)

Correcting these two issues solved the problem and I was able to successfully connect to the server.

Topics

RoboServer

Views

716

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

RoboHelp Server 10 Users: Have you configured an external db using JDBC?

Explorer ,
Aug 31, 2016

Copy link to clipboard

Copied

I'm trying to configure a new installation of Server 10 with SQL Server 2014 Standard Edition but I can't get past the RoboHelp Server Configuration Manager.

  • I think I've created a correct database URL
  • I think I've specified the correct JDBC driver class
  • I'm using a database username and password that I created in SSMS, so I know it's correct
  • I'm rather certain I've specified the correct path to the sqljdbc_4.1.jar file

And when I click "Test Connection," all I'm getting is "Connection failed."

Calling the RoboHelp Server 10 docs on this subject "sparse" would be generous. Are there additional undocumented steps that I need to do first?

Has anyone out there even gotten this to work?

I finally succeeded in this. The problem was two things:

  • The user credentials did not have the correct permissions on the SQL Server instance
  • The database URL was needlessly complex. All that was required was jdbc:sqlserver://localhost (specifying a databaseNAME property actually prevented it from working, for some reason)

Correcting these two issues solved the problem and I was able to successfully connect to the server.

Topics

RoboServer

Views

717

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Employee ,
Sep 01, 2016

Copy link to clipboard

Copied

Hi Rocky,

Since you can connect to DB using SSMS i am sure you are using correct login credential. Just make sure you are providing other details for connection set-up in specified format. Below is example for the same:

   Field Example

Database URL ----- >      jdbc:sqlserver://NEON-I:1440;databaseName=RHSSQL12

Database User Name ------>      <your username>

Database Password           ------>      <your pwd>

JDBC Driver Class           ------>      com.microsoft.sqlserver.jdbc.SQLServerDriver

JDBC Driver Path           ------>      C:\Users\labuser\Desktop\sql41.jar

Thanks,

Mohd Sameer

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Sep 01, 2016

Copy link to clipboard

Copied

I finally succeeded in this. The problem was two things:

  • The user credentials did not have the correct permissions on the SQL Server instance
  • The database URL was needlessly complex. All that was required was jdbc:sqlserver://localhost (specifying a databaseNAME property actually prevented it from working, for some reason)

Correcting these two issues solved the problem and I was able to successfully connect to the server.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...