![kofax vrs deactivate machine not available kofax vrs deactivate machine not available](https://s3.manualzz.com/store/data/023589888_1-1c10fe010ad0769c721e38afc8814e19-360x466.png)
What I believe is the issue is the fact that an exe called AppInit.exe has to run after a reboot. KdoLib: The database has not been configured.Please contact the Kofax Capture Admin Your Batch Catalog server or network may be down Now when I start any kofax app i get the message:Įrror loading User Profile COM oject: PFCaptur.dll Now me, I'd like to avoid a reboot since our deployment system (LANDesk) doesn't like em.
#Kofax vrs deactivate machine not available install#
I'm able to silently install the components of this app (via the setup.exe), but a manual install does some stuff after a reboot. Hmm, ok, I know it's been awhile since I posted this topic, but I'm still struggling with this package (just struggled with some other, more urgent stuff for awhile first )Īt the moment the situation is as follows:
![kofax vrs deactivate machine not available kofax vrs deactivate machine not available](https://support.ikansoftware.com/hc/en-us/article_attachments/202892845/ErrorsTab.jpg)
So my question is: has anyone succeeded in creating a package for this application, using as many of the "provided" MSI's as possible for it? I've looked in the package KB but no luck. The first two parts (VRS and SQLEXPRESS) are proving a bit eluseve though.
![kofax vrs deactivate machine not available kofax vrs deactivate machine not available](https://manula.r.sizr.io/large/user/10889/img/kofaxvrsconsole-scansettings.png)
So my plan now was to analyse the various existing msis, and install them as prerequisites, then capturing the "leftovers" for my package, trying to avoid as much junk as possible. I've tried the silent setup, but at one point i get an empty Windows warning window where I have to click OK( I suspect it's the VRS part) WIBU drivers (I'll go to and get an installer from there) Sentinel Protection Drivers (ok, it's an MSI, no prob) SQL EXPPRESS 2005 (ok, I'm sure i can get that installed, need to change the service (and server perhaps) name, but OK) Let me try to sketch the process so far.ġ) did an install capture with snapshots, opened the result, cried abit and decided to find another wayĢ) good thing I did because I found out parts of this install are actually MSIs (or equivalent), I have identified the following: I've ran into a package that's proving to be quite a challenge.