46xxx Files created and left behind in the application directory

• Related Articles

• Empty 46xxxx files created in the license directory

  They might be driver communication files The NT Driver uses files to communicate if it can't use a more direct method.   This situation can be caused by - older driver/ngn - security settings - drive share networking on a slow or unreliable ...

• Controlling where SLOG.txt is created.

  I’ve discovered that I can overcome this problem in the following way: I temporarily change the current directory,  prior to the call to InitCrypkey, to our app’s ProgramData folder. If I change it back again immediately after InitCrypkey then it ...

• RQ and AN files or _RQ and _AN

  AN or _an files would indicate that an older service is installed as well indicates that the User account running the application or share doesn’t have full permissions. The RQ or _rq files you speak of are usually generated by the System account not ...

• Debugging CEC and CES files in Enterprise client and server scenario

  We can turn on error logging in local mode in any app, by including ces (causes the ngn to make slog.txt) and cec (causes app to make log.txt) files in the directory, with information in them the same as the attached example ces and cec. This is a ...

• Redirection to Program Data Hash path when installed under Program Files

  There is a new function in the Client Library to find that (it's been added to CRYPKEY.H).  First he has a full path to where he expects the .KEY file. Then he passes that as an argument to CKResolveVistaPath() which returns a pointer to the true ...