Ошибка vbs требуется объект

I’m getting an «object required» error on line 54, the last line, when I run the following script. What is wrong?

 Option Explicit
Dim cmdString, g_strHostFile, filepath, flexnetpath, importcmd, dtmToday, dtmYesterday, dtmFileDate, param1, param2, param3, i4path, objFSO, objTextStream, g_strComputer, WshShell
'Initialize global constants and variables.
Const FOR_READING = 1
g_strHostFile = "D:dataimportsLUM_servers.txt"
i4path = "C:IFORWINBINi4blt.exe"
filepath = "D:DataImports"
flexnetpath = "C:Program Files (x86)FlexnetManagerAdmin"
importcmd = flexnetpath & "flexnet bulkimport -uadmin -padmin -f" & filepath
dtmToday = Date()
dtmYesterday = Date() - 1
dtmFileDate = Year(Date) & padDate(Month(Date)) & padDate(Day(Date))
param1 = "-r1 -e2,4 -n "
param2 = " -v 'Dassault Systemes' -b "
param3 = " -g "
WScript.Echo "i4Path: " & i4path
WScript.Echo "FilePath: " & filepath
WScript.Echo "flexnetpath: " & flexnetpath
WScript.Echo "importcmd: " & importcmd
WScript.Echo "dtmToday: " & dtmToday
WScript.Echo "dtmYesterday: " & dtmYesterday
WScript.Echo "dtmFileDate: " & dtmFileDate

'Read LUM Server Names from text file.
Set objFSO = CreateObject("Scripting.FileSystemObject")
If objFSO.FileExists(g_strHostFile) Then
  Set objTextStream = objFSO.OpenTextFile(g_strHostFile, FOR_READING)
Else
  WScript.Echo "Input file " & g_strHostFile & " not found."
  WScript.Quit
End If
'Loop through list of computers and perform tasks on each.
Do Until objTextStream.AtEndOfStream
  g_strComputer = objTextStream.ReadLine
WScript.Echo "Processing Server: " & g_strComputer
Set cmdString = i4path & param1 & g_strComputer & param2 & dtmYesterday & param3 & dtmToday & filepath & g_strComputer & "_" & dtmFileDate & "_lum.lrl"
WScript.Echo "Processing Command: " & cmdString
Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run "cmdString"
Loop
objTextStream.Close
Set WshShell = WScript.CreateObject("WScript.Shell")
WScript.Echo "Processing Bulk Import: " & importcmd
WshShell.Run "importcmd"

Function padDate(intNumber)
 if intNumber <= 9 Then
  padDate = "0" & CStr(intNumber)
 Else
  padDate = CStr(intNumber)
 End If
End Function

asked Jul 16, 2010 at 14:49

Object required is raised when you have a statement like Set x = y where x is not an object type, but is instead an simple type (Integer, Double, Date, etc. ). I think the line

Set cmdString = i4path & param1 & g_strComputer & param2 & ...

is causing the error, and I think all you have to do is remove the Set statement. I think strings do not derive from Object and thus do not need the Set statement.

There are a few problems, I think.

 importcmd = flexnetpath & "flexnet bulkimport -uadmin -padmin -f" & filepath

You probably need some spaces:

 importcmd = flexnetpath & " flexnet bulkimport -uadmin -padmin -f " & filepath

Set is only used with objects, not strings, so it should be removed from this line:

 Set cmdString = i4path & param1 & g_strComputer & param2 & dtmYesterday & param3 & dtmToday & filepath & g_strComputer & "_" & dtmFileDate & "_lum.lrl"

I am fairly sure you either mean

 WshShell.Run importcmd

Or

 WshShell.Run """" & importcmd & """"

answered Jul 16, 2010 at 14:58

Could someone tell me why does this line error:

set my_obj = wscript.CreateObject("ObjectTest","pref_")

It gives this error:

Object required: ‘wscript’

If I run this code:

Set WScript = CreateObject("WScript.Shell")
set my_obj = CreateObject("ObjectTest","pref_")

I get this error instead:

Object doesn’t support this property or method: ‘CreateObject’

I’m running the vbscript from within a Delphi app.

Object required: ‘wscript’

I’m running the vbscript from within a Delphi app.

This is why your script is failing. The wscript object is only defined when the script is run by wscript.exe. To do what you are attempting, you need to implement your own object and provide it to the script environment for the script code to access when needed.

Assuming you are using IActiveScript to run your script, you can write a COM Automation object that implements the IDispatch interface, and then you can create an instance of that object and give it to the IActiveScript.AddNamedItem() method before then calling IActiveScript.SetScriptState() to start running the script.

For example, write an Automation object that exposes its own CreateObject() method, give it to AddNamedItem() with a name of App, and then the script can call App.CreateObject(). Your CreateObject() implementation can then create the real requested object and hook up event handlers to it as needed. To fire events back into the script, use the IActiveScript.GetScriptDispatch() method to retrieve an IDispatch for the desired procedure defined in the script, and then use IDispatch.Invoke() with DISPID 0 and the DISPATCH_METHOD
flag to execute that procedure with the desired input parameters.

Your object can implement any properties and methods that you want the script to have access to.

answered Feb 4, 2016 at 6:19

The reason your script is failing is due to a few occurrences.

1. DO NOT use «WScript» as an object especially while coding in Windows-Based Script Host(or WSH), as the program assumes you are running wscript.exe or calling WScript commands.
2. Use Dim! If the first rule wasn’t null, this is why. Using command «Option Explicit» in VBScript requires users to Dim any object or calling of an object.

A fixed code would be:

Option Explicit
Dim 1, 2
Set 1 = WScript.CreateObject("WScript.Shell")
Set 2 = WScript.CreateObject("ObjectTest", "pref_")

answered Feb 23, 2021 at 3:05