Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies replies
    5
  • Subscribers subscribers
    4
  • Views views
    742
  • Users 0 members are here
  • +1 person also asked this people also asked this
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Asset Manager Web Service login error

jiwook

Hi, I'm Wook.

I need help.

My customer is using ITAM. Both the ITAM client version and WEB are in use.

Automated process manager crashes frequently. So I run it every now and then.

For some reason, I suddenly couldn't access the ITAM web.

I get up to the login screen, but when I try to log in, I get an error message asking me to validate the database.

The ITAM client connects normally. We are using weblogic.

16:37:36,684 INFO - com.peregrine.ac.ws.desc.WsCacheLoader - pre-loading services : Head/*
16:37:36,814 ERROR - com.hp.ov.ac.aop.AmWsThrowAdvice - Intercepted exception of type [com.peregrine.ac.AmException] AMException [12002] Exception [Error (12,002): Internal blob cache error (too many crc conflicts)
Error reading database description.
Validate the database with the administration tool..] thrown by target class [com.peregrine.ac.ws.axis.ACContextApi] and method [public abstract java.lang.String com.peregrine.ac.api.IAmApi.selectAQL(java.lang.String,java.lang.String,int,int,boolean,boolean) throws com.peregrine.ac.AmException] for the params of , SELECT SQLName FROM amFuncDomain WHERE seWebService = 2 ORDER BY SQLName, 0, 0, true, false
Error (12,002): Internal blob cache error (too many crc conflicts)
Error reading database description.
Validate the database with the administration tool.

I think it's because Automated Process Manager keeps shutting down, but I'm not sure. I even rebooted the server, but still the same situation.

Does anyone know what the reason might be?

Thank you.

  • 0

    There could be multiple reasons...the biggest one is to resolve reason why Automated Process Manager (APM) crashes frequently which could be due to same reason as to your supplied error (ie. too many crc conflicts).

    If you do not have an APM log file setup, then please do as this will capture all processing/error results.

    Using the Designer application, under Action menubar, perform a diagnostic/repair > Analyze Only for all options except 'Check validity of records' against all tables.  Have a log file generated for this option so you can review and resolve any potential issues/conflicts.

    When you are comfortable, and your DBA has performed a database backup, perform same task again but this time select Repair option.

    After the repair, you will want to Tag the web services (another action menubar option), use the Client application to execute action "Check definitions of the Web services", then Tag the web services a second time.

    Review the Administer guide for these tasks.

    The crc conflicts could be related with "lCrc" field which is on the following tables:  amAction, amImage, amSysConfig, amViewDef, amForm, amReport, amUserRight, amDocBlob

  • 0 in reply to 

    Thank you for answer.

    May I know what the lcrc field is?

  • 0 in reply to 

    That is the SQLName with Label being "CRC" and description "Cyclic redundancy check" and all controlled by AM background functionality.

  • Verified Answer

    +1  
    Hi,
    For the web client, you may cleanup the files under the folder mentioned in your web.xml file : 

    default is the AssetManager.DB.Name env-entry value is something like this:

    <env-entry-value>[MSSQL;AMDemo95en_11738;;;;itam;EIlGdUllzGMWLRwSlL+Q5g==;1;/tmp;1048576;AmApiDll='c:\data\9.50.11738\en/bin/aamapi95.dll';ExpandTypedLinks='|amDocument|amWfWorkItem|amHistory|amReconcProposal']</env-entry-value>
     
    The part of value "1;/tmp" is corresponding to the setting made in package.properties file of web service:
    # Whether the DB cache is enabled
    DB.cache.enabled=true
    # The cache directory
    DB.cache.dir=/tmp
     
    Find this part of setting in your web.xml of Web service, and go to that folder.
    With this error, normally it is very possible that the file extensions value in the folder has reached to 999. For example,0FD0AF1D.999. You can confirm on this in this folder. And delete all the xxxx.001-xxxx.999 files in this folder. Then start web service to see the issue is gone.
     
    [!] This has to be done on all web service servers if you have more than one web services.

    Hope this will help you out.

    -----------------------------------

    Boryana Kotseva

    Premium Support / Named Support Engineer [SMAX & Asset Manager]

  • 0 in reply to   

    The customer did it themselves without help, but I don't know because they didn't share the detailed solution.

    It seems to have been fixed by clearing the cache.

    It seems to be consistent with the guide you gave me.

    Thank you for your help.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.