MMarcial - Wednesday, October 5, 2011 1:24 PM:
Connecting to SQL Express on a local maching uses:
<DB-Connection id="InnovatorSolutions" database="InnovatorSolutions" server="MACHINESQLEXPRESS" uid="innovator" pwd="innovator" dbType="SQL Server" />
What does a DB connection string look like when using SQL Server 2008 that is on a different box than the IIS Server running Innovator?
eric_h - Wednesday, October 5, 2011 2:18 PM:
Marcial,
On a test server I use sometimes that has the DB on the same server as IIS/Aras, instead of "MACHINESQLEXPRESS", ours is set as "(local)". I assume what you have is UNC notation for something like: 'this machine, the SQLEXPRESS service' or something like that. But probably all works the same.
But you want to connect to a remote database instance from the IIS instance. Our development and production servers work this way, but I do not have server access to confirm by looking at the config file. That said, I am pretty sure (not 100% positive) that we just put the name of the database server in quotes for the server value. So we have something like:
... server="dbservername" ...
Since the IIS machine is in the same domain as the SQL Server machine, there is no need to fully qualify the domain name. I suppose you could also just use the IP address of the machine here.
Anyway, hope this helps. If you cannot get it to work, post the details of where in the network both machines exist (same or different domains) and I can get access to our config file to confirm.
Eric
MMarcial - Wednesday, October 5, 2011 7:07 PM:
Indeed the Innovator installer put ... server="dbservername" ... in the DB-Connection string. However, the dropdown box on the Innovator loging screen is empty.
I then came across postings showing DB-Connection strings like ...server="MACHINESQLEXPRESS"... and ...server="(local)SQLEXPRESS"... and ...server="(local)"....
Therefore, I believe the server attribute is incorrect since the DB dropdown is empty.
NOTE: The IIS server and SQL server are on different machines with different IP addys and are on the same IP network in the same WIndows domain.
eric_h - Monday, October 10, 2011 2:43 PM:
MMarcial,
I just took a look at our production server config file which has Aras and the database on separate servers. For the server string we have: ... server="SERVERNAME"
This works for us. Have you verified the 'uid' and 'pwd' values to make sure these could access the database? It might be worth verifying, if only to count this out as part of the problem.
Eric
MMarcial - Monday, October 10, 2011 4:23 PM:
I did rule out an authentication issue by logging into SQL server via SQL Server Management Studio with "User name: innovator" and "Password: xyz" with SQL Server Authentication.
I also verified the SQL Server Instance name was the same name as the computer name such that [server="SERVERNAME"] should work. If this was not the case the I would need [server="MACHINENAMESQLSERVERNAME"]. Thanks for verifying your config file.
