Solved

Why are users getting this error "could not create object named "scripting.filesystemobject"

Posted on 2009-05-19
3
847 Views
Last Modified: 2013-11-21
All users, whether admin or not  are getting this error message when loging into the termninal server (2003). could not create object named "scripting.filesystemobject".  The error message comes up after loging into the terminal when the script is suppose to start running. I've attached an image of the error message.  thanks for your help.  The error started showing up after MS was assisting with our finance application (SL 6.0).  MS made some changes in registry that resulted in this message poping up every time a login occurs.
 
ScriptError.jpg
0
Comment
Question by:y2kane4eva
3 Comments
 
LVL 3

Expert Comment

by:Cameron_S
ID: 24427264
It is a login script error - looks like it is broken, but without seeing what Line 30 actually is trying to do, it will be difficult to troubleshoot. If you can post what Line 30 in Login2.vbs reads that might give some insight as to why it is failing. Or have whoever wrote the login script for your Domain look at it and try to determine why it is failing when attempting to make the FSO call.
0
 
LVL 65

Accepted Solution

by:
RobSampson earned 500 total points
ID: 24427496
Hi, it seems that line 30 in your code might be
Set objFSO = WScript.CreateObjct("Scripting.FileSystemObject")

What happens if you omit the WScript. part and make that line just
Set objFSO = CreateObject("Scripting.FileSystemObject")

If that still produces an error, try clicking Start, Run, and type:
regsvr32 scrrun.dll

If that does not help: reinstall Windows Script 5.6.

Windows Script 5.6 for Windows XP and Windows 2000:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=C717D943-7E4B-4622-86EB-95A22B832CAA

Regards,

Rob.
0
 
LVL 1

Author Comment

by:y2kane4eva
ID: 24428448
i don't believe the problem is with the script.  there are other terminal servers that uses the same login script on the same domain that does not receive the error message at all.  the error only shows up on this terminal server.  But reinstalling windows script for server 2003 fixed the problem.  the error is no longer showing up.  Thanks.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Not long ago I saw a question in the VB Script forum that I thought would not take much time. You can read that question (Question ID  (http://www.experts-exchange.com/Programming/Languages/Visual_Basic/VB_Script/Q_28455246.html)28455246) Here (http…
With User Account Control (UAC) enabled in Windows 7, one needs to open an elevated Command Prompt in order to run scripts under administrative privileges. Although the elevated Command Prompt accomplishes the task, the question How to run as script…
Although Jacob Bernoulli (1654-1705) has been credited as the creator of "Binomial Distribution Table", Gottfried Leibniz (1646-1716) did his dissertation on the subject in 1666; Leibniz you may recall is the co-inventor of "Calculus" and beat Isaac…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

792 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question