@scottalanmiller said in AVImark support has stated that running virtual servers can result in a 40-50% data loss or complete destruction of your server.:

and we just left that as it was (having learned about it), that's establishing that that is official.

Bolded bit is the thing you are glossing over.

This entire thing is a rant by @CCWTech

No where in here is there proof that anyone, above the support tech at the vendor, has been made aware of anything.

At this point there is nothing but an unsubstantiated claim by @CCWTech the vendor knows what the support tech said. Yes, absolutely, if it is known and not corrected, this would be shit, but no one, in this thread, knows this.

Is this a shit ass vendor with a bad product? Maybe, hell probably even. But I won't take the word of anyone the just comes on here and rants without any proof.

Here it is

This is the error:
a8ab3c57-38bf-4d0f-ad9a-07476b021268-image.png

Check if the error is present by by visiting Help-> About Avimark.
ae3ca2f7-e09f-41a2-bc31-e7ef0e0c249e-image.png

If you confirm the error is showing follow the steps:

Close Avimark

Find the Avimark shortcut in the desktop, right click and open its properties.
6bf7334c-199b-45c6-baaa-a285a06a2ff2-image.png

In the target section add /regserver to the Avimark link and click ok to save the change.
e9c58755-192f-464c-8984-c3d587b96870-image.png

Right click on the Avimark shortcut and run it as an ADMINISTRATOR
a1e9393a-0e31-46e1-9dd4-f41b82d5123a-image.png

Let it run for a bit (1-2 min), nothing will appear to be happening but it really is.

Right click the shortcut again, go into properties and remove the added /regserver to the target field (returning the shortcut to the original state).

Open up Avimark again and the error should be gone and the machine will be printing again.

Oh Cool! Thanks Scott!

This is working on several machines now. But @romo reports that it is still hit or miss, it's not a reliable or permanent fix, but it more reliable than other attempts. It remains, as MS has stated, somewhat random.

If we look at net use, the table is clear and empty. But if we try to mount the AviMark share from the command line we get a 1219 error telling us that the share is already mounted with other credentials. So waiting for clearance to reboot, looks like the net use table is corrupted.

@scottalanmiller said in Error on Avimark Server: "fail to initialize the LT DLL":

@Dashrender said in Error on Avimark Server: "fail to initialize the LT DLL":

@scottalanmiller said in Error on Avimark Server: "fail to initialize the LT DLL":

@Dashrender said in Error on Avimark Server: "fail to initialize the LT DLL":

@scottalanmiller said in Error on Avimark Server: "fail to initialize the LT DLL":

So we don't have an answer yet, might take a while. But what we found that Active Directory was disconnecting because of a bad manual DNS entry. We've fixed that and are waiting to see if the issue recurs.

Do we assume there was DRM that was failing? lol

I'm not aware of any DRM. Is there something pointing to that that makes you assume that?

No - it was a simple guess as to what the program would want/need DNS for, assuming DNS is reason it was failing.

I assume it needs DNS for AD and it needs AD for SMB and needs SMB for the system files.

I just looked this stuff up - it's Vet software - for some reason I thought it was video editing software.