Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
SALT deployment on OCS RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    I have developed a simple "Hello World" SALT application in Visual Studio 2005.  It works fine in the debugger.  When I deploy the application on an OCS, I get a (500) Internal Server Error.  The application won't answer at all.  Do I have something configured wrong?
    Tuesday, October 9, 2007 8:35 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    This was an ASP.NET configuration issue.  Although 2.0.50727 was displayed as the ASP.NET version in IIS, changing this to version 1.1.4322, and back again, made the 500 error go away.

     

    Wednesday, October 24, 2007 4:10 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    A few questions....

     

    1.  Have you looked at the event viewer on the OCS server to see if the 500 error generated an application error.

     

    2. Sometimes you can tell alot about whether the application is even installed properly by simply typing the URL into a web browser to see the response... especially with SALT apps.  So can you put the URL into IE for example and at least get a response from IIS.

     

    3. Are you using a soft phone or some other method to call the application on your OCS box?

     

    4. Where you able to call the OCS box with the default "Welcome to Speech Server 2007" application before attempting to call the SALT application?

     

    kstep

    Thursday, October 11, 2007 12:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This was an ASP.NET configuration problem.  2.0.50727 was displayed as the ASP.NET version in IIS.  However, changing this to 1.1.4322, and back again made the 500 error go away

     

    Wednesday, October 24, 2007 4:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This was an ASP.NET configuration issue.  Although 2.0.50727 was displayed as the ASP.NET version in IIS, changing this to version 1.1.4322, and back again, made the 500 error go away.

     

    Wednesday, October 24, 2007 4:10 PM