Invalid URI: The format of the URI could not be determined

I'm using the sample on custom authentication from msdn but whenever I try to login I get this message.What URI are they complaining about? Has it anything to do with the custom cookie handling? I cant for the world understand whats wrong.

I had to replace the url to the service in the proxy.

But now I have problems with the cookie. Authorization ticket not received by LogonUser

|||

Am I the only one with this problem?

Could the problem be that I'm using two instances of reporting services? I thought that it was a good idea to create two instances of reporting services to be able to preserve our project portal (team foundation, sharepoint) with windows authentication and use the other one for development with forms authenitcation.

Anyone? Any input would be useful.

|||

Maybe this link will be of some help to you:

http://msdn2.microsoft.com/en-us/library/ms155878.aspx

Shyam

|||Thanks Shyam for your reply but sadly it didnt make any difference.

Invalid Target name - how can it be determined?

Hi, I am sending a message to an invalid target name. The message eventually gets back to the initiator as an error type message. How can I determine the exact cause of the error - and determine that the target service name is invalid? I am using the ServiceBrokerInterface and the Message does not tell much - it seems. Also, in the sys.conversation_endpoints table, the record associated to the message only says 'Error', but no other indicator.

I found it - it is embedded as a stream in the Body property.|||

Right, the cast the response Error message_body to XML and the text will contain the problem service name.

HTH,
~ Remus