How do I resolve error -1032 "Could not create log file" error for Nearest Web?

Summary

While attempting to troubleshoot potential problems with nearest for the web, you may find that it is useful to setup kernel logging. While configuring the product to carry out the kernel logging, you may find that while accessing the sample pages you are confronted with error -1032 – Could not Create Log File.

Symptoms:

For troubleshooting assistance, you may have activated the nearest for the web kernel logging feature, in order to help you, or QAS support staff in determining the cause of a particular issue. In doing so, you will have added lines similar to the ones below into your nearest.ini file:

LogErrors=Yes

LogFile=logfile.log

LogTrace=-1

After doing this, you may wish to carry out a nearest lookup using our asp sample pages, in order to re-create any issue that you may be experiencing. In doing so, the sample pages may return error -1032 “Could not create log file” (see screenshot below):

Solution

1. Locate Your Configuration File

Locate the nearest.ini file, in which you made changes to in order to activate the kernel logging. By default, this file will be located in C:\program files\qas\nearweb.362 for nearest for the web version 3.62 and C:\program files\qas\nearweb.350 for nearest for the web version 3.50.

2. Edit the Kernel Logging Lines

Locate the lines that were added to the nearest.ini file in order to setup the kernel logging (see above). You will need to edit the LogFile= line, in order that the file name that it points to includes the absolute path to the location in which you wish the log file to be created. So, for example, if you wished the log file to be created in the installation folder of your nearest for the web 3.62 products, the line may look like this:

LogFile=C:\program files\qas\nearweb.362\logfile.log

3. Try the Sample Pages again

Save the changes that you made to the nearest.ini file, and attempt to carry out a new nearest lookup, using the asp sample pages. You should now find that the error is resolved, and the log file is now created.

Please Note:

If you are using the jsp sample pages, and are attempting to setup logging, you will not receive an error informing you that the log file could not be created, but you will still need to ensure that an absolute path is specified within the nearest.ini file to the log file as in point (2) above.

Related links

Experian QAS Support API & Kernel Logging