ScriptControl Exception

[ggp2005]

Hi All

I get an exception when I try to edit a Template in a Project.

-------------------------------------------------------------------------------
Exception Type:
COMException

Source:
ScriptControl

Method:
Void SaveInput()

Line: Column:
0 0

Message:
The operation could not be completed because the script engine has not been initialized to a valid language.

Stack Trace:
at MyGeneration.FormAddEditSavedObject.SaveInput()
-------------------------------------------------------------------------------

This exception suddenly appeared, after months of perfect operation.

Really I have no idea about this issue.

I reinstalled Microsoft Script Control, My Generation and nothing changed.

Any help will be much appreciated.

Best Regards
Gianfranco

[mike.griffin]

Is it when you try to edit or execute?

[ggp2005]

When I try to Edit.

[mike.griffin]

From your error message:

The operation could not be completed because the script engine has not been initialized to a valid language.

It appears that there is no language set in your template? You might compare it using notepad to another template? There is a header section at the top.

Code: Select all

##|TYPE Template
##|UNIQUEID bb997abc-46b9-418d-a4fd-192586a5bd87
##|TITLE dOOdads - Invoke a Stored Procedure
##|NAMESPACE dOOdads.C#
##|OUTPUT_LANGUAGE None
##|GUI_ENGINE Microsoft Script
##|GUI_LANGUAGE VBScript
##|GUI_BEGIN

That could be it unless it's happening on all templates?

[ggp2005]

This is what appears at the beginning of the Template

##|TYPE Template
##|UNIQUEID 262a50ac-c726-4d0d-b0d3-de3f98dfb4b7
##|TITLE dOOdads Business Entity Dynamic SQL - MSSQL - PKOverload
##|NAMESPACE dOOdads.C#
##|OUTPUT_LANGUAGE C#
##|GUI_ENGINE Microsoft Script
##|GUI_LANGUAGE VBScript
##|GUI_BEGIN

[justin.greenwood]

You could try it on another computer just to see if it's your system. If it fails on multiple computers, send me the template and, if I can reproduce it, I will fix it and put a new build up.

[ggp2005]

I edited and executed this Template (Inside the Project) hundreds of times until version 1.1.2

This is the first time I try to edit the Record Template Input in version 1.1.3

After the Exception pressing the View Data Button the Grid has no data.

Any way I'll try the same process in other machine to see what happen.

[justin.greenwood]

If you're still having problems, go ahead and send me the template and I'll try to get this fixed for you.
justin.greenwood@mygenerationsoftware.com

[mike.griffin]

Hmmm, I found this:
http://support.microsoft.com/default.as ... -US;184977

This error had been reported by somebody else, did you ever figure out what it was?

[ggp2005]

I fixed this situation reinstalling Windows Script 5.6.0.8825.

I don't know how it got corrupted but happen.

Should be also healthy reinstall the Microsoft Script Control.

It's all what I know about it.

[Stixoffire]

Here is one answer and it worked for me marvellouly

http://support.microsoft.com/kb/949140

You are running a 32-bit version of the Windows operating system
Click Start, click Run, type cmd, and then click OK.
Type regsvr32 %systemroot%\system32\vbscript.dll, and then press ENTER.
Type regsvr32 %systemroot%\system32\jscript.dll, and then press ENTER.
Type regsvr32 %systemroot%\system32\dispex.dll, and then press ENTER.
Type regsvr32 %systemroot%\system32\scrobj.dll, and then press ENTER.
Type regsvr32 %systemroot%\system32\scrrun.dll, and then press ENTER.
Type regsvr32 %systemroot%\system32\wshext.dll, and then press ENTER.
Type regsvr32 %systemroot%\system32\wshom.ocx, and then press ENTER.

You are running a 64-bit version of the Windows operating system, and you receive the error message that is mentioned in the "Symptoms" section while you are using the 64-bit scripting components
Click Start, click Run, type cmd, and then click OK.
Type %systemroot%\system32\regsvr32 %systemroot%\system32\vbscript.dll, and then press ENTER.
Type %systemroot%\system32\regsvr32 %systemroot%\system32\jscript.dll, and then press ENTER.
Type %systemroot%\system32\regsvr32 %systemroot%\system32\dispex.dll, and then press ENTER.
Type %systemroot%\system32\regsvr32 %systemroot%\system32\scrobj.dll, and then press ENTER.
Type %systemroot%\system32\regsvr32 %systemroot%\system32\scrrun.dll, and then press ENTER.
Type %systemroot%\system32\regsvr32 %systemroot%\system32\wshext.dll, and then press ENTER.
Type %systemroot%\system32\regsvr32 %systemroot%\system32\wshom.ocx, and then press ENTER.

You are running a 64-bit version of the Windows operating system, and you receive the error message that is mentioned in the "Symptoms" section while you are using the 32-bit scripting components
Click Start, click Run, type cmd, and then click OK.
Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\vbscript.dll, and then press ENTER.
Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\jscript.dll, and then press ENTER.
Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\dispex.dll, and then press ENTER.
Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\scrobj.dll, and then press ENTER.
Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\scrrun.dll, and then press ENTER.
Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\wshext.dll, and then press ENTER.
Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\wshom.ocx, and then press ENTER.