|
Home > Archive > IIS Server Security > June 2004 > Microsoft Speech Server IIS6 error 401
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Microsoft Speech Server IIS6 error 401
|
|
|
| We have reached the final stage of our MS Speech Server implementation and even with the help from our reseller and consultants we can't seem to go any further due to an authorization issue in the SES in an 2003 Enterprise Server Domain environment. Ther
e are two files to configure, access.txt and trustedaccess.txt on the SES. (Our TAS/TIM is on one server and the SES/Web/ASP is on a second server; trusts have been established between both servers). The instructions are pretty straight-forward and we've
rechecked the configuration several times. However when we place a phone call to the assigned T1 number we get dead-air. The event logs show the lobby.axms file could not be reached due to an authenication issue. I'm sure its a simple solution but I c
an't figure it out. Has anyone experienced this problem and what do you try to resolve it. I can supply more details. (drop down did not have Speech Server as choice so I'm posting it here).
| |
| David Wang [Msft] 2004-06-30, 6:01 pm |
| You may get better results on microsoft.public.inetserver.iis , as more
people browse that newsgroup. Your question really has nothing to do with
IIS nor security issues -- this looks to be an application configuration
issue.
Please look in the web log files
(%SYSTEMROOT%\System32\LogFiles\W3SVC#\*
.log) for that particular failed
request and post the log line(s) here. In particular, I want to know the
HTTP status code, substatus code, and Win32 error code for all associated
requests.
Also, please give what authentication protocols are enabled on all URLs
involved.
I know nothing about Speech Server. Is it normal Speech Server
configuration to have two different machines involved. I'm not certain what
you mean by establishing trusts between both servers.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Dave" <Dave@discussions.microsoft.com> wrote in message
news:5A23E53E-A2A1-4D4A-8EAE-EBFF544E73AB@microsoft.com...
We have reached the final stage of our MS Speech Server implementation and
even with the help from our reseller and consultants we can't seem to go any
further due to an authorization issue in the SES in an 2003 Enterprise
Server Domain environment. There are two files to configure, access.txt and
trustedaccess.txt on the SES. (Our TAS/TIM is on one server and the
SES/Web/ASP is on a second server; trusts have been established between both
servers). The instructions are pretty straight-forward and we've rechecked
the configuration several times. However when we place a phone call to the
assigned T1 number we get dead-air. The event logs show the lobby.axms file
could not be reached due to an authenication issue. I'm sure its a simple
solution but I can't figure it out. Has anyone experienced this problem and
what do you try to resolve it. I can supply more details. (drop down did
not have Speech Server as choice so I'm posting it here).
| |
|
| I realize it is not the correct group, however this was the only one that seemed related. The Microsoft Speech Server is not on the drop-down and you can't manually type the group in.
I appreciate the response. I will get that info as soon as possible.
thanks,
DAVE
"David Wang [Msft]" wrote:
> You may get better results on microsoft.public.inetserver.iis , as more
> people browse that newsgroup. Your question really has nothing to do with
> IIS nor security issues -- this looks to be an application configuration
> issue.
>
> Please look in the web log files
> (%SYSTEMROOT%\System32\LogFiles\W3SVC#\*
.log) for that particular failed
> request and post the log line(s) here. In particular, I want to know the
> HTTP status code, substatus code, and Win32 error code for all associated
> requests.
>
> Also, please give what authentication protocols are enabled on all URLs
> involved.
>
> I know nothing about Speech Server. Is it normal Speech Server
> configuration to have two different machines involved. I'm not certain what
> you mean by establishing trusts between both servers.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "Dave" <Dave@discussions.microsoft.com> wrote in message
> news:5A23E53E-A2A1-4D4A-8EAE-EBFF544E73AB@microsoft.com...
> We have reached the final stage of our MS Speech Server implementation and
> even with the help from our reseller and consultants we can't seem to go any
> further due to an authorization issue in the SES in an 2003 Enterprise
> Server Domain environment. There are two files to configure, access.txt and
> trustedaccess.txt on the SES. (Our TAS/TIM is on one server and the
> SES/Web/ASP is on a second server; trusts have been established between both
> servers). The instructions are pretty straight-forward and we've rechecked
> the configuration several times. However when we place a phone call to the
> assigned T1 number we get dead-air. The event logs show the lobby.axms file
> could not be reached due to an authenication issue. I'm sure its a simple
> solution but I can't figure it out. Has anyone experienced this problem and
> what do you try to resolve it. I can supply more details. (drop down did
> not have Speech Server as choice so I'm posting it here).
>
>
>
|
|
|
|
|