Runtime error 91 object variable or with block variable not set что значит

Error: Ошибка 91 — Чтобы создать объектную переменную, нужно выполнить два шага. Сначала вы должны объявить объектную переменную. Затем вы должны назначить действительную ссылку на объектную переменную с помощью оператора Set. Аналогично, блок With … End With должен быть инициализирован путем выполнения

	Номер ошибки:	Ошибка во время выполнения 91
Название ошибки:	Object variable or With block variable not set
Описание ошибки:	There are two steps to creating an object variable. First you must declare the object variable. Then you must assign a valid reference to the object variable using the Set statement. Similarly, a With…End With block must be initialized by executing the
Разработчик:	Microsoft Corporation
Программное обеспечение:	Windows Operating System
Относится к:	Windows XP, Vista, 7, 8, 10, 11

Основы «Object variable or With block variable not set»

Это наиболее распространенное условие «Object variable or With block variable not set», известное как ошибка времени выполнения (ошибка). Разработчики, такие как Microsoft Corporation, обычно проходят через несколько контрольных точек перед запуском программного обеспечения, такого как Windows Operating System. К сожалению, инженеры являются людьми и часто могут делать ошибки во время тестирования, отсутствует ошибка 91.

В выпуске последней версии Windows Operating System может возникнуть ошибка, которая гласит: «There are two steps to creating an object variable. First you must declare the object variable. Then you must assign a valid reference to the object variable using the Set statement. Similarly, a With…End With block must be initialized by executing the ». Если происходит «Object variable or With block variable not set», разработчикам будет сообщено об этой проблеме, хотя отчеты об ошибках встроены в приложение. Затем Microsoft Corporation исправляет эти дефектные записи кода и сделает обновление доступным для загрузки. Таким образом при выполнении обновления программного обеспечения Windows Operating System, он будет содержать исправление для устранения проблем, таких как ошибка 91.

Почему происходит ошибка времени выполнения 91?

Сбой во время запуска Windows Operating System или во время выполнения, как правило, когда вы столкнетесь с «Object variable or With block variable not set». Вот три наиболее заметные причины ошибки ошибки 91 во время выполнения происходят:

Ошибка 91 Crash — она называется «Ошибка 91», когда программа неожиданно завершает работу во время работы (во время выполнения). Это возникает, когда Windows Operating System не реагирует на ввод должным образом или не знает, какой вывод требуется взамен.

Утечка памяти «Object variable or With block variable not set» — Когда Windows Operating System обнаруживает утечку памяти, операционная система постепенно работает медленно, поскольку она истощает системные ресурсы. Потенциальные триггеры могут быть «бесконечным циклом», или когда программа выполняет «цикл» или повторение снова и снова.

Ошибка 91 Logic Error — Логические ошибки проявляются, когда пользователь вводит правильные данные, но устройство дает неверный результат. Это может произойти, когда исходный код Microsoft Corporation имеет уязвимость в отношении передачи данных.

Как правило, такие Microsoft Corporation ошибки возникают из-за повреждённых или отсутствующих файлов Object variable or With block variable not set, а иногда — в результате заражения вредоносным ПО в настоящем или прошлом, что оказало влияние на Windows Operating System. Большую часть проблем, связанных с данными файлами, можно решить посредством скачивания и установки последней версии файла Microsoft Corporation. Кроме того, некоторые ошибки Object variable or With block variable not set могут возникать по причине наличия неправильных ссылок на реестр. По этой причине для очистки недействительных записей рекомендуется выполнить сканирование реестра.

Распространенные сообщения об ошибках в Object variable or With block variable not set

Object variable or With block variable not set Проблемы, связанные с Windows Operating System:

• «Ошибка программного обеспечения Object variable or With block variable not set. «
• «Ошибка программного обеспечения Win32: Object variable or With block variable not set»
• «Извините, Object variable or With block variable not set столкнулся с проблемой. «
• «Object variable or With block variable not set не может быть найден. «
• «Отсутствует файл Object variable or With block variable not set.»
• «Ошибка запуска в приложении: Object variable or With block variable not set. «
• «Файл Object variable or With block variable not set не запущен.»
• «Отказ Object variable or With block variable not set.»
• «Object variable or With block variable not set: путь приложения является ошибкой. «

