Webservice privilegies during debug

[Sakalicek]

Hi all,

can you please help me?
I have Web Service that should do some things on Postgre database.
I am using Npgsql.dll to provide functions to make connection to the database. But I am not able to make this connection.
I tried to step into the Npgsql source and found out that there is a problem when Socket socket is created.
I thought about it and got an idea that it could be in ASP privilegies.

I suppose that aspnet_wp.exe process has some wrong privilegies and thereby it cannot use win api function like to create socket.

Could someone tell me if am I wrong or what?
Or could you just help me with this problem?

Thx a lot, Zdenek.

[kenobewan]

Please don't repost questions - this is already under the IIS forum. You should ask for it to be moved if you want it answered in another forum. Thanks.

[Sakalicek]

Ehm sorry, but it also belongs to this forum, doesnt it?
I dot really know what to do with this so I find every help.
Z.

[Frinavale]

Hi all,

can you please help me?
I have Web Service that should do some things on Postgre database.
I am using Npgsql.dll to provide functions to make connection to the database. But I am not able to make this connection.
I tried to step into the Npgsql source and found out that there is a problem when Socket socket is created.
I thought about it and got an idea that it could be in ASP privilegies.

I suppose that aspnet_wp.exe process has some wrong privilegies and thereby it cannot use win api function like to create socket.

Could someone tell me if am I wrong or what?
Or could you just help me with this problem?

Thx a lot, Zdenek.

You could be right about your permissions setting...but I think you'd be getting permissions error if your application wasn't permitted to use this resource... not a Socket error. This leads me to believe that there's probably another reason for your problem (although I could be wrong about this)

Are you working on a proxy? Sometimes they can cause socket errors like this.

Have you thought about using something other than Npgsql?
Maybe try using .NET's "System.Data.SqlClient" instead?

-Frinny