Allen Poole

What log information is useful for troubleshooting WebDirect crashes? My client's FMS 16 running on Windows is rock solid for FMP clients but its WebDirect process crashes occasionally, sometimes not for weeks and other times more often than daily, with a load of c. 20 occasional users. Sometimes a Windows log report like this Error 04/29/2019 8:31:13 AM FileMaker Server 16 701 Web Publishing Engine process has terminated abnormally. Error 10/29/2019 10:12:31 AM Application Error 1000 (100) Faulting application name: fmscwpc.exe, version: 16.0.5.501, time stamp: 0x5cdee983 Faulting module name: FMEngine.dll, version: 16.0.5.47008, time stamp: 0x5cdee806 Exception code: 0xc0000005 Fault offset: 0x0000000000040594 Faulting process id: 0x1260 Faulting application start time: 0x01d5800f16d9068f Faulting application path: C:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\cwpc\fmscwpc.exe Faulting module path: C:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\cwpc\FMEngine.dll Report Id: 98290031-3fe3-487c-b781-de36fdd6182b Faulting package full name: Faulting package-relative application ID: acknowledges the crash, but not always. FMS' log is similarly unhelpful: Tue Oct 29 10:12:31 EDT 2019 Server Events Error Web Publishing Engine process has terminated abnormally. I've asked my users to let me know what actions they take immediately prior to crashes, but they're not effective in providing this kind of detail. What tools and techniques do y'all recommend for ferreting out the cause(s) of WebDirect crashing?

Work-around I've found so far: deleting a CIM customer profile seems to delete its associated CIM payment profiles, allowing me to give the customer a new profile and then re-add card details corresponding to a (previous, now deleted) payment method with lost token.

If I use CCProfileCreatePayment to submit a credit card number and expiration date to Authorize.net and their token gets lost on my end, trying to re-submit the same card information returns an error saying that the card is a duplicate of an entry that already exists in the CIM... but doesn't give me the token for that entry such that I could run a charge against it, delete it, or update it. If I lose a token for a CIM record, how can I get it back or delete the CIM record?

But using Plastic can help make your practices PCI compliant. For example, if you use Authorize.net as your gateway, Plastic can submit payment card and ACH account numbers to Authorize.net's PCI-complient CIM database in exchange for a token, which is PCI-compliant to store in your database. Plastic then lets you run charges against these tokens, and Authorize.net looks up the corresponding account information in their CIM to complete each transaction.

I'll try next time I'm over there. What if I can, and what if I cannot? Thanks, Allen

Hi all - My client's using SuperContainer and FMP 11, and since I upgraded my workstation to Mac OS 10.10 I can't see any of his SuperContainer documents in the FileMaker UI (Webviewer) that still works for him and his users. SuperContainer asks me to authenticate as usual and accepts my credentials without objection, but afterward I can't see its data. I've tried upgrading my companion plugin to the latest version, but that made no change. Is anyone else having this problem, and has anyone found a solution? Thanks, and happy 2015, Allen

The setting: FMS 5.5 on Windows FMP 5, 5.5, 6 clients for 5-10 users on Windows Server and all clients appear to have adequate memory; network performance is strong. The problem: Sometimes, when a user views a layout that includes a portal showing join records in a file with a large number of records, FileMaker pops a "Sorting..." progress dialog, that counts down from a number in the thousands, then goes away. This is not surprising in some cases, since the portal shows records in a particular sort order, and there are a lot of join records, and over a network these things can take time. Here's the mystery: It doesn't happen all the time or for all users! Here's the pattern I've figured out so far: 1. A user can launch the database and browse records for hours without seeing the sorting dialog (or having to wait for it to finish). 2. After editing a record or creating a new join record, the sorting slowdown begins... even on the same records and layouts that had better performance in 1. above. 3. Another user can be looking at the same records on the same layouts at the same time, and not experience the sorting slowdowns. 4. Any user who's started experiencing the sorting slowdowns (which become chronic and sap performance enough to be a serious problem) can make them go away by quitting FileMaker and opening the database again. My client and I have been experimenting, yet we can't find a way to avoid these chronic "Sorting..." dialogs, aside from restarting FileMaker. Is this problem familiar to anyone? Does anyone know a work-around whereby we could avoid the chronic sorting and attendant dialogs? Thanks in advance, Allen