Ошибки Object variable or With block variable not set EXE возникают во время установки Windows Operating System, при запуске приложений, связанных с Object variable or With block variable not set (Windows Operating System), во время запуска или завершения работы или во время установки ОС Windows. При появлении ошибки Object variable or With block variable not set запишите вхождения для устранения неполадок Windows Operating System и чтобы HelpMicrosoft Corporation найти причину.

Источники проблем Object variable or With block variable not set

Эти проблемы Object variable or With block variable not set создаются отсутствующими или поврежденными файлами Object variable or With block variable not set, недопустимыми записями реестра Windows Operating System или вредоносным программным обеспечением.

Более конкретно, данные ошибки Object variable or With block variable not set могут быть вызваны следующими причинами:

• Поврежденные ключи реестра Windows, связанные с Object variable or With block variable not set / Windows Operating System.
• Вирус или вредоносное ПО, которые повредили файл Object variable or With block variable not set или связанные с Windows Operating System программные файлы.
• Другая программа (не связанная с Windows Operating System) удалила Object variable or With block variable not set злонамеренно или по ошибке.
• Другое приложение, конфликтующее с Object variable or With block variable not set или другими общими ссылками.
• Поврежденная загрузка или неполная установка программного обеспечения Windows Operating System.

Продукт Solvusoft

Загрузка
WinThruster 2022 — Проверьте свой компьютер на наличие ошибок.

Совместима с Windows 2000, XP, Vista, 7, 8, 10 и 11

Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление

Overview

VBA run-time error 91 is a common trappable error seen in VBA development. This error is triggered when you try to use an object variable (i.e. a variable which is of the “Object” type) that has no object (properly) assigned to it.

This error is a very common technical error which can often be encountered by beginners and even experienced programmers. Therefore, it is useful that you understand it, learn about how it is triggered, and how to work around it. This knowledge will help you in your development as a programmer in Microsoft Office.

Key Concept Before We Start — Value Assignment to Variables in VBA

Before we look into the topic of Error 91, let’s go through a very important coding concept in VBA about value assignment to variables. There are two main types of value assignment, which you can think of as (1) “object” and (2) “non-object”. You can see in the table below that for all variables which are non-objects, we simply use “=” to assign values to them. However, for object variables, we must always begin the assignment with “Set“.

You can now see why Error 91 is called “Object variable not Set”.  It is because you should assign an object to an object variable with the SET statement.

So How is Error 91 Triggered?

There are four main reasons you might encounter this error:

1. “Set” is omitted in the assignment of an object variable
2. Using GoTo to jump into a “With” block
3. Attempting to use an object variable that has been set to Nothing.
4. Attempting to use an object which is not yet being created

Scenario 1: “Set” is Omitted in the Reference to an Object Variable

The macro “example1” below shows the most straightforward scenario when Error 91 can be triggered. The variable “MyObject” is an object variable. In line 4, “MyObject = ActiveSheet” attempts to assign a worksheet object (the ActiveSheet) to MyObject. Because the SET statement was omitted, this line of code causes Error 91 during run time.

Sub example1()
Dim MyObject As Object   'Create object variable
Dim x As String
MyObject = ActiveSheet   'Create object reference [Err 91 here]
x = MyObject.Name        'Assign Count value to x
MsgBox "Sheet name is: " & x
End Sub

Solution:

To avoid making this mistake, you must always remember to use a Set statement to assign an object to an object variable.

See the correct way of object variable assignment with a Set statement in line 4 below:

Sub example1_fixed()
Dim MyObject As Object    	'Create object variable
Dim x  As String
Set MyObject = ActiveSheet	'Create object reference the correct way
x = MyObject.Name        	'Assign Count value to x
MsgBox "Sheet name is: " & x
End Sub

