PRB: VB/VB Apps Won't Run if Windows NT OLE Service Stopped (129800)
The information in this article applies to:
- Microsoft Visual Basic Standard Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Professional Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Professional Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 32-bit, for Windows 4.0
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Workstation 3.51
This article was previously published under Q129800 SYMPTOMS
If the OLE service under Windows NT is stopped, when you attempt to start
Visual Basic or an application written with Visual Basic, you'll see this
error:
"Unexpected error; quitting"
Or, if the OLE service is stopped while Visual Basic or an application
written with Visual Basic is running and you attempt to use an OLE control
in Visual Basic, you'll see this error:
"Unable to create embedded object"
CAUSE
Visual Basic uses OLE extensively for controls, data access, and even
internal communication. The OLE Service is a necessary component for Visual
Basic, but it is not absolutely necessary for this service to be running
under Windows NT. It may be stopped to increase the overall performance of
other tasks. If this is done, Visual Basic and Visual Basic applications
will not run.
STATUS
This behavior is by design.
Modification Type: | Major | Last Reviewed: | 12/9/2003 |
---|
Keywords: | kberrmsg kbprb kbProgramming KB129800 |
---|
|