Community Forums
Page 1 of 2 12 LastLast
Results 1 to 5 of 6

Thread: Logging in FNMP 9.2

  1. #1
    Join Date
    Dec 2013
    Posts
    4

    Question Logging in FNMP 9.2

    We are currently running FNMP 9.2, and are having an issue importing the ARL. Support said to look in the Recognition.log file, but there are no log files on the server. Any ideas as to how to turn on logging? I've searched both drives on the server, but can't find any current log files. The only ones I see are over five years old.

  2. #2
    Join Date
    May 2010
    Location
    Melbourne, Australia
    Posts
    41
    The ARL update process should normally put its log file into the %TEMP% folder of the account that the process runs as. You can run the process manually by logging in to the FlexNet Manager Platform application server, and executing the following in a cmd shell window:

    Code:
    C:\Program Files (x86)\ManageSoft\DotNet\Bin\MgsImportRecogition.exe
    After doing this, check for a %TEMP%\Recogition.log file.

    Chris @ Flexera

  3. #3
    Join Date
    Dec 2013
    Posts
    4

    System processing for hours

    Okay, so I ran this command at 8:00 this morning, and now almost seven hours later it is still running. I found the Recognition log file, which I'll attach. Our FNMP system is crawling because this is running.
    Attached Files Attached Files

  4. #4
    Join Date
    May 2010
    Location
    Melbourne, Australia
    Posts
    41
    The ARL update process can run for a long time if the database is running in a memory or resource-constrained environment; for example, if the database is running on a virtual machine a reasonable amount of memory allocated. It's not usual for the system to run more slowly than usual while the ARL update is running - but if you are seeing that it would further suggest to me that the database server is perhaps under-spec'ed for memory and possibly CPU.

    Chris @ Flexera

  5. #5
    Join Date
    Jan 2018
    Location
    London
    Posts
    2
    Looks like the script stopped doing anything after about 20 minutes. Any change yet? Anything new in the log file?

    Is your SQL server running ok? I'd check that and retry the import. Probably a good idea to run at non-peak times.

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •