Run-time error 3633 in Visual Basic program

[cjolley]

Hi... I'm a brand-new wine user, and I'm trying to run some analytical software that was developed (by someone else) in Visual Basic. (see https://pardee.du.edu/access-ifs). When I run it from the command line, a window pops up with a message reading: "Run-time error '3633'". I was able to find some discussion of this type of error on a VB forum (http://www.vbforums.com/showthread.php? ... error-3633), but I'm not sure how to do what they're recommending from within wine.

Here's the output that came up in my terminal window:
craig@craig-XPS-13-9370:~$ wine "C:\Users\Public\IFs\IFs.exe"
0114:fixme:olepicture:OleLoadPictureEx (0x13544e4,774,0,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x33f9b0), partially implemented.
0114:fixme:olepicture:OLEPictureImpl_SaveAsFile (0x21c7f28)->(0x26d0030, 0, (nil)), hacked stub.
0114:fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}

Any ideas about what might be happening here?

Thanks!

[cjolley]

UPDATE: After poking around a little, I discovered another forum post (viewtopic.php?f=8&t=17556) where someone was trying to install the run the same program using wine. Following the suggestions there and elsewhere, I re-installed with a 32-bit wineprefix and installed MS Jet 4.0 using winetricks.

Now the program launches all right (although the fonts look a little weird), but quickly crashes after giving me a window that says: "Run-time error '-2147417848 (80010108)' Automation error."

This apparently has something to do with Commandbars.ocx (https://support.microsoft.com/en-us/hel ... ct-invoked). This post (viewtopic.php?f=8&t=28585) seemed to suggest that mfc42 might help with that, but the error message was unchanged.

Any guesses as to what I could try next?

[fargodwe]

use winetricks and install jet40 and mdac28. I'm not sure but this may require using a 32-bit wine prefix as well.

https://wiki.winehq.org/Winetricks

to create a 32-bit wine prefix, IF it needs it:
- make a directory to hold your instance of wine. As an example:
- create a folder WINE-PREFIXES in your home directory
- create a folder MYAPP in the WINE-PREFIXES directory
- open a terminal window
- WINEPREFIX=/home/<your usedid>/WINE-PREFIXES/MYAPP WINEARCH=win32 winecfg

to install jet40 and mdac28:
- open a terminal window
- WINEPREFIX=/home/<your userid>/WINE-PREFIXES/MYAPP winetricks jet40
- WINEPREFIX=/home/<your userid>/WINE-PREFIXES/MYAPP winetricks mdac28

Then install your app again in the new wine prefix and try it again.

[fargodwe]

You second post didn't show when I posted my first reply - sorry about that.

I assume you just let wine install to the default .wine prefix - that's ok but I learned from a guru here that it's actually better to use separate wine prefixes. That way if one gets screwed up you don't have to reinstall everything. That being said, I'm just a beginner here myself. I did a little research on your last post. That link to Microsoft would require you to have the installation cd/dvd, then install them to wine.

Another post on the net had another suggestion for another app with a similar problem, so you could try it if you like:

winetricks vcrun6

and possbily:

winetricks vcrun2003

Then try re-installing your app.

I'll keep searching the net to see if I can find anything else. Someone here with more experience may be able to help you out.

[fargodwe]

BTW - which version of the app from the page you pointed to did you download and install? I could try working with it here and see if I can figure it out.

The runtime error you posted would need to be sent to the developer(s) for them to know what they were doing at that point. That in itself could point to something that needs to be installed in wine.

[fargodwe]

I downloaded and installed the desktop version. In the end I got the same error you did. I created a log file and noticed the following at the end of the log file:

Code: Select all

0009:fixme:olepicture:OleLoadPictureEx (0x147c824,774,0,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32eb10), partially implemented.
0009:fixme:olepicture:OleLoadPictureEx (0x1494204,774,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32e28c), partially implemented.
0009:fixme:olepicture:OleLoadPictureEx (0x1494204,140233,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32e25c), partially implemented.
0009:fixme:olepicture:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0 palette.
0009:fixme:ole:NdrCorrelationInitialize (0x32c32c, 0x32c4bc, 1024, 0x0): semi-stub
0009:fixme:ole:NdrCorrelationFree (0x32c32c): stub
0009:fixme:olepicture:OLEPictureImpl_SaveAsFile (0x297f8c8)->(0x2b94190, 0, (nil)), hacked stub.
0009:fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
0009:fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4f92-6699-11cf-b70c-00aa0060d393}

Seeing it mentioned OLE, I installed the OLE dll via winetricks - still no difference. So the I looked at the last 2 lines - olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4f92-6699-11cf-b70c-00aa0060d393}. A post on the internet indicated this may be a problem with the version of oleaut32.dll, so I downloaded an older version of it and put it in the folder the program executes from - no difference. Deleted it from there in put in the Windows/System32 folder - no difference. I even installed doenet3 and an older directx since this is an older program. Still no difference.

There are other programs listed on the net that return that error. I think it varies by application. One I saw said it needed vbrun60, which I had already installed. But it also said it needed msxml6 so I installed that with winetricks - still no difference. I suspect it is a difference in a version of some Windows dll, etc., and the wine version. But I don't know, and I am finished for now. I'll let you know if I find something else.

[fargodwe]

Sorry for another reply but I can't figure out how to edit a post I already made. There are MANY dll's, ocx files, etc., in the readme in the unpacked folder with the installation file, and there is over 900 lines in that readme. I tried going through part oft it but it's a little beyond me how to know if they are present in wine. I therefore sent an email to the developers describing what you are trying to do and the error encountered asking for help. Just have to wait now to see if they answer.

[fargodwe]

Never received an email back from the developer yet. I have another post out regarding the ipicture "stuff". From what someone has replied back it is part of oleaut32.dll. I have tried changing that but still no go. I'll post again when I find out more.

[fargodwe]

Ok, I got the email back from the developer. They have had the same problem trying to run IFs in wine and have not been able to solve it. It must be something in wine. they want to know the steps if we do get this working in wine. The only solution at this time is to run it in a full-blown virtual machine. I'll let you know if/when this works.

[DarkShadow44]

@cjolley

We got it to work, also see https://bugs.winehq.org/show_bug.cgi?id=45212

1) Use a fresh 32bit WINEPREFIX
2) winetricks -q jet40
3) Get a 32bit dao360.dll from win7 or so (mine is version 03.60.9756.0), and put it into drive_c/Program Files/Common Files/Microsoft Shared/DAO/ - overwriting the already existing dll