Если файла нет ошибка vbscript

Troubleshooting Code 800A0035 – File not found

Code 800A0035 is a straightforward error to solve.  The secret is to read the Windows Script Error message carefully, then check the file path.  Guy bet’s there is a typo.

Introduction to Error Code 800A0035

Code 800A0035 is runtime error more common with an .ASP file than a .VBS.  The error is pointing to a file type or the wrong path rather than a pure scripting mistake.

The Symptoms You Get 800A0035

When you get a pop-up message box put on your detective hat, and pay close attention to the line number.  My point is that its the line in the script and not the file name following Script: 

The Cause of Error 800A0035

In the example above, Line 31: is the source of the error.  Char 1: is not always very useful as the error could be anywhere on the line, and WSH still blames char 1.

The cause of error 800A0035 is most likely to be a spelling mistake in the file,  however, Geoffery unearthed a bizarre problem where his files had an extra .extension.  For example instead of being info.txt, it was info.txt.txt.

The Solution

Before you find the root cause you may want to confirm the diagnosis by using a reference to a different file, preferably on a different drive.  If that works, then revisit the name of the original script.  Should you be hard-coding a path in your script, try copying and pasting from the bar in Windows Explorer.

  ‡

Example 1: Script to map a printer

In this example, the actual file was called Input.txt.txt, thus either rename that to the more normal single .txt, else change the script!

©

See More Windows Update Error Codes 8004 Series

• Error 800A101A8 Object Required   •Error 800A0046   •Error 800A10AD   •Error 800A000D

• Error 80048820   •Error 800A0401   •Review of SolarWinds Permissions Monitor

• Error 80040E14   • Error 800A03EA   • Error 800A0408   • Error 800A03EE

The Symptoms You Get 800A0035

When you get a pop-up message box put on your detective hat, and pay close attention to the line number.  My point is that its the line in the script and not the file name following Script: 

The Cause of Error 800A0035

In the example above, Line 31: is the source of the error.  Char 1: is not always very useful as the error could be anywhere on the line, and WSH still blames char 1.

The cause of error 800A0035 is most likely to be a spelling mistake in the file,  however, Geoffery unearthed a bizarre problem where his files had an extra .extension.  For example instead of being info.txt, it was info.txt.txt.

The Solution

Before you find the root cause you may want to confirm the diagnosis by using a reference to a different file, preferably on a different drive.  If that works, then revisit the name of the original script.  Should you be hard-coding a path in your script, try copying and pasting from the bar in Windows Explorer.

  ‡

Example 1: Script to map a printer

In this example, the actual file was called Input.txt.txt, thus either rename that to the more normal single .txt, else change the script!

©

See More Windows Update Error Codes 8004 Series

• Error 800A101A8 Object Required   •Error 800A0046   •Error 800A10AD   •Error 800A000D

• Error 80048820   •Error 800A0401   •Review of SolarWinds Permissions Monitor

• Error 80040E14   • Error 800A03EA   • Error 800A0408   • Error 800A03EE

Guy Recommends: WMI Monitor and It’s Free!

Windows Management Instrumentation (WMI) is one of the hidden treasures of Microsoft operating systems.  Fortunately, SolarWinds have created the WMI Monitor so that you can examine these gems of performance information for free.  Take the guess work out of which WMI counters to use for applications like Microsoft Active Directory, SQL or Exchange Server.

Download your free copy of WMI Monitor

Do you need additional help?

• For interpreting the WSH messages check Diagnose 800 errors.
• For general advice try my 7 Troubleshooting techniques.
• See master list of 0800 errors.
• Codes beginning 08004…
• Codes beginning 08005…
• Codes beginning 08007…
• Codes beginning 0800A…

Give something back?

Would you like to help others?  If you have a good example of this error, then please email me, I will publish it with a credit to you:

If you like this page then please share it with your friends

I am pretty new to all this VBS stuff because basically all I need to do is to make one simple VBS script, which I have possibly written, however, my problem is that it gives me 800A0035 or 800A004C error when I execute it for the first time on a particular PC, as soon as I execute it for the second time, it runs just OK and does what it is supposed to do. Incidentally, on my own computer it works OK even on the first execution.
I know that the errors have something to do with the wrong paths but I have checked my script several times and I am 100% positive that they are correct.

Here is the script:

Set objFSO = CreateObject("Scripting.FileSystemObject")
objFSO.MoveFile "rar.bat" , "rarp.bat"
'HideBat.vbs
CreateObject("Wscript.Shell").Run "rarp.bat", 0, True

What the script is supposed to do is to rename the rar.bat file to rarp.bat and run that batch file (rarp.bat) without popping up the command prompt. What the batch file does is not relevant, I guess, but anyway, it just runs WinRAR.

The rar.bat file and the VBS script are in the same folder, that’s why I have used relative paths in the script. I cannot use absolute paths because I need to run the script on several computers.

I have read somewhere on the internet that by default VBS script first looks for the files in C:WindowsSystem32 when relative paths are used. I have even tried using absolute paths in the script but it didn’t work either. Here is how I need them to look like: %systemdrive%users%username%appdataroamingrar.bat but this simply didn’t work in the VBS script.

I really think that what I need is really a simple script but apparently it’s pretty hard to get it working properly. I will be very grateful to those who help me.

Thank you a lot in advance.

Regards.

Я довольно новичок во всех этих вещах VBS, потому что в основном все, что мне нужно сделать, это сделать один простой сценарий VBS, который я, возможно, написал, однако моя проблема в том, что он дает мне 800A0035 or 800A004C ошибка, когда я запускаю его в первый раз на конкретном ПК, как только я запускаю его во второй раз, он работает нормально и делает то, что должен делать. Кстати, на моем собственном компьютере он работает нормально даже при первом запуске. Я знаю, что ошибки как-то связаны с неправильными путями, но я несколько раз проверял свой скрипт и на 100% уверен, что они верны.

Вот сценарий:

Set objFSO = CreateObject("Scripting.FileSystemObject")
objFSO.MoveFile "rar.bat" , "rarp.bat"
'HideBat.vbs
CreateObject("Wscript.Shell").Run "rarp.bat", 0, True

Что скрипт должен делать, так это переименовывать rar.bat файл в rarp.bat и запустите этот командный файл (rarp.bat) без появления командной строки. Что делает пакетный файл, я думаю, не имеет значения, но в любом случае он просто запускается WinRAR.

Компания rar.bat файл и сценарий VBS находятся в одной папке, поэтому я использовал относительные пути в сценарии. Я не могу использовать абсолютные пути, потому что мне нужно запустить скрипт на нескольких компьютерах.

Я где-то читал в Интернете, что по умолчанию сценарий VBS сначала ищет файлы в C:WindowsSystem32 когда используются относительные пути. Я даже пытался использовать абсолютные пути в скрипте, но это тоже не сработало. Вот как мне нужно, чтобы они выглядели: %systemdrive%users%username%appdataroamingrar.bat но это просто не работало в сценарии VBS.

Я действительно думаю, что мне нужен действительно простой скрипт, но, по-видимому, довольно сложно заставить его работать должным образом. Буду очень благодарен тем, кто мне поможет.

Заранее большое спасибо.

С уважением.