FileMaker Server - Could not allocate required memory

Questions about Wine on Linux
Locked
pquesinb
Newbie
Newbie
Posts: 4
Joined: Tue Jan 15, 2013 2:54 pm
Location: Maryland
Contact:

FileMaker Server - Could not allocate required memory

Post by pquesinb » Tue Jan 15, 2013 3:20 pm

Hi everyone,

I'm fairly new to Wine and I'm trying to run an old version of FileMaker Server with it but am getting a memory allocation error as follows:

fixme:advapi:RegisterEventSourceA ((null),"FileMaker Server"): stub
fixme:advapi:RegisterEventSourceW (L"",L"FileMaker Server"): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000001,(nil),0x0002,0x00000000,0x7e3776e4,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x40000001,(nil),0x0002,0x00000000,0x11e818,(nil)): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0xc000005b,(nil),0x0001,0x00000000,0x7e3776e4,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0xc000005b,(nil),0x0001,0x00000000,0x11e818,(nil)): stub
err:eventlog:ReportEventW L"FileMaker Server quitting! Could not allocate required memory at initialization. (1)"
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000002,(nil),0x0000,0x00000000,0x7e3778f0,(nil)): stub
fixme:advapi:DeregisterEventSource (0xcafe4242) stub
Starting up FileMaker Server. Please wait...

Version of Wine is 1.01 on CentOS 5.8. As a start, I tried compiling the latest stable version of Wine but get an error that my version of Flex is too old... I need Flex 2.5.33 or newer. The latest version of Flex for CentOS 5.8 is too old.

So I have a couple of questions:
Is it likely that I need a newer version of Wine to run this program or should I be able to get it to work with 1.01?
If it is likely to work with 1.01, what would be some things to look at or try?
If I do need a newer version, how can I get it on my system?

Many grateful thanks for any suggestions that might be offered.

Regards,

- Phil

User avatar
dimesio
Moderator
Moderator
Posts: 12898
Joined: Tue Mar 25, 2008 10:30 pm

Re: FileMaker Server - Could not allocate required memory

Post by dimesio » Tue Jan 15, 2013 4:00 pm

1.0.1 is over four years old and no longer supported. You need to upgrade. If your distro doesn't provide current Wine packages you will have to build it yourself.

pquesinb
Newbie
Newbie
Posts: 4
Joined: Tue Jan 15, 2013 2:54 pm
Location: Maryland
Contact:

Re: FileMaker Server - Could not allocate required memory

Post by pquesinb » Tue Jan 15, 2013 6:27 pm

Understood, and that's what I was trying to do. Any ideas where I can get updated source code for the required version of Flex?

Searching around, the only thing I was able to come across was a source RPM here:
http://download.fedora.redhat.com/pub/a ... c8.src.rpm

But apparently it's no longer there. If I can just locate an archive of the required source somewhere I should be fine.

- Phil


pquesinb
Newbie
Newbie
Posts: 4
Joined: Tue Jan 15, 2013 2:54 pm
Location: Maryland
Contact:

Re: FileMaker Server - Could not allocate required memory

Post by pquesinb » Thu Jan 17, 2013 4:40 pm

Thanks!

I managed to find suitable RPMs here before I got your reply, various binary RPMs are available as well as a source RPM:
http://pkgs.repoforge.org/flex/

After building flex and building or installing a few other dependencies, I managed to install 1.4.1 but there's quite a dance involved with the 32-bit dependencies on a 64-bit system. While I got much of it to work, there were a few supporting files/libraries which configure shows as still being needed even though it appeared that I was successful in installing some (not all) of them. Many of them are installed with later versions. This is the output from configure:

configure: XInput2 headers not found, the XInput 2 extension won't be supported.
configure: libxcomposite 32-bit development files not found, Xcomposite won't be supported.
configure: OpenCL 32-bit development files not found, OpenCL won't be supported.
configure: libhal 32-bit development files not found, no legacy dynamic device support.
configure: libgnutls 32-bit development files not found, no schannel support.
configure: libv4l 32-bit development files not found.
configure: liblcms 32-bit development files not found, Color Management won't be supported.
configure: gstreamer-0.10 base plugins 32-bit development files not found, gstreamer support disabled
configure: OSS sound system found but too old (OSSv4 needed), OSS won't be supported.
configure: libcapi20 32-bit development files not found, ISDN won't be supported.
configure: fontconfig 32-bit development files not found, fontconfig won't be supported.
configure: libgsm 32-bit development files not found, gsm 06.10 codec won't be supported.
configure: libtiff 32-bit development files not found, TIFF won't be supported.
configure: libmpg123 32-bit development files not found (or too old), mp3 codec won't be supported.
configure: libopenal 32-bit development files not found (or too old), OpenAL won't be supported.