Scenario 2: Using GoTo to Jump into a “With” Block

If a GoTo statement jumps into a With block, it may cause Error 91. See the example below:

Sub BadJumper()
    Dim x As Integer    'counter for use with for loop
    Dim result As String
    x = WorksheetFunction.RandBetween(1, 10) 'Draw integer between 1&10
    If x > 5 Then
        GoTo jumper1   'Jump if x >5
    Else
        End			'Terminate macro if x<=5
    End If
    With Range("A1")
jumper1:
        .Value = x 	'place rolling total [Err 91 here]
    End With
End Sub

In line 6, the GoTo statement jumps to “jumper1” when x>5. The With statement in line 10 is bypassed and the process jumps straight to line 12 which is supposed to put the value of x into cell A1. Error 91 will be trigger right there.

Having the With statement (line 10) bypassed, Excel has no idea what object the “Value” property (line 12) refers to, and therefore has no idea where to place the value of x.

Solution:

To avoid this mistake, make sure your GoTo statements never jump directly inside a WITH block.

Scenario 3: Attempting to Use an Object Variable that Has Been Set to Nothing.

Error 91 can also be triggered when the code attempts to use an object variable that has been set to “Nothing”. (i.e. the object variable has been reset/erased.)

In line 5 of the macro below, the object variable “MyObject” has been reset by the statement “Set MyObject = Nothing“. Error 91 will happen in line 6 (when the code tries to display the name of MyObject in a Msgbox). This is equivalent to having an blank object variable which has nothing assigned to it.

Sub example3()
Dim MyObject As Object      'Create object variable.
Set MyObject = ActiveSheet  'Create valid object reference.
MsgBox "Sheet name is: " & MyObject.Name
Set MyObject = Nothing
MsgBox "Sheet name is: " & MyObject.Name	'[Err 91 here]
End Sub

Solution:

After resetting an object variable by setting it to nothing, make sure you re-assign an object to it (with a Set statement) before calling it.

Scenario 4: Attempting to Use an Object which Is Not Yet Created During Run-Time

The previous examples showed Error 91 scenarios in which objects have not been properly assigned to object variables. There are situations where Error 91 is triggered because the object has not been created.

This scenario normally applies to objects which are not under any of the Microsoft Office Application objects. For instance, (1) generic Visual Basic objects (such as Collection, Dictionary) or (2) Objects in libraries added through “Add Reference”.

Example (part 1):

The two macros below “ex4_Collection” and “ex4_Dictionary” contain very typical mistakes made by VBA programmers when using Collections and Dictionaries. In line 2 of both macros, the objects were declared, and then values are being added to the Collection/Dictionary in line 3, where Error 91 occurred.

Sub ex4_Collection()
Dim MyCollection1 As Collection
MyCollection1.Add Item:=123		'[Err 91 here]
End Sub 

Sub ex4_Dictionary()
Dim dict As Scripting.Dictionary
dict.Add "key1", 123		'[Err 91 here]
End Sub

Solution:

To fix the macro, you need to learn the syntax to create a new instance of the object.  See below how the two macros are fixed by inserted a new Set statement in line 3 of both macros.

Sub ex4_Collection_fixed ()
Dim MyCollection1 As Collection
Set MyCollection1 = New Collection   'create the Collection
MyCollection1.Add Item:=123
End Sub

Sub ex4_Dictionary_fixed()
Dim dict As Scripting.Dictionary
Set dict = New Scripting.Dictionary	'create the Dictionary
dict.Add "key1", 123
End Sub

Example (part 2):

Here is another very common case when a reference to a library is added. For example, the Office library is added through “Add Reference” from the Tools menu in VB Editor:

The macro below tries to create a Mail item. But Error 91 will be triggered in line 3. The macro seems perfectly fine, where the Outlook application object and the MailItem object have been declared, and then a Set statement is used to create a Mail item. But why there is still the Error 91?

Sub ex4_Outlook()
  Dim OutlookApp As Outlook.Application
  Dim OutlookMail As Outlook.MailItem
  Set OutlookMail = OutlookApp.CreateItem(olMailItem)
