Showing posts with label soap. Show all posts
Showing posts with label soap. Show all posts

Monday, March 19, 2012

Make Connection to SOAP endpoint without integrated login?

I have a endpoint on our SQL Server and I've written a test .Net app to access it and it all works great. It uses the Integrated Login for Authentication.

My project in the end will have connections made to the endpoint via some custom code on a Non Windows/Linux platform. My concern is that there is no Authentication method that I can use from this client. Integrated is out since it not something you log into. SSL is out since there is no Cert store. Isn't there a way to use the SQL Authentication in a Mixed mode SQL Authentication install?

What are my other options? I need to be able to get data from our SQL server from this custom platform. We looked into using TDS protocol, but would rather not have to license it and develop a client on our platform. We wanted to just generate the HTTP Packets to send and receive the data.

Thank you,

Scott<-

SQL SOAP always requires integrated login first before you can use SQL login. You should try digest it should work from a non-MS platform.

Friday, March 9, 2012

Major Problem!...Multiple user connection problem in reporting service 2000 with SOAP

Hi Everyone,

I am having a big problem here.

I am using Reporting Service 2000 and Visual Studio 2005. I have developed a custom web control which communicates with reporting web service and displays report. I pass username, password and domain information as network credential for communicating with report server (report server is remote). This is a web application in which users can see reports on the web page which uses my custom web control.

Everything works fine when there is single user. But when another user logs onto website and tries to access same or different report it seems like connection of the first user gets lost. And everything crashes for first user and for second user it works fine.

In fact if second user is accessing the same report then first user can see second user's report information which is no at all acceptable. I am sure that there should be some way so that multiple users can communicate with reporting server programmatically at the same time. Microsoft wouldn't make reporting web service so that only one user can access report at a time, would they?

Can anyone help me with this problem? Any help will be greatly appreciated.

Sounds like your users are being identified as the same person which would suggest annonymous access is being used or your web control is passing the same credentials for both users. I'm not sure how you've coded it or whether you are doing any caching or storing session state somewhere.

You have to narrow down what is at fault here. I would suggest the following:

Set your report server and report manager virtual directories to integrated or basic authentication and have 2 separate users access report manager at the same time|||

Thanks Adam for quick reply.

I don't have anonymous access enabled. I am using integrated windows authentication. Earlier i was trying to authenticate all users with one administartor credentials to communicate with Reporting web service. But then i changed my code so that it takes individual user's credentials. But this didn't make any difference.

I read in one reporting service book that Report server overwrites SessionID member after each call to the Render method. Therefore, two subsequent report requests will share same sessions only if they ask for the same report (assuming that the parameter set is same)

For example, let's say you run report A, then report B, and then report A again. When report B is rendered, its session identifier will overwrite the previous session identifier, which means that you will lose report A's session identifier. When report A is run again, even if the parameter set is the same, its execution will create a new report session and IsNewExecution will return true.

So i think this overwriting of SessionID by report server is causing the problem. But i don't know yet how to program so that it maintains proper SessionID for each user and hence doesn't crash for any user.

If anyone has any idea for solving this problem then please let me know. Thanks in advance.

|||Figured out. It was bug in my code. Accidentlly i had declared Parameter property as static in my code and because of that one user's report was using other user's property and which was making program crash. Thanks for reply though.

Major Multiple connection problem RS2000 with SOAP

Hi Everyone,

I am having a big problem here.

I am using Reporting Service 2000 and Visual Studio 2005. I have developed a custom web control which communicates with reporting web service and displays report. I pass username, password and domain information as network credential for communicating with report server (report server is remote). This is a web application in which users can see reports on the web page which uses my custom web control.

Everything works fine when there is single user. But when another user logs onto website and tries to access same or different report it seems like connection of the first user gets lost. And everything crashes for first user and for second user it works fine.

In fact if second user is accessing the same report then first user can see second user's report information which is no at all acceptable. I am sure that should be some way so that multiple users can communicate with reporting server programmatically at the same time. Microsoft wouldn't make reporting web service so that only one user can access report at a time, would they?

Can anyone help me with this problem? ANyhelp will be greatly appreciated.

I don't have anonymous access enabled. I am using integrated windows authentication. Earlier i was trying to authenticate all users with one administartor credentials to communicate with Reporting web service. But then i changed my code so that it takes individual user's credentials. But this didn't make any difference.

I read in one reporting service book that Report server overwrites SessionID member after each call to the Render method. Therefore, two subsequent report requests will share same sessions only if they ask for the same report (assuming that the parameter set is same)

For example, let's say you run report A, then report B, and then report A again. When report B is rendered, its session identifier will overwrite the previous session identifier, which means that you will lose report A's session identifier. When report A is run again, even if the parameter set is the same, its execution will create a new report session and IsNewExecution will return true.

So i think this overwriting of SessionID by report server is causing the problem. But i don't know yet how to program so that it maintains proper SessionID for each user and hence doesn't crash for any user.

If anyone has any idea for solving this problem then please let me know. Thanks in advance.