Quote Originally Posted by OptionBase1 View Post
I think your over-exuberant placeholder modification of the connection string is really, really muddying the waters here.

Earlier you said this:



But then you keep making mention of trying to log in with a service account. So which is it? Are you using your own Windows user account credentials in the connection string?

And it still isn't clear what the "SVC" prefix you are using for the credentials is attempting to represent here. Is it the host name of the server that you are connecting to? Is it your local workstation name? Is it the NetBios name of the Active Directory domain that everything is joined to? Is it the SQL Server instance name?

While it is possible that the root cause is a lack of permissions, I'm not convinced that is the case. If you could provide more specific details answering the questions I pose above, then you might get pointed in the right direction.

Good luck.
SVC IS the first 3 letters of the service login account. Ddddd2 is my local account.

At any rate, I got an answer. It woudn't have been possible to do this locally.


"I did talk to XXXX about this issue. Per XXXX, you won’t be able to connect to the SQL DB directly from SSS using a windows service account. For .Net apps, we are connecting to DB via IIS app pool. Is there anything similar in SSS? If not, we may have to check with DB team for a local DB account."

The weblogic server that connects is running from a linux server.

The person who asked me about this originally, is building a Java app and can't figure out how to connect to the database with the service account provided. I told them I would try from a different environment - VBScript - but of course was unsuccessful. There was also a .net app that connected successfully, but of course it's not going to work from our angle.


Thanks everyone for trying to help. The java developer is pointed in the right direction. Resolved.