WCF in Managed Application
-
*Note I don't know the proper terminology for what I am asking so bear with me... I am hosting a WCF Service within a Managed application. In other words I have an application that is running a ServiceHost. I did not set it up as an Independent service, it is embedded within the app. Now I have run into a variety of issues. The first being:
System.ServiceModel.AddressAccessDeniedException: HTTP could not register URL http://+:48921
I know this is due to UAC on Vista/Win7. I however have found no way to fix it from the developer side of things. Any clue how to resolve the error without the user having to do anything? My second issue:
System.ServiceModel.FaultException: The server was unable to process the request due to an internal
error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from
ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order
to send the exception information back to the client, or turn on tracing as per the Microsoft .NET
Framework 3.0 SDK documentation and inspect theNow for this one, I am clueless. 1) I don't know how to enable it inside a Managed App that doesn't use a config file. 2) from what I read, you have to have a good Idea of exactly what error it would produce. My last issue is that I cannot get the client and server to work correctly in .NET 3.5. Everything I try doesn't seem to work correctly. So, I am being 'forced' to use 4.0. (Not that I mind. Seems to run faster anyway.) There was another that I think i fixed on my own, it dealt with the port already being in use. Since i run the commands in new threads they can sometimes hit at the wrong time... So I have it wait for them to complete before running the next.
-
*Note I don't know the proper terminology for what I am asking so bear with me... I am hosting a WCF Service within a Managed application. In other words I have an application that is running a ServiceHost. I did not set it up as an Independent service, it is embedded within the app. Now I have run into a variety of issues. The first being:
System.ServiceModel.AddressAccessDeniedException: HTTP could not register URL http://+:48921
I know this is due to UAC on Vista/Win7. I however have found no way to fix it from the developer side of things. Any clue how to resolve the error without the user having to do anything? My second issue:
System.ServiceModel.FaultException: The server was unable to process the request due to an internal
error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from
ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order
to send the exception information back to the client, or turn on tracing as per the Microsoft .NET
Framework 3.0 SDK documentation and inspect theNow for this one, I am clueless. 1) I don't know how to enable it inside a Managed App that doesn't use a config file. 2) from what I read, you have to have a good Idea of exactly what error it would produce. My last issue is that I cannot get the client and server to work correctly in .NET 3.5. Everything I try doesn't seem to work correctly. So, I am being 'forced' to use 4.0. (Not that I mind. Seems to run faster anyway.) There was another that I think i fixed on my own, it dealt with the port already being in use. Since i run the commands in new threads they can sometimes hit at the wrong time... So I have it wait for them to complete before running the next.
It's a rather strange port, did you choose it yourself? I'm not too sure what's going on but if you don't specify the port and use the HTTP protocol you will have some conflict with httpsys! (the native http handler) On a server I use that http://httpsysconfig.codeplex.com/ [^] to share URL with httpsys. On a client computer, I guess you can specify a port (other than 80 of course!), or not use HTTP
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
-
*Note I don't know the proper terminology for what I am asking so bear with me... I am hosting a WCF Service within a Managed application. In other words I have an application that is running a ServiceHost. I did not set it up as an Independent service, it is embedded within the app. Now I have run into a variety of issues. The first being:
System.ServiceModel.AddressAccessDeniedException: HTTP could not register URL http://+:48921
I know this is due to UAC on Vista/Win7. I however have found no way to fix it from the developer side of things. Any clue how to resolve the error without the user having to do anything? My second issue:
System.ServiceModel.FaultException: The server was unable to process the request due to an internal
error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from
ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order
to send the exception information back to the client, or turn on tracing as per the Microsoft .NET
Framework 3.0 SDK documentation and inspect theNow for this one, I am clueless. 1) I don't know how to enable it inside a Managed App that doesn't use a config file. 2) from what I read, you have to have a good Idea of exactly what error it would produce. My last issue is that I cannot get the client and server to work correctly in .NET 3.5. Everything I try doesn't seem to work correctly. So, I am being 'forced' to use 4.0. (Not that I mind. Seems to run faster anyway.) There was another that I think i fixed on my own, it dealt with the port already being in use. Since i run the commands in new threads they can sometimes hit at the wrong time... So I have it wait for them to complete before running the next.
About your second issue, you need an config file for the client or server. You can add these configurations programatically I used to get this error, as i had a connection stirng in one config file and the wcf settings in other config file. Combining then worked for me. And also check the debug/release folders and check the config files are of correct names..