configure: WARNING: No sound system was found. Windows applications will be silent.

configure: Finished. Do 'make' to compile Wine.



Despite the issues listed above, attempts to execute FileMaker Server are more successful after building/installing the newer version of Wine. I'm not quite sure what to make of the following output though, it appears to be running but with a few errors which may or may not be significant:

fixme:advapi:RegisterEventSourceA ((null),"FileMaker Server"): stub
fixme:advapi:RegisterEventSourceW (L"",L"FileMaker Server"): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000001,(nil),0x0002,0x00000000,0xace744,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x40000001,(nil),0x0002,0x00000000,0x11c820,(nil)): stub
fixme:netbios:Netbios NCBADDNAME: stub, returning success
fixme:netbios:Netbios NCBADDNAME: stub, returning success
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x4000006a,(nil),0x0001,0x00000000,0xace94c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x4000006a,(nil),0x0001,0x00000000,0x12a270,(nil)): stub
fixme:winsock:convert_socktype_w2u unhandled Windows socket type 5
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0xc0000020,(nil),0x0003,0x00000000,0xace6e8,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0xc0000020,(nil),0x0003,0x00000000,0x1ae518,(nil)): stub
err:eventlog:ReportEventW L"IPX/SPX"
err:eventlog:ReportEventW L"an unexpected error occurred."
err:eventlog:ReportEventW L"10022"
Usage of FileMaker Server:
FMSERVER OPEN [<path>] to open one or more databases
FMSERVER CLOSE [<path>] to close one or more open databases
FMSERVER PAUSE [<path>] to pause activity on one or more open databases
FMSERVER RESUME [<path>] to resume activity on one or more paused databases
FMSERVER START to start the Server (see -S option below)
FMSERVER STOP to stop the Server, closing all databases

where <path> is an optional file path (with wildcard) or directory path

CLOSE/PAUSE/RESUME without <path> will affect all open databases
OPEN without <path> opens databases in the Server folder (and one level down)

The following options may be used with CLOSE or STOP:
-M "text" sends the specified text to guests of database(s) being closed
-T # # is number of minutes after which guests will be disconnected

The following option may be used with START:
-S skip opening databases in Server folder (and one level down)
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000003,(nil),0x0001,0x00000000,0xace938,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x40000003,(nil),0x0001,0x00000000,0x1ae830,(nil)): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x4000005c,(nil),0x0001,0x00000000,0xace92c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x4000005c,(nil),0x0001,0x00000000,0x1ae830,(nil)): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000062,(nil),0x0001,0x00000000,0xace92c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x40000062,(nil),0x0001,0x00000000,0x1ae830,(nil)): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000069,(nil),0x0002,0x00000000,0xace92c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x40000069,(nil),0x0002,0x00000000,0x1ae830,(nil)): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000067,(nil),0x0001,0x00000000,0xace92c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x40000067,(nil),0x0001,0x00000000,0x1ae830,(nil)): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000063,(nil),0x0001,0x00000000,0xace91c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x40000063,(nil),0x0001,0x00000000,0x1ae830,(nil)): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000065,(nil),0x0001,0x00000000,0xace91c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x40000065,(nil),0x0001,0x00000000,0x1ae830,(nil)): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x4000005d,(nil),0x0001,0x00000000,0xace91c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x4000005d,(nil),0x0001,0x00000000,0x1ae830,(nil)): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000066,(nil),0x0001,0x00000000,0xace91c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x40000066,(nil),0x0001,0x00000000,0x1ae830,(nil)): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x4000006f,(nil),0x0001,0x00000000,0xace91c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x4000006f,(nil),0x0001,0x00000000,0x1ae830,(nil)): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x4000006e,(nil),0x0001,0x00000000,0xace91c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x4000006e,(nil),0x0001,0x00000000,0x1ae830,(nil)): stub
[root@Server1 FileMaker Server 5]# fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000005,(nil),0x0000,0x00000000,0x33fa50,(nil)): stub


The last error line which appears to be typed at the prompt appears a few seconds after the program exits.

So my dumb questions are:

1. Should I be concerned about the configure errors in this case? FileMaker Server runs in text mode, no graphics, no sound, etc.
2. Are the 'fixme' lines reporting serious errors, or are we just getting a full trace of things like attempts to open IPX/SPX networking which are not applicable now but apparently are included in this old version of FileMaker since it hails from the heady days of Novell Netware?

Thanks again, and my apologies for the silly questions.

- Phil

User avatar
dimesio
Moderator
Moderator
Posts: 12898
Joined: Tue Mar 25, 2008 10:30 pm

Re: FileMaker Server - Could not allocate required memory

Post by dimesio » Thu Jan 17, 2013 10:22 pm

If the app is working, don't worry about what's in the terminal.

Locked