Jump to content

Search the Community

Showing results for tags 'hasp error'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • W4
    • W4 - Forensic Triage
    • Wishlist Forum W4
  • Intella
    • Intella 10, 100, 250, Pro and TEAM
    • Wishlist Forum Intella
  • Intella Connect
    • Intella Connect/Node
    • Wishlist Forum Connect
  • Talking Tech with Vound
    • Webinars

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. Hello There, Last night I started to update my NODE from Connect 2.2.2 to 2.3 version. Immediately after the instalation I received the error 33 - Unable to Access HASP KEY and I notice that the LED from the USB key was off. In order to fix that I used the commands >haspdinst -r then >haspdinst –purge and finally >haspdinst –I from the Version 2.2.2 in order to restore hasp drivers. After that the USB key led trun on again. Because of that I'm still currently using the 2.2.2 version, and I'm not sure if it's a good idea using the new version with old driver
  2. Introduction: This post provides information in regards to troubleshooting issues with Intella and Connect. The information is split into categories to make navigation to the topic, which matches your issue, easier to find. You may have been pointed to this post from the Vound support team. If that is the case, they likely require some information from your Intella/Connect case, or your system. Use this checklist to gather the information required, then provide it to the support team. 1. Intella log files & Exception reports Case logs: Each Intella case has its own set of lo
×
×
  • Create New...