I have developed an application that handles data from a SQL server runnig inside my main domain.
When i connect with the SQL server from the inside i have no problems at all.
However we opened up the application (smart client application) for some beta testers and i bumped into some problems. i changed the connectionstring to use the IP for the server. I also tried a registered dns name, but i got the following
The aspnetdb i use for authentication is refusing to run the stored procedures and i get the famous disconnected due to the remote server does not accept remote calls, or something like that.
If i disable the Authentication in the application and just run the application with the same connectionstring IP or DNS, parts of the application works. Some of the stored procedures get executed , and the others does not get executed.
I have looked at the owner of the items but they all have the same owner and exec rights. I have checked my C# code and they are all using the patterns to execute the calls the same way.
Does anyone have any idea whats going on here ?
I also confirmed that the correct SQL ports has been opened in the PIX.
I ran home and tried to connect the sql server managment studio from home and i got access , the application still behaves like before
Hi
The SQL server is set to mixed mode security and i'm using a SQL login i created with dbo schema.
|||
is the server configured to accept local and remote connection
in the surface configuration
|||start>programs> sqlserver2005>
configuration tools>surface area configuration>
configuration for service and connection>datbase engine
>remote connection> check local and remote connection
Thanks for your answer
I found the problem last night. In the solution someone had added a SQL report that had a hardcoded connectionstring. The try catch found the connection issue and then skipped parts of the load of the application.
Once i removed the conn string everything is working fine...
No comments:
Post a Comment