none
04-00000020 - A Script element in this OSD file is missing an executable. - 4.6 Client Error

    Question

  • A Script element in this OSD file is missing an executable. Report the following error code to you System Administrator.

    Error code: 4605F3-07901a04-00000020

    -----------------------------------------------------------------------------------------------------------------------------
    Client version 4.6.0.1523
    Windows Server 2003 Enterprise SP2

    So after installing the 4.6 client I started running into this error message on applications that had pre launch scripts.

    Here's the weird part.

    It happens when we launch from the OSD file, but we use App-V in XenApp only. So all of our command lines launch from the osd files.

    If the users were launching the applications from the start menu, they would not see the error.

    It's intermittant, so it will launch the app the first couple of attempts, but once the user receives the error, they continue to receive that error until we clear that application from the cache on that server.

    It's acting like it doesn't see the script as a valid script element.

    Has anyone seen this yet?

    Anyone have any ideas?

    JJ
    Wednesday, April 28, 2010 2:39 PM

Answers

  • Yea I looked at that article, but the script is definetly there.

    And like I said, it launches the first time, but then comes up with that error the next time.

    Clear the cache, and you might get another 10 launches before it fails again.

    Change the version or name in the osd file, and it will work until you make any change to the pre launch script.

    It was wierd and frustrating.

    You are correct though, the 4.6 client does not regiser the FTA from a clean install. However, if you do an upgrade from a 4.5 client, the FTA's stay in place.

    I'm still doing some testing, but it looks like the  4.6.0.20200 client released on 4/15/2010 for TS resolves the script issue

    http://www.microsoft.com/downloads/details.aspx?FamilyID=e633164f-9729-43a8-9149-de651944a7fe&displaylang=en


    JJ
    • Marked as answer by JJ Zettle Thursday, April 29, 2010 6:09 PM
    Thursday, April 29, 2010 6:09 PM

