Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 259389 - Last Review: July 27, 2001 - Revision: 1.0
PRB: Remote Scripting Error If You Change Server Language to JScript
This article was previously published under Q259389
If you change the server-side script language from Microsoft VBScript to Microsoft JScript in a server Active Server Pages (ASP) page that is used for remote scripting, the following error message appears:
Remote Scripting Error
REMOTE SCRIPTING ERROR: Page invoked does not support remote scripting.
Within the server-side script page, a remote scripting function called
RSDispatch() is called. The error occurs because the public_description object, which is utilized by the
RSDispatch() function, has not been created.
To resolve the error, ensure that the public_description object is created before you call
RSDispatch(). You can accomplish this by simply making the call to
RSDispatch() as the last command on the page.
For example, change
<%@ LANGUAGE=JScript%>
<!--#include file="_ScriptLibrary/rs.asp"-->
<% RSDispatch() %>
<SCRIPT Language=JavaScript RUNAT=SERVER>
function Description()
{
this.TestFunction = TestFunction;
}
public_description = new Description();
function TestFunction()
{
return "Hello world!";
}
</SCRIPT>
to:
<%@ LANGUAGE=JScript%>
<!--#include file="_ScriptLibrary/rs.asp"-->
<SCRIPT Language=JavaScript RUNAT=SERVER>
function Description()
{
this.TestFunction = TestFunction;
}
public_description = new Description();
function TestFunction()
{
return "Hello world!";
}
RSDispatch();
</SCRIPT>
This behavior is by design.
APPLIES TO
- Microsoft Active Server Pages 4.0
| kbprb kbremoteprog kbscript KB259389 |
Retired KB Content DisclaimerThis article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate