+1I using Outlook to send pdf's to customers and it is working fine with Windows7 and 32 bit.
On Windows10 and 64bit i got error's starting: Modify NAMESPACE-HANDLE LOGON().
The handle has a value.
Are there changes to make?
An AxdefGen64 has created a new def.
I using Outlook to send pdf's to customers and it is working fine with Windows7 and 32 bit.
On Windows10 and 64bit i got error's starting: Modify NAMESPACE-HANDLE LOGON().
The handle has a value.
Are there changes to make?
An AxdefGen64 has created a new def.
What is the error message?
+1I using Outlook to send pdf's to customers and it is working fine with Windows7 and 32 bit.
On Windows10 and 64bit i got error's starting: Modify NAMESPACE-HANDLE LOGON().
The handle has a value.
Are there changes to make?
An AxdefGen64 has created a new def.
Before I start the Cobolprogram, Outlook is already running. When Outlook not is already running, the error's below are the same.
I do not using AcuBench for debugging.
Below the values after statement: Modify NAMESPACE-Handle logon().
I using Outlook to send pdf's to customers and it is working fine with Windows7 and 32 bit.
On Windows10 and 64bit i got error's starting: Modify NAMESPACE-HANDLE LOGON().
The handle has a value.
Are there changes to make?
An AxdefGen64 has created a new def.
What is the working-storage definition of the handle?
+1I using Outlook to send pdf's to customers and it is working fine with Windows7 and 32 bit.
On Windows10 and 64bit i got error's starting: Modify NAMESPACE-HANDLE LOGON().
The handle has a value.
Are there changes to make?
An AxdefGen64 has created a new def.
77 OUTLOOK-APP HANDLE OF APPLICATION of OUTLOOK.
77 OUTLOOK-MAIL HANDLE OF MAILITEM of OUTLOOK.
77 NAMESPACE-HANDLE HANDLE OF NAMESPACE of OUTLOOK.
I using Outlook to send pdf's to customers and it is working fine with Windows7 and 32 bit.
On Windows10 and 64bit i got error's starting: Modify NAMESPACE-HANDLE LOGON().
The handle has a value.
Are there changes to make?
An AxdefGen64 has created a new def.
Please consider requesting ECN-4406 SUBJECT: Handle value clash
It is possible for DOTNET handle values to clash (different handles have the same value), causing many types of errors. The particular error first found was the created object handle having the same value as a later returned stored object handle. This resulted in a method not being found, since the wrong object was being searched.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