All replies

  • Hello,

    See this article;

    http://kbalertz.com/930637/SoftGrid-Client.aspx

    and didn't the 4.6 client change so that .OSD-files aren't an registered FTA?

    /Znack

    Wednesday, April 28, 2010 9:36 PM
  • Yea I looked at that article, but the script is definetly there.

    And like I said, it launches the first time, but then comes up with that error the next time.

    Clear the cache, and you might get another 10 launches before it fails again.

    Change the version or name in the osd file, and it will work until you make any change to the pre launch script.

    It was wierd and frustrating.

    You are correct though, the 4.6 client does not regiser the FTA from a clean install. However, if you do an upgrade from a 4.5 client, the FTA's stay in place.

    I'm still doing some testing, but it looks like the  4.6.0.20200 client released on 4/15/2010 for TS resolves the script issue

    http://www.microsoft.com/downloads/details.aspx?FamilyID=e633164f-9729-43a8-9149-de651944a7fe&displaylang=en


    JJ
    • Marked as answer by JJ Zettle Thursday, April 29, 2010 6:09 PM
    Thursday, April 29, 2010 6:09 PM
  • Spoke too soon.

    The issue reared it heads the next time I cleared the cache.

    For now I'm going to stick with the 4.5 SP1 Hotfix 1 client (4.5.2.18131)
    JJ
    Tuesday, May 04, 2010 4:14 PM
  • This is a major issue also at our company with the new APP-V 4.6 RDS client it doesn't matter if it is the new 20200 build. Both are affected with the issue.

    A SCRIPT element in this OSD file is missing an executable. Report the following error code to your System Administrator.

    Error code: 4604EE8-07901A04-00000020

    Has anyone made a case with Microsoft about this issue, because we cannot go live with this unstable version.

     

    Wednesday, May 26, 2010 6:23 AM
  • I have submiited a ticket to premier support. They are aware of the issue, but don't have a solid time frame for when this will be fixed.

    In the mean time, we went with 4.5 SP1 Hotifx 1 in our TS evironment.

    However, 4.5 SP2 has since come out.

    Unless you're trying to make the move to 64 Bit, I would recommend testing out SP2 and going with that for the short term.


    JJ
    Monday, June 14, 2010 10:08 PM
  • Thank you for your reply. Please keep us posted on the outcome of what fix MS will release! I haven't got realy an option to go back to 4.5 SP2, because 4.6 has also some improvements that make it possible to sequence certain applications that didn't work under 4.5. The occurence of the issue is very low but nonetheless I hope on a quick fix for the issue.

     

    Regards,

    Erik

    Tuesday, June 15, 2010 5:08 AM
  • Did you had some information from Microsoft into resolving the issue.
    Monday, July 19, 2010 5:26 AM
  • We've had a case open with MS since 4.6.0.1523. Its not fixed in the lastest patch either 4.6.0.10241.

    Its an intermittent problem that affects some apps/some clients and not others. Unfortunately for the time being we've had to wait until we get a fault and then fix by removing the embedded script body and putting it in a batch file and use HREF instead. eg

    old:

    <SCRIPT EVENT="LAUNCH" PROTECT="TRUE" TIMING="PRE" WAIT="TRUE">

    <SCRIPTBODY LANGUAGE="Batch">@echo off \n

    echo Configuring MVRS. Please wait. \n

    wscript.exe \\\\xxx\\SGUKContent\\foldername\\script.vbs \n

    </SCRIPTBODY>

    </SCRIPT>

     

    new:

    <SCRIPT TIMING="PRE" EVENT="LAUNCH" PROTECT="TRUE" WAIT="TRUE">

    <HREF>\\filwz016\SGUKContent\MVRS-NEW.ctx\PreLaunch_MVRS.bat</HREF> 

    </SCRIPT>

     

    Having to be reactive I'm afraid, not good for service desk faults.

    Dave

    Friday, July 23, 2010 10:12 AM
  • Changing the NAME tag value in the OSD file seems to have got around this problem

     

    Paul

    Tuesday, October 26, 2010 11:02 AM
  • Paul,

     

    What about the name did you change? Was the name incorrect?

     

    Thanks

    Kevin

    Wednesday, October 27, 2010 5:34 PM
  • Hi.

    We experienced the same problems. Then I read this thread. We changed the name tag value - had a blank space in ours.

    That solved the problem for us.

    /Flemming

    Tuesday, November 30, 2010 1:13 PM
  • Hello, I am seeing this problem, did anyone get to the bottom of the cause?

     

    I have the following script in my osd:

    <DEPENDENCY>
     <SCRIPT TIMING="PRE" EVENT="LAUNCH" WAIT="TRUE" PROTECT="FALSE">
     <SCRIPTBODY>
     
     @echo off \n  
     cscript "\\\\users\\resources\\Win2k\\JMUAPPS\\ArchiCADv14\\InstallPreReq-Encode.wsf" \n
     
     </SCRIPTBODY>
     </SCRIPT>
     </DEPENDENCY>

    This works fine on an XP client running App-V client 4.6.

    I get a script element in the osd file is missing error on my windows 7 client with 4.6 sp1 client/

     

     

     

     

    Thursday, April 14, 2011 3:00 PM
  • This should be gone in 4.6 SP1.
    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    Tuesday, April 19, 2011 10:42 AM
  • Also be advised that this will also be addressed for App-V 4.6 in Hotfix 7 as well: The KB will be 2555574  for this.
    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    Tuesday, June 14, 2011 3:02 AM
  • Hi Steve, I'm still seeing this problem, my client is version 4.6.1.20870. I've added the following script:

     

    <DEPENDENCY>
    <SCRIPT TIMING="POST" EVENT="SHUTDOWN" WAIT="TRUE" PROTECT="TRUE">
    <SCRIPTBODY>

    cscript "\\\\users\\applications\\SoftGrid-Content\\Managed-Applications\\Dreamweaver&Fireworks_CS5_REV1_MNT\\fireworkstaskkill.wsf" \n

    </SCRIPTBODY>
     </SCRIPT>
     </DEPENDENCY>

    I then start getting an unexpected error occured.

     

    There are no problems with the script it is trying to run because I can run that up manually.

     

    Regards

     

    Ian


    Wednesday, June 22, 2011 8:54 AM
  • Hello,

    WAIT is deprecated....

    Any chance you can post the entire error message here and where it comes from?


    /Znack
    Wednesday, June 22, 2011 9:06 AM
  • Hello,

    An Unexpected erorr occured. Report the following error cod to your System Administrator.

    Error code:4615186-0C405A04-00001007

     

     

    Wednesday, June 22, 2011 9:31 AM
  • Hello,

    Your error code is different than this thread - I suggest creating a new one
    /Znack
    Wednesday, June 22, 2011 10:37 AM
  • Hi Steve,

    As per IanC's post, I have also just experienced this with client 4.6.1.20870 and can (bizarrely) confirm that it can be resolved by removing a blank space from the NAME parameter in the OSD!?

    In case it assists, I believe the client was upgraded as opposed to being a clean install.

    Regards,
    Danny

    Wednesday, July 20, 2011 10:35 AM
  • Are you referring to the SCRIPTBODY error or the Unexpected Error. That should probably spin up on a new thread as it does seem like it is worth investigating.
    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    Wednesday, July 20, 2011 8:38 PM
  • Hi Steve,

    Sorry - I meant the Script Element error (00000020) - I have a pre-launch script to copy a file which would work once or twice and then start generating the error which was fixed by removing a space from the NAME element!?  Very odd.

    Cheers,

    Danny 

    Thursday, July 21, 2011 9:01 AM
  • I'd advise opening an issue with MSFT support.
    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    Friday, July 22, 2011 11:20 PM