tags:

views:

107

answers:

1

I'm using the sqlxmlbulkloadlib to perform an xml bulk load. When integrated security=SSPI, the process completes fine inside a workflow hosted on my local machine in a wcf service. However, when that workflow is hosted on our server and kicked off from a service reference on an aspx page, the bulkloader produces an error connecting to the data source. I have tried using sql server authentication instead, but that fails even on my local machine with the same error connecting to data source.

My connection string looks like: "provider=SQLOLEDB;data source=Myserver;database=Mydb;User ID=Myuser;Password=Mypassword"

A: 

Ok, so after creating the sql account for the bulkloader, the policy required that I change the password. Didn't catch that till I tried logging in with the account in management studio.

I am curious, though, what I would have to do differently for integrated security to work from the production server.

Brian
(In case it isn't clear, having logged in and changed the password in sql management studio, the bulk loader is able to successfully connect.)
Brian