End Sub

The macro below shows the correct approach to create such an (early binding) instance of the Outlook application object. See how line 3 has been added?

Sub ex4_Outlook_fixed()
  Dim OutlookApp As Outlook.Application
  Dim OutlookMail As Outlook.MailItem

  Set OutlookApp = New Outlook.Application  'create Outlook App
  Set OutlookMail = OutlookApp.CreateItem(olMailItem)
End Sub

The skills to interact with object variables is crucial in VBA development and successful declaration and assignment are the first steps. Understanding the above scenarios can for sure help you program more efficiently in VBA.

Attention Before you read this post, I highly recommend you check out my resources page for access to the tools and services I use to not only maintain my system but also fix all my computer errors, by clicking here!

A runtime error is basically an error that occurs during a programs “runtime”, to put it simply. Each runtime error has its own error code, such as 91, in this case. When an individual experiences a runtime error 91 on their computer, it’s usually accompanied by a “Object variable set to nothing” error message.

Runtime error 91 is a fairly common error on Windows based systems that usually occur at random moments. This error doesn’t have a clear defined cause; however, the Visual Basic DCOMCnfg.exe on your computer is one known culprit for this error; which is usually the result of damage, and/or corruption to this file. With that said, there are a number of things that you can do, when you find yourself in this situation.

Symptoms of Runtime Error 91

There are a number of symptoms individuals may experience when they encounter an error 91, but of the various symptoms, the most common are the following:

• The active program window crashes, just as the Error 91 dialog box appears.
• Error 91 frequently crashes, as you attempt to run the same application.
• “Object variable or with block variable not set” error message is displayed.
• Windows performance becomes very slow and unresponsive to both keyboard and mouse input.
• Computer randomly freezes for several seconds at a time.

The runtime error 91 can occur while you are installing an application, while you are using a program, within a Windows based environment, during the startup phase of your computer or while it is shutting down, or even when installing Windows for the first time. Keeping note of when you actually experience this error is very important, as it will help you when troubleshooting the problem.

Cause of Error

Already speaking briefly about the cause of this error, .NET Framework and Visual Studio (in addition to DCOMCnfg.exe) are also known to be related to this error; these are tools used in the development of applications.

Within a programming environment, the runtime error 91 would tell the programmer that an invalid variable, which has the value of “nothing”, is being referenced to.

Usually, it’s not known whether or not an application will generate a runtime error 91, till after the user attempts to run it. Error 91 can also be caused by a network blackout, while an application is attempting to download additional data from its server.

The general consensus amongst this error is that it occurs, when attempting to use an application that has issues with the variables within it.

A variable is essentially a container that a programmer will use to store flexible data. An invalid variable could relate to the wrong kind of data being stored in a variable, or the variable being incorrectly referenced.

Fixing this error will thus, entail repairing the coding of a particular application, in order to prevent the error from reappearing, every time you try to use it.

Fixing Runtime Error 91

Below are a number of fixes that an individual can attempt when trying to fix this problem. This error is a pretty difficult one to fix, because of the personal nature of it, as it relates to the application. However, there are still many things that you can do, to at least mask the problem.

Use Registry Cleaner

One thing you should definitely do before anything else is use a registry cleaner to scan through your system so that it can repair any damaged configurations which could be aiding the runtime error.

The function of the registry cleaner is to fix errors within your computers registry, the registry is the area of the computer were all you’re most important data is stored, such as system options, preferences and various other things.

Whenever you install and use an application on your computer, numerous registry settings are created and used, but this process can also lead to redundant entries, invalid registry keys and damaged settings.

Fixing this problem will require you to use a registry cleaner, which will scan through your entire system, locate all of these errors and fix them. With that said, there are various registry cleaners out there, but the one I personally recommend is Advanced System Repair Pro, and that’s because of its multifaceted nature. Anyway, you can pick this tool up here:

CLICK HERE TO CHECK OUT ADVANCED SYSTEM REPAIR PRO

