GN4 client applications crash

CONDITIONS

SOLUTION

STARTUP ISSUES: Any GN4 application may crash if you launch it during the transitory states of the GN4 server: rebooting, shutting down, resetting IIS, server software being upgraded, etc.

Wait few minutes and then retry.

INSTALLATION ISSUES: Any GN4 application may crash if the server or client installation is not complete, e.g. certain files are missing.

1.Download again all necessary files related to your version from the Tera Web repository and make sure the files are entire and not corrupted.

2.Understand well what has to be updated, having in mind that you must not install different versions/builds on server and on client.

3.When extracting zipped files, make sure GN4 is not running. On servers, make sure that related services are stopped (stop also IIS).

4.After extracting, make sure the dates of all extracted items correspond to the dates in zipped files.

5.Re-register all components that need registering and make sure it was successful.

INSTALLATION ISSUES: Any GN4 application may crash if the upgrade was performed on the client while not all GN4 applications were shut-down. Therefore, the upgrade was unable to extract all files (some files were in use).

Make sure GN4 is not running, and then re-extract files from zipped archive.

INSTALLATION ISSUES: Any GN4 application may crash if some components on server are not registered correctly.

Exit GN4, and re-register all components that need registering. See Register COM components.

CLICKONCE CACHE CORRUPTION ISSUE: A ClickOnce GN4 application may crash or be very slow or show empty pages if the client cache got corrupted.

See the cache paragraph in the Troubleshooting and FAQ for ClickOnce topic.

CONFIGURATION ISSUES: Ted4/Fred4 may crash at startup if they cannot access to the server volume because of wrong access permissions for the volume.

Note: EdAdmin4 can start correctly even if access to the volumes is denied.

See Ted4/Fred4 crash on startup because of access denied to a volume.

CONFIGURATION ISSUES: Ted4/Fred4 may crash at startup if users have no RefRead Content permission on the typography.

Set the View preset on the typography as the minimal permission.

LOCALIZATION ISSUES: Any GN4 application may crash if you're using a localized GN4 version, and there's  something wrong with localization.

Update the resources if required, and make sure they are ok. To test, remove the resource files from the directory, set the locale to US English, and then check if the application still crashes on the same point. If required, recompile the resources.

Any GN4 application may crash if the USERCONFIG.XML on client computer is corrupted

Delete the line, related to the connection that crashes client, and rebuild it. If that does not help, rename entire USERCONFIG.XML file and rebuild it. See Providing for automatic sign-in for instructions about USERCONFIG.XML file.

Fred4 may crash on launch when the Fred4_MruUserConfig for given user is corrupted.

Launch EdAdmin4, and then under Application Configuration, Client Applications, search for Fred4_MruUserConfig related to the specific user, and then spike it.

Ted4/Fred4 may crash if the list of fonts on the GN4 server and on the GN4 client is different, but the fonts cannot be installed on client computer.

The error message may appear:

System.InvalidOperationException: Error in XML document. ---> Microsoft.Web.Services3.Mime.XopDocumentException: WSE1622: The incoming message contains more than 64 MIME parts.  Refer to the messaging/mtom/maxMimeParts configuration section for adjustment.

  in Microsoft.Web.Services3.Mime.MimeReaderMimePartProvider.GetNextMimePart(MimeReader reader, Boolean throwIfExceedLimit)...

Locate the missing fonts and install them manually on the client.

Any GN4 application may crash if the 64-bit add-ins are loaded for 32-bit applications or vice versa.

Follow the recovery steps in Purge add-ins from the GN4 database.

Fred4 can crash with the following sequence: open the recover edition dialog, change the sorting of elements by clicking on a column, and crash occurred when you tried to recover an element.

Fixed in build 2106 (1.6 and 2.0).

Fred4 can crash with the following sequence: open a page and then design a picture placeholder with a caption frame. Drag and crop a wire image on the placeholder. Design body frame, and then select it together with picture and caption. Create a new article, enter the name and click OK.

Fixed in build 2111 (1.6 and 2.0).

EdAdmin4 can crash if you select many sections (Bug report GN4-2349  -  EdAdmin4: crash selecting a lot of sectionPage)

GN4 applications may crash after you've loaded the add-ins in the database.

The steps to recover from this situation are described in GN4 applications crash after add-ins are loaded in the database