GotSpeech.NET

I just got a new development machine at work.  I think I've set everything up properly, but I can't debug workflows.

I get this error message in Visual Studio 2005 when I try:

Unable to attach to the process. Debugging cannot continue. Unable to start debugging on the web server. The web server could not find the requested resource.

I'm running Vista Business. My last machine was also running Vista and I don't remember running into anything like this setting up that machine.

Has anyone else seen this?  Any ideas?

Can you post your IIS default web site properties list.

Thanks,

Suresh.
 

 

---

Suresh S
Tech Lead

What properties are you interested in specifically?  I don't know of an easy way to list out all properties at once.

Someone else reporting the same problem after installing VS 2008: http://gotspeech.net/forums/thread/4268.aspx.

---

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Sounds like that could be it except that I've uninstalled VS2008 and the .NET 3.5 Framework. 

I guess there may be some things still there that are causing this. 

Anyone know how I can fix this without doing something drastic (and time consuming) like reinstalling Windows?

I know someone who had this problem and they fixed it by doing something in the IIS MMC. I'll check with him and see what he did?

---

Marshall Harrison
Microsoft MVP, Office Communications Server


www.GoldSys.com
W: 303.447.2774
H: 904.342-6205

the gotspeech guy

A fellow developer encountered this problem today when he accidentally types some invalid xml into the web.config. He removed the extra characters and the problem went away. So check your web.config to make sure it is valid.

outside of the xml, ex:

     <authentication mode="Forms" />

     <identity impersonate="true" />ca

  </system.web>

 

Notice the “ca” on the second line. 

---

Marshall Harrison
Microsoft MVP, Office Communications Server


www.GoldSys.com
W: 303.447.2774
H: 904.342-6205

the gotspeech guy

I wish that was it, but it's not.  My web.config is fine.  And it's happening in all of my speech workflows. 

And I can get to outbound.aspx in the application though a browser, which wouldn't work if the web.config was invalid.

This is a known issue that has been raised through MS Product Support Services and is currently being investigated.  We have a repro and dev is investigating a cause/fix/workaround.

This was just opened to us last week - so I will post more when I have details.

Thanks

 

---

Greg Winters [MS]
Unified Communications Group

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Thanks Greg,

Keep us informed.

---

Marshall Harrison
Microsoft MVP, Office Communications Server


www.GoldSys.com
W: 303.447.2774
H: 904.342-6205

the gotspeech guy

Hi Greg,

 Can you provide us with an update to this issue?  I've had this happen twice now on my Vista box.  The first time I rebuilt the whole thing to solve the problem and I'm hoping there is a fix so I don't have to do this again.  Last time the cause was .NET 3.0 SP1 and this time I'm not sure which update caused it but I can't seem to find a system restore point that will resolve this issue.

 Please help!

 

Thanks,

Josh

 

Josh,

Have you tried installing the hotfix yet?

---

Marshall Harrison
Microsoft MVP, Office Communications Server


www.GoldSys.com
W: 303.447.2774
H: 904.342-6205

the gotspeech guy

Are you talking about the old hotfix that just gets rid of the red X's, or is there something new I don't know about?

I was referring to the hot-fix for the red x problem.

---

Marshall Harrison
Microsoft MVP, Office Communications Server


www.GoldSys.com
W: 303.447.2774
H: 904.342-6205

the gotspeech guy

I did try the red x hotfix and it does resolve the red x problem but not the debugging problem.  I was hopeful that the problem was related and the red x hotfix would solve it. 

What's interesting is the OCS Speech Server release notes talk specifically about this error (one of the few on the web) but the suggested fix doesn't resolve the problem for me.