Prev: Local to Remote switch for retrieving file ownership in XP
Next: Exporting an Excel Sheet to Outlook
From: Bharat Suneja [MVP] on 14 Nov 2006 20:31
Just tried to run a simple script I had - the script works, but towards the
end I use the Scripting.FileSystemObject to create a text file and write the
results to it. I'm getting the following error:
Microsoft VBScript runtime error: ActiveX component can't create object:
'Scripting.FileSystemObject'

Is this because of some new IE7 security setting? I have IE7 and Office 2007
installed.

Thanks,
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------



From: "Tim Williams" timjwilliams at gmail dot on 14 Nov 2006 21:25
FSO is not "safe for scripting". Try setting your browser security settings to "dangerous"...

I'm assuming you're running your script in a browser, but you're not clear on this in your post.


--
Tim Williams
Palo Alto, CA


"Bharat Suneja [MVP]" <bharatsuneja(a)no.spam.org> wrote in message news:OXOdSXFCHHA.3620(a)TK2MSFTNGP02.phx.gbl...
> Just tried to run a simple script I had - the script works, but towards the
> end I use the Scripting.FileSystemObject to create a text file and write the
> results to it. I'm getting the following error:
> Microsoft VBScript runtime error: ActiveX component can't create object:
> 'Scripting.FileSystemObject'
>
> Is this because of some new IE7 security setting? I have IE7 and Office 2007
> installed.
>
> Thanks,
> --
> Bharat Suneja
> MVP - Exchange
> www.zenprise.com
> NEW blog location:
> www.exchangepedia.com/blog
> ----------------------------------------------
>
>
>


From: TDM on 15 Nov 2006 11:24

"Bharat Suneja [MVP]" <bharatsuneja(a)no.spam.org> wrote in message
news:OXOdSXFCHHA.3620(a)TK2MSFTNGP02.phx.gbl...
> Just tried to run a simple script I had - the script works, but towards
> the end I use the Scripting.FileSystemObject to create a text file and
> write the results to it. I'm getting the following error:
> Microsoft VBScript runtime error: ActiveX component can't create object:
> 'Scripting.FileSystemObject'
>
> Is this because of some new IE7 security setting? I have IE7 and Office
> 2007 installed.
>
> Thanks,
> --
> Bharat Suneja
> MVP - Exchange
> www.zenprise.com
> NEW blog location:
> www.exchangepedia.com/blog
> ----------------------------------------------
>
>
>

This is interesting. Are you running your VBS in an instance of IE ?
I would not think that a plain vanilla VBS from the command line
would generate this error. I will install IE7 and play around, this
could be a MAJOR impact on the huge library of scripts that I have.

If you are running in an instance of IE, then I can certainly understand
this. In the case where I use FSO from IE, I test the registry for this
setting before spawning IE and change the value, then put the value
back after closing IE and ending the script.

TDM



From: Bharat Suneja [MVP] on 15 Nov 2006 11:40
That's the funny thing - I'm running this from a command-line.... I have no
clue what ActiveX has to do with FSO in a normal shell window running
locally!

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------


"Tim Williams" <timjwilliams at gmail dot com> wrote in message
news:u%23TdK1FCHHA.3600(a)TK2MSFTNGP06.phx.gbl...
> FSO is not "safe for scripting". Try setting your browser security
> settings to "dangerous"...
>
> I'm assuming you're running your script in a browser, but you're not clear
> on this in your post.
>
>
> --
> Tim Williams
> Palo Alto, CA
>
>
> "Bharat Suneja [MVP]" <bharatsuneja(a)no.spam.org> wrote in message
> news:OXOdSXFCHHA.3620(a)TK2MSFTNGP02.phx.gbl...
>> Just tried to run a simple script I had - the script works, but towards
>> the
>> end I use the Scripting.FileSystemObject to create a text file and write
>> the
>> results to it. I'm getting the following error:
>> Microsoft VBScript runtime error: ActiveX component can't create object:
>> 'Scripting.FileSystemObject'
>>
>> Is this because of some new IE7 security setting? I have IE7 and Office
>> 2007
>> installed.
>>
>> Thanks,
>> --
>> Bharat Suneja
>> MVP - Exchange
>> www.zenprise.com
>> NEW blog location:
>> www.exchangepedia.com/blog
>> ----------------------------------------------
>>
>>
>>
>
>


From: Bharat Suneja [MVP] on 15 Nov 2006 11:39
No, it's a simple VBScript running locally! I'm not sure I can nail this
down to IE7, but it used to work for years!

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------


"TDM" <rpuffd(a)gmail.com> wrote in message
news:%23IIMDKNCHHA.1012(a)TK2MSFTNGP04.phx.gbl...
>
> "Bharat Suneja [MVP]" <bharatsuneja(a)no.spam.org> wrote in message
> news:OXOdSXFCHHA.3620(a)TK2MSFTNGP02.phx.gbl...
>> Just tried to run a simple script I had - the script works, but towards
>> the end I use the Scripting.FileSystemObject to create a text file and
>> write the results to it. I'm getting the following error:
>> Microsoft VBScript runtime error: ActiveX component can't create object:
>> 'Scripting.FileSystemObject'
>>
>> Is this because of some new IE7 security setting? I have IE7 and Office
>> 2007 installed.
>>
>> Thanks,
>> --
>> Bharat Suneja
>> MVP - Exchange
>> www.zenprise.com
>> NEW blog location:
>> www.exchangepedia.com/blog
>> ----------------------------------------------
>>
>>
>>
>
> This is interesting. Are you running your VBS in an instance of IE ?
> I would not think that a plain vanilla VBS from the command line
> would generate this error. I will install IE7 and play around, this
> could be a MAJOR impact on the huge library of scripts that I have.
>
> If you are running in an instance of IE, then I can certainly understand
> this. In the case where I use FSO from IE, I test the registry for this
> setting before spawning IE and change the value, then put the value
> back after closing IE and ending the script.
>
> TDM
>
>
>


 |  Next  |  Last
Pages: 1 2 3
Prev: Local to Remote switch for retrieving file ownership in XP
Next: Exporting an Excel Sheet to Outlook