-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
com_error: (-2147221164, 'Class not registered', None, None) #1
Comments
yes, we have this issue before, not sure the root cause. |
Hi
thanks very much for your replay.
Yes I already installed the CANape application.
My python version : Python 3.7.6 (default, Jan 8 2020, 20:23:39) [MSC v.1916 64 bit (AMD64)] :: Anaconda, Inc. on win32。 So I thing it is 64, right ?
At 2020-07-26 10:38:10, "sgnes" <[email protected]> wrote:
yes, we have this issue before, not sure the root cause.
I assume you already installed the CANape application, right?
what is the python version, 32 or 64 bit?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hi
thanks very much for your replay.
Yes I already installed the CANape application.
My python version : Python 3.7.6 (default, Jan 8 2020, 20:23:39) [MSC v.1916 64 bit (AMD64)] :: Anaconda, Inc. on win32。 So I thing it is 64, right ?
How did you fix it?
At 2020-07-26 10:38:10, "sgnes" <[email protected]> wrote:
yes, we have this issue before, not sure the root cause.
I assume you already installed the CANape application, right?
what is the python version, 32 or 64 bit?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
**when I run the following script, then com_error: (-2147221164, 'Class not registered', None, None) happen.
is it happen on your side before? if yes, how your fix it?
self._Canape = DispatchEx('CANape.Application')**
The text was updated successfully, but these errors were encountered: