What error are you getting when trying to connect?

Have you verified you can reach the server with a SQL Client?  Just in case it is not on the standard SQL Server port?

Hi, Have you added in the Workflow Server $ account in to the database logins?

this will look like ServerName0203$

I created a local account for the database and that account has sysadmin rights.  I am also an admin on the server and in SQL but I can't get it to connect using my domain account or a service account that was created for workflow.  I know I had issues with SQLExpress using the domain accounts which is why I created a local account for this as well.  BUT that being said I do not have any accounts for the actual workflow server as you have listed.  Our server is MEDALT01 so I am guessing that in SQL2008 I need to add MEDALT01$ as a user?  Thanks for your help.

Hi,

Have you already tried to run the defaultAppPool with your service account instead of the system account?

That way you won't have to add another account into SQLServer.

You can get more information there :

http://www.symantec.com/connect/articles/enabling-pass-through-ad-authentication-workflow-71

This articles is very usefull to install Workflow Server.

Regards,

Cédric DUBIE

The Workflow install is fine.  I have the service account and everything set up.  I am just trying to connect to a different SQL server for the purposes of a Workflow that I am creating.  After hours of running in to the same brick wall, I believe it has more to do with the SQL server set up after talking to the person that installed it.  We are working to resolve this and I'll post anything that is related to the issue.  But by all means, I'm still taking suggestions.

First of all, you need to have remote access enabled on SQL Server (on Express it is disabled by default) :

http://www.linglom.com/2009/03/28/enable-remote-connection-on-sql-server-2008-express/

This is the link I used to enable it.

Now when you want to connect to your SQL Server to query, you have different authentication type (SQL Server authentication and Windows authentication), the second one is a bit tricky to enable as it is using either the logged-on user whom has called the workflow or the defaultAppPool account or the server itself depending on the way your workflow is configured.

For SQL Server authentication, you shouldn't have any problem if you created a SQL Server account which is dbo or have at least read rights on the database you need to query. (being sysadmin just allow you to query the system databases if I remember well; as I am not an expert on SQL Server I won't say I am sure about it)

When you create your SQL query integration Library, don't forget to choose the SQL Authentication to connect to the database using the appropriate SQL Connection String (e.g.:"Data Source=ServerName\InstanceName;Initial Catalog=DBName;User Id=myUsername;Password=myPassword;"), you can get all the different connection string here :

http://www.connectionstrings.com/sql-server-2008

Other links that might help you are :

http://workflowswat.com/learn-workflow.html (the screencast holy bible)

http://www.screencast.com/t/2RwdWNCvBeQ (video presenting how to create SQL Table generator)

Hope this will help you more than my previous post.

Have a nice week-end and good luck.

Regards,

Cédric DUBIE