Deployment issue in Beta 3

[Ben Clackson]

I have deployed a speech app to a Web Server and find that it works OK when
the client is my development machine, but gives a run-time error "Object
doesn't support this property or Method (Code 0)" message on one of the
pages when the client has only had the Microsoft Internet Explorer Speech
Add-In Stand-alone installation (This is of course on top of IE6 SP1 and the
.NET Framework v1.1). Other pages in the app work OK.

After viewing the source code in the client browser, I am wondering if this
is anything to do with the fact that although I have built the app with the
Release configuration, the code served up to the client still includes
SpeechControlDialogD.js rather than SpeechControlDialog.js. This seems
anomalous: The D signifies Debug I think, so why is that file being selected
at run-time by a Release build?

Is there anything else I could try? If all else fails I could go back to
installing Visual Studio.NET 2003 and the whole of SASDK Beta 3 on the
client, but according to the documentation that shouldn't be necessary. Any
ideas?

Ben Clackson

[Ben Clackson]

[Tom Faber [MS]]

Hi Ben - thanks for letting us know about this. A few questions for you:

1) What user agent string is the browser sending to the web server? The
easiest way to see this is by looking in the IIS logs, if you have access to
the web server.
2) What's unique about that page? Are there certain types of speech
controls you're only using on that page?

Thanks
-Tom [MS]

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

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

"Ben Clackson" <ben.cl...@ntlworld.com> wrote in message
news:rQigb.825$b93...@newsfep1-gui.server.ntli.net...

[Ben Clackson]

Hi Tom,

Thanks for your encouraging reply on this. You asked about:

1. User Agent Strings:

User Agent string sent by XP development machine (the client that works
fully):

2003-10-08 15:26:23 172.20.0.161 - 172.20.0.90 80 GET /PackReader/ - 302
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SALT+1.0.4223.1+0111+Deve
loper;+.NET+CLR+1.0.3705;+.NET+CLR+1.1.4322)

User Agent string sent by Windows 2000 machine with only the IE Speech
Add-in installed (the client that fails on the 3rd page):

2003-10-07 01:46:06 172.20.0.153 - 172.20.0.90 80 GET /packreader/ - 302
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+SALT+1.0.4223.4223+0111;+
.NET+CLR+1.1.4322)

2. You asked if there were some types of controls only used on that page.
The answer is: not that I can see. The page uses a QA control, a Command and
a SemanticMap but so does another page that works OK (on the client with the
IE Speech Addin stand-alone installation; as I said in my original mail the
whole app works OK when the client is my XP development machine).

The load error which occurs on the IE Speech stand-alone installation client
directs me to line 734 or 743 (can't remember which), which I believe to be
somewhere in SpeechControlDialogD.js. I have tried doing View Source on the
client, saving the page as htm, and replacing the

<script language="javascript" src="....SpeechControlDialogD.js">
</script>

by the contents of the file (surrounded of course by script tags). But
running that htm file, I haven't managed to reproduce the same error (so I
can't trace the line number that fails). This htm file gives an error even
on my development machine when it reaches the line in the Javascript:

SpeechCommon.init("VoiceOnly");

so no doubt there is some essential difference about running the htm page in
isolation and running it as part of a website.

Does the D in SpeechControlDialogD.js denote Debug or Developer or neither?

I am not willing to post the URL of the site to the newsgroup for security
reasons but could give it to you if you can give me an email address to send
it to.

Regards,
Ben Clackson

"Tom Faber [MS]" <to...@online.microsoft.com> wrote in message
news:OYU7PARj...@TK2MSFTNGP12.phx.gbl...

[speech beta]

I am experiencing this same error, except with the tap and talk demo that
comes with the sdk. I have installed the tap and talk on one computer(fast
machine) with vs.net and office 2003 beta and then on another with server
2003 and speech server 2003(server). The fast machine plays the voice and
works with the speech javascript just fine, whether it is using the
tapandtalk on localhost or on the server machine. But the server machine
gets javascript errors on both tapandtalks. I made sure the TTS and speech
recognition was setup in control panel like how the SDK said. I tried
reinstalling the IE plug-in from the SDK or server cd but it says another
version is already installed. Any idea?

"Ben Clackson" <ben.cl...@ntlworld.com> wrote in message
news:rQigb.825$b93...@newsfep1-gui.server.ntli.net...

[Ben Clackson]

(I am puzzled that the following reply which I posted to the Group on 8
October and was displayed for a few days is no longer displayed. I still
have no reply from Mr Faber and am wondering if he is a real Microsoft
engineer or a spammer trying to sound like one.)

Hi Tom,

1. User Agent Strings:

SpeechCommon.init("VoiceOnly");

Regards,
Ben Clackson

[Tom Faber [MS]]

Oh no! I left this thread unattended, and I've been appropriately
chastised. My apologies to Ben and anyone else who's been following this
issue. Thanks to John Lawrence [MS] who brought this to my attention.
I've followed up with Ben in email, and I'll post back to the group once we
have more information.

Sorry again
- Tom Faber [still employed by MS as far as I know]

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

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

"Ben Clackson" <ben.cl...@ntlworld.com> wrote in message

news:2zrjb.31$id2...@newsfep3-gui.server.ntli.net...

[Tom Faber [MS]]

For anyone still following this thread, we have (mostly) figured out the
cause of this problem. Ben had an <OBJECT> tag on his page that for some
reason caused the prompt object to fail. Once we moved the <OBJECT> tag
to the top of the html page, the app functioned as expected. Exactly why
this should be the case, we are still investigating.

thanks
-Tom Faber [MS]

This posting is provided "AS IS" with no warranties, and confers no rights.

"Tom Faber [MS]" <to...@online.microsoft.com> wrote in message

news:uRxHfkOl...@TK2MSFTNGP11.phx.gbl...