David Blake Ricoh USA Sr. Solution Integrator

Customer reported having an issue printing a single page from a document in Fortis using MS IE. Can print through FireFox. Is there a known issue with MS IE regarding printing?

https://www.docuware.com/sites/default/files/forums-images/Print%20Single%20Page%20Error_0.jpg

Following up if there was any movement or progress regarding this issue or the ticket.

A customer wrote the following experience:

"We noticed some slowness in the webflow processes (during testing). At the time we wrote it off to people accessing it (Webflow) remotely.
It is still continuing to be slow. It’s more noticeable at the approval point – where the user clicks "Approved" to advance the invoice. It took one user almost 20 minutes to get through 4 invoices."
 

Five months ago we've upgraded to Fortis 2.8. Webflow was newly installed and has only gone to production for the first time last month. Fortis sits on a Windows 2012 R2 box with 4GB RAM. There are additional separate servers for IIS and Inflo with the same Windows configuration.

Any recommendations to hasten the actions of Webflow?

Fortis FormIt has often been failing. It is the latest version available, version 5.1 on a Windows 2012 R2 server.

We've started with setting Recovery for the Forms Service to Restart Service. When that didn't fix, we've set Recovery to Restart Server.

This has been a good patch for at least a month. Since then, they are now seeing failures with the operating system, and I'm sure reviewing the logs showed IT that there has been an issue with the Forms Service.

The question is what is causing this failure. Will be reviewing logs extensively. Here's a few of the error logs we've compilied:

Log Name: Application
Source: Application Error
Date: 3/29/2016 7:28:38 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: recordsapp.acc.austincc.edu
Description:
Faulting application name: FormsService.exe, version: 6.8.0.0, time
stamp: 0x56d45adb
Faulting module name: ntdll.dll, version: 6.3.9600.18202, time stamp:
0x569e72c5
Exception code: 0xc0000006
Fault offset: 0x0001a5c7
Faulting process id: 0x49c
Faulting application start time: 0x01d188ff460b69ab
Faulting application path: C:\Program Files (x86)\Fortis
Forms\FormsService.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: c31aa8b9-f5a9-11e5-811a-00505695754b
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-03-29T12:28:38.000000000Z" />
<EventRecordID>32124</EventRecordID>
<Channel>Application</Channel>
<Computer>recordsapp.acc.austincc.edu</Computer>
<Security />
</System>
<EventData>
<Data>FormsService.exe</Data>
<Data>6.8.0.0</Data>
<Data>56d45adb</Data>
<Data>ntdll.dll</Data>
<Data>6.3.9600.18202</Data>
<Data>569e72c5</Data>
<Data>c0000006</Data>
<Data>0001a5c7</Data>
<Data>49c</Data>
<Data>01d188ff460b69ab</Data>
<Data>C:\Program Files (x86)\Fortis Forms\FormsService.exe</Data>
<Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
<Data>c31aa8b9-f5a9-11e5-811a-00505695754b</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 3/29/2016 7:28:38 AM
Event ID: 1005
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: recordsapp.acc.austincc.edu
Description:
Windows cannot access the file for one of the following reasons: there
is a problem with the network connection, the disk that the file is
stored on, or the storage drivers installed on this computer; or the
disk is missing. Windows closed the program FormsService because of this
error.

Program: FormsService
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that
corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that
there is not a problem with the network and that the server can be
contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM,
verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK,
click Start, click Run, type CMD, and then click OK. At the command
prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not,
the disk might be damaged. If it is a hard disk, contact your
administrator or computer hardware vendor for further assistance.

Additional Data
Error value: C0000034
Disk type: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="49152">1005</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-03-29T12:28:38.000000000Z" />
<EventRecordID>32125</EventRecordID>
<Channel>Application</Channel>
<Computer>recordsapp.acc.austincc.edu</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>FormsService</Data>
<Data>C0000034</Data>
<Data>0</Data>
</EventData>
</Event>

Log Name: System
Source: Service Control Manager
Date: 3/29/2016 7:29:00 AM
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: recordsapp.acc.austincc.edu
Description:
The Forms Service service terminated unexpectedly. It has done this 1
time(s). The following corrective action will be taken in 60000
milliseconds: Reboot the machine.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager"
Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service
Control Manager" />
<EventID Qualifiers="49152">7031</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2016-03-29T12:29:00.021575000Z" />
<EventRecordID>55306</EventRecordID>
<Correlation />
<Execution ProcessID="512" ThreadID="2504" />
<Channel>System</Channel>
<Computer>recordsapp.acc.austincc.edu</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">Forms Service</Data>
<Data Name="param2">1</Data>
<Data Name="param3">60000</Data>
<Data Name="param4">2</Data>
<Data Name="param5">Reboot the machine</Data>

<Binary>46006F0072006D007300200053006500720076006900630065000000</Binary>
</EventData>
</Event>

Existing customer, all workstations work but one, where the thick client will open, attempt to open the database, and it fails to open the database with an error: Data source name not found and no default driver specified.

Uninstalled Fortis client and reinstalled. No difference.

Workstation is a Windows 7 OS.

Path statement: C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files\Dell\Dell Data Protection\Access\Advanced\Wave\Gemalto\Access Client\v5\;C:\Program Files (x86)\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;C:\Program Files\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Common Files\Sage SBD\;;;;\\fortisappa\Imaging\Fortis\;\\fortisappa\Imaging\Fortis\Viewers

https://www.docuware.com/sites/default/files/forums-images/2016-02-02%2016_15_52-Fortis%20Error%20DB.docx%20-%20Microsoft%20Word.jpg