Jump to content

This topic is 7365 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Let me start by saying I'm a novice with regard to IWP...

Anyone have any ideas why FM crashes with "This application has generated errors" every time I try to activate IWP for a database?

I have a large database that a client wants to install on several machines without spending $1500 on FM licenses, so I thought I would give IWP a look to see how much clean up I would have in my scripts. I fully expected to find a slew of incompatibilities, given that I haven't written a single script with web compatibility in mind. However, every time I try to turn web publishing on, FM crashes unceremoniously.

The crash happens every time I click the ok button on the IWP screen. Initially, I had Apache running on my machine, and so had to change the Port to 591 (as suggested by the FM docs). But I shut down Apache to see if that was causing the problem. No dice.

I opened my database in Admin, and told it to allow access to All Users, just to be sure that rights weren't a problem. Still no go.

I sure would like to be able to tell nmy client whether this will be a possibility for them, but so far, I can't tell.

  • 2 weeks later...
Posted

I am replying to my own original post to report on my latest results. I deleted my recent aggravated update...

After posting a second plea for assistance with setting up IWP, I started thinking about my problem, and decided that I must have done something that really upset IWP, since so many of you have been able to use the software. Consequently, I rooted around on my hard drive for about an hour looking for whatever Filemaker files had been set up recently. I found a couple of preferences files (web.prefs, and a second file that had an ips extension), and deleted them. When next I tried setting up IWP, it worked (well, except for the parts of my application that aren't web-compatible...).

As far as I can tell, I ran into trouble when I initially tried to set up IWP. Because I was running Apache Web server already on my machine, IWP forced me to change the port number, which I did, to an arbitrary number (82). From this point forward, IWP crashed every time I tried to change the settings (like setting the port to Filemaker's suggested, registered alternative of 591). Obviously, deleting the preferences files cleared up the problem.

When I set up IWP again, I had disabled most of my non-essential services (such as Apache, MySQL, etc.), so I do not know whether my problems occurred as a result of interactions with these services. I *do* know that when I rebooted and opened Filemaker the next time (when all my services were running again), IWP insisted that I change the port from 80 (which now conflicted with Apache) to another, and I entered the requisite 591, and it works.

So maybe this will help someone out there figure out what to avoid the next time around.

This topic is 7365 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.