Check for Viruses

The next step you should consider doing when attempting to fix a runtime error 91, is to use an antivirus scanner. In a lot of situations, this issue is the result of malware or viruses running within the background of the computer causing the application to crash, every time you use it. Because viruses spread, infecting more components of your operating system over time, it’s very important that you address it as soon as possible.

A good antivirus program should have little difficulty finding the virus on your computer, and removing it. Antivirus tools are very easy to use, the only thing that is required on your end, is to ensure that everything on it is up-to-date, especially its virus definitions.

With that said, simply run a full scan of your system, for this task. If you don’t have an antivirus tool on your computer, or you think your tool isn’t very good, then I recommend you use SpyHunter, alternatively you could check out my post on the very best antivirus tools.

To learn more about SpyHunter, please visit the following link:

CLICK HERE TO CHECK OUT SPYHUNTER

The solution(s) below are for ADVANCED level computer users. If you are a beginner to intermediate computer user, I highly recommend you use the automated tool(s) above!

Reinstall Application

If all other methods have failed, then you should consider reinstalling the application. There is a good chance that the error was due to an incomplete installation, in which case, a reinstallation should fix it.

When it comes to reinstalling the application, you want to ensure that every trace of the application is removed; this includes redundant files, folders and registry entries, before you reinstall it.

However, in order for you to do this, you will need to use the uninstallation tool called Express Uninstaller. This powerful removal tool is capable of not only removing applications using the conventional InstallShield, but also running independent scans of your operating system and registry and removing all associated data. Anyway, you can acquire this excellent tool from here:

CLICK HERE TO CHECK OUT EXPRESS UNINSTALLER

Check for Patches

Whenever an individual encounters a runtime error 91 while attempting to run a program, there is very little they can do about the coding for that particular program. However, one possibility entails checking the website of the developer, to see whether or not they have released a patch that fixes the bug in the code.

If you do find a patch, simply download it, and apply it to the program. The patch should come with its own update facility to make the update process more seamless.

Alternatively, if the program has its own update utility, you can try that, before heading off to the website of the developer.

Check Windows Updates

Another idea that has proven to be quite effective at fixing this problem involves checking for Windows updates. This is because, not only do developers release patches for bugs in their programs, but so does Microsoft, for their operating system.

If the application that is generating a runtime error 91 came preinstalled with your computer, when you purchased it, then you can try checking the websites of the computer manufacturers for any updates for this problem.

This is an excellent way for you to find all the appropriate updates for your computer make and model. You may find updates that fix the runtime error in additional to updates that may improve the overall performance of your computer. By keeping your computer up-to-date with the latest updates, not only will it secure it from bugs, but it will also secure it from hacks and viruses.

Configure DCOMCnfg.exe

If the runtime error you’re experiencing is due to the DCOMCnfg.exe, then you will need to reconfigure its settings to fix the problem. The purpose of this program is to control file permissions and various other things, related to Visual Basic, on your computer.

Unfortunately, if the necessary steps are not taken to rectify this problem, the error will persist, thus it’s important that you configure DCOMCnfg.exe to Allow “Everyone”.

If you don’t know how to do this, I suggest you check out the following report: https://support.microsoft.com/en-us/kb/183607

Turn Off Error Messages

If you’ve searched for a fix for the application, but were unable to find anything, then the first thing you should do is contact the developer to notify them about the problem.

The next option available to you is to turn off script debugging, that way, you won’t have to see the error message, every time it occurs. After all, the error message is of little value to you.

The Machine Debug Manager is the tool that operates the script debugging, a tool that you can control through Internet Explorer. Anyway, to disable it, simple do the following:

1. First, ensure you have booted into your computer with administrative rights.

2. Then, double click on the Internet Explorer Icon, to start the browser.

3. Once Internet Explorer starts, click on Tools [Cog] -> Internet Options.

4. This will bring up the Internet Options, from here, click on the Advanced Tab, and check the box next to Disable Script Debugging (Internet Explorer) and Disable Script Debugging (Other) then click on OK.