Distribution workflow tests pass once the fail. Windows Server 2019 V1809 OS 17763.2565

[grayman]

Thanks Wayne  for the quick reply .   I think we are good  issue is more just with the destination test from the web interface  which always fails on  second test.    Workflows appear to be ok , good to know regarding the  naming of the docs , typically  or scanned locations are temp and user move the scans out of the repository before they can reach that count . 

[WayneBDA312-ASP]

Good Morning

I figured it out.

The naming convention. If left at default scan naming it names the docs DOC001, DOC002 etc  when it hit DOC999  it will stop as it cant go over 999

I changed it to use the date and time for default naming and that eliminated the problem with DOC999 stopping any scans from entering the folder.

Kind Regards

Wayne

[grayman]

Hello ,  did you ever get this resolved . Having same issue   with c8170 .  One thing i noticed is that if you open a private browser tab  to the web interface and  do  a destination test it will work on first attempt and then  not on second .  Printer reboot was not required .  

Tested on  two  SMB shares both running on Windows Server 2019 Datacenter 10.0.17763

Thanks

[WayneBDA312-ASP]

Thanks for getting back to me Cheryl

I tried 2nd Lvel before I reached out here and as they did not have any suggestions that we have not already tried

Kind Regards

Wayne

[CherylO-Xerox]

Hi Wayne, 

Thank you for using the Support Forum. Sounds like you have tried everything already, so it would be a second level escalation: 1-800-821-2797 or 1-800-835-6100 

[WayneBDA312-ASP]

Hello 

I have never seen this issue. Scan distribution workflows pass destination test first time. We test same workflow a few seconds later and it fails.. we cant hit server no ping reponse. I reboot the Xerox and do a destination test and the workflow passes .. I test it again a few seconds later and it fails

I have attached scren shots and the firmware level

We have deleted and recreate scan workflow on the server as well as creating a new scan tempate on the server with same results. Rebooted server enabled SMB1/2 tried using  server host and IP for workflow destination 

has anyone seen this or any ideas?

We are going to try the scan to laptop with one techs laptop next 

Many thanks

Wayne