Page 1 of 1

Problems using Commandline-Interface (thin client)

Posted: Tue Oct 04, 2011 11:00 am
by byte
We use a standart Client/Server Setup an all works fine on normal use by Client. (Sign, Send, Get Demo AppNo, etc). But when i try to use the Commandline-Interface i get an Error like this. (from PMSResponse.xml)

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE OLF_2_PMS_response SYSTEM "OLF_2_PMS_response.dtd">
<OLF_2_PMS_response mode="demo" language="de" result="failure">
    <return_values>
        <return_value error_ID="36">Verbindung zum Server verloren. Bitte schliessen und neu starten.</return_value>
    </return_values>
  </OLF_2_PMS_response>
Help says "Network Problem", test Connection. But normal Client use works fine, and tests with telnet says Ports are ok. Only the old -xml Parameter works.

Here is the (simplest) Commandline i try. (Other Variants with full Pathname etc. will produce the same result.) And from Commandline i get no Feedback and errorcode 0. Just PMSResponse.xml changes and shows error 36.

Code: Select all

OLFClient.exe -import "-Filename=G0002EP_0.zip" -Username=Administrator -Password= -Language=DE -ImportState=ready_to_sign
ProcessExplorer show me some activity for OLFClient.exe. Programm seems to be called correct. Access to File G0002EP_0.zip works (Read). But the only Networkactivity is local, and Programm ends by

Code: Select all

11:39:06,4683159	OLFClient.exe	4296	Load Image	C:\WINDOWS\system32\wshtcpip.dll	SUCCESS	Image Base: 0x719f0000, Image Size: 0x8000
11:39:06,4686712	OLFClient.exe	4296	QueryOpen	C:\WINDOWS\system32\mswsock.dll	SUCCESS	CreationTime: 14.09.2007 20:44:28, LastAccessTime: 04.10.2011 11:39:06, LastWriteTime: 20.06.2008 18:02:46, ChangeTime: 04.07.2011 08:44:36, AllocationSize: 249.856, EndOfFile: 247.296, FileAttributes: A
11:39:06,4687109	OLFClient.exe	4296	Thread Create		SUCCESS	Thread ID: 4664
11:39:06,8849414	OLFClient.exe	4296	TCP Reconnect	localhost:2116 -> localhost:kerberos	SUCCESS	Length: 0
11:39:07,4318046	OLFClient.exe	4296	TCP Reconnect	localhost:2116 -> localhost:kerberos	SUCCESS	Length: 0
11:39:07,4318545	OLFClient.exe	4296	TCP Disconnect	localhost:2116 -> localhost:kerberos	SUCCESS	Length: 0
11:39:08,4797663	OLFClient.exe	4296	CreateFile	C:\WINDOWS\system32\drivers\etc\protocol	SUCCESS	Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened
11:39:08,4801443	OLFClient.exe	4296	ReadFile	C:\WINDOWS\system32\drivers\etc\protocol	SUCCESS	Offset: 0, Length: 841
11:39:08,4803121	OLFClient.exe	4296	CloseFile	C:\WINDOWS\system32\drivers\etc\protocol	SUCCESS	
11:39:08,9630316	OLFClient.exe	4296	TCP Reconnect	localhost:2117 -> localhost:kerberos	SUCCESS	Length: 0
11:39:09,5098953	OLFClient.exe	4296	TCP Reconnect	localhost:2117 -> localhost:kerberos	SUCCESS	Length: 0
11:39:09,5099477	OLFClient.exe	4296	TCP Disconnect	localhost:2117 -> localhost:kerberos	SUCCESS	Length: 0
11:39:10,5424568	OLFClient.exe	4296	CreateFile	C:\WINDOWS\system32\drivers\etc\protocol	SUCCESS	Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened
11:39:10,5428264	OLFClient.exe	4296	ReadFile	C:\WINDOWS\system32\drivers\etc\protocol	SUCCESS	Offset: 0, Length: 841
11:39:10,5435934	OLFClient.exe	4296	CloseFile	C:\WINDOWS\system32\drivers\etc\protocol	SUCCESS	
11:39:11,0411175	OLFClient.exe	4296	TCP Reconnect	localhost:2118 -> localhost:kerberos	SUCCESS	Length: 0
11:39:11,4786073	OLFClient.exe	4296	TCP Reconnect	localhost:2118 -> localhost:kerberos	SUCCESS	Length: 0
11:39:11,4786457	OLFClient.exe	4296	TCP Disconnect	localhost:2118 -> localhost:kerberos	SUCCESS	Length: 0
11:39:12,5264837	OLFClient.exe	4296	CreateFile	C:\WINDOWS\system32\drivers\etc\protocol	SUCCESS	Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened
11:39:12,5268292	OLFClient.exe	4296	ReadFile	C:\WINDOWS\system32\drivers\etc\protocol	SUCCESS	Offset: 0, Length: 841
11:39:12,5269873	OLFClient.exe	4296	CloseFile	C:\WINDOWS\system32\drivers\etc\protocol	SUCCESS	
11:39:13,0098342	OLFClient.exe	4296	TCP Reconnect	localhost:2119 -> localhost:kerberos	SUCCESS	Length: 0
11:39:13,5566979	OLFClient.exe	4296	TCP Reconnect	localhost:2119 -> localhost:kerberos	SUCCESS	Length: 0
11:39:13,5567449	OLFClient.exe	4296	TCP Disconnect	localhost:2119 -> localhost:kerberos	SUCCESS	Length: 0
11:39:14,6046004	OLFClient.exe	4296	CreateFile	C:\WINDOWS\system32\drivers\etc\protocol	SUCCESS	Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened
11:39:14,6049744	OLFClient.exe	4296	ReadFile	C:\WINDOWS\system32\drivers\etc\protocol	SUCCESS	Offset: 0, Length: 841
11:39:14,6051477	OLFClient.exe	4296	CloseFile	C:\WINDOWS\system32\drivers\etc\protocol	SUCCESS	
11:39:14,9785499	OLFClient.exe	4296	TCP Reconnect	localhost:2120 -> localhost:kerberos	SUCCESS	Length: 0
11:39:15,5254148	OLFClient.exe	4296	TCP Reconnect	localhost:2120 -> localhost:kerberos	SUCCESS	Length: 0
11:39:15,5254642	OLFClient.exe	4296	TCP Disconnect	localhost:2120 -> localhost:kerberos	SUCCESS	Length: 0
11:39:15,5573781	OLFClient.exe	4296	CreateFile	C:\Programme\EPO_OLF5-TC\PMSResponse.xml	SUCCESS	Desired Access: Generic Write, Read Attributes, Disposition: OverwriteIf, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, AllocationSize: 0, OpenResult: Overwritten
11:39:15,5575159	OLFClient.exe	4296	CreateFile	C:\Programme\EPO_OLF5-TC	SUCCESS	Desired Access: Synchronize, Disposition: Open, Options: Directory, Synchronous IO Non-Alert, Open For Backup, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened
11:39:15,5575872	OLFClient.exe	4296	CloseFile	C:\Programme\EPO_OLF5-TC	SUCCESS	
11:39:15,5578123	OLFClient.exe	4296	WriteFile	C:\Programme\EPO_OLF5-TC\PMSResponse.xml	SUCCESS	Offset: 0, Length: 128
11:39:15,5579018	OLFClient.exe	4296	WriteFile	C:\Programme\EPO_OLF5-TC\PMSResponse.xml	SUCCESS	Offset: 128, Length: 128
11:39:15,5579437	OLFClient.exe	4296	WriteFile	C:\Programme\EPO_OLF5-TC\PMSResponse.xml	SUCCESS	Offset: 256, Length: 98
11:39:15,5579733	OLFClient.exe	4296	CloseFile	C:\Programme\EPO_OLF5-TC\PMSResponse.xml	SUCCESS	
11:39:15,6024278	OLFClient.exe	4296	QueryOpen	C:\WINDOWS\system32\msctf.dll	SUCCESS	CreationTime: 14.09.2007 20:45:11, LastAccessTime: 04.10.2011 11:39:06, LastWriteTime: 14.04.2008 07:52:18, ChangeTime: 23.06.2010 13:42:31, AllocationSize: 299.008, EndOfFile: 297.984, FileAttributes: A
11:39:15,6026545	OLFClient.exe	4296	QueryOpen	C:\WINDOWS\system32\msctf.dll	SUCCESS	CreationTime: 14.09.2007 20:45:11, LastAccessTime: 04.10.2011 11:39:06, LastWriteTime: 14.04.2008 07:52:18, ChangeTime: 23.06.2010 13:42:31, AllocationSize: 299.008, EndOfFile: 297.984, FileAttributes: A
11:39:15,6028413	OLFClient.exe	4296	Thread Exit		SUCCESS	Thread ID: 4664, User Time: 0.0000000, Kernel Time: 0.0000000
11:39:15,6036606	OLFClient.exe	4296	Thread Exit		SUCCESS	Thread ID: 3676, User Time: 0.0000000, Kernel Time: 0.0156250
11:39:15,6102050	OLFClient.exe	4296	Thread Exit		SUCCESS	Thread ID: 4592, User Time: 0.0937500, Kernel Time: 0.1718750
11:39:15,6107889	OLFClient.exe	4296	Process Exit		SUCCESS	Exit Status: 0, User Time: 0.1093750 seconds, Kernel Time: 0.1406250 seconds, Private Bytes: 4.345.856, Peak Private Bytes: 7.000.064, Working Set: 8.626.176, Peak Working Set: 11.309.056
11:39:15,6108024	OLFClient.exe	4296	CloseFile	C:\Programme\EPO_OLF5-TC	SUCCESS	
11:39:15,6109120	OLFClient.exe	4296	CloseFile	C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202	SUCCESS	
Questitions
* What could be wrong?
* Thera are other ways to Debug oder find Errors like PMSResponse.xml?

Re: Problems using Commandline-Interface (thin client)

Posted: Tue Oct 04, 2011 2:26 pm
by byte
When i use the Commandline-Interface, do i need to activate the PMS Interface ("Tools" - "Preferences" - "System Preferences") and run a Smartcard on the Server? PMS is enabeld on my Server, but the Smartcard are used on the Client. The Tech.Documents are ambiguous in this Case.

But when i use the PMS and i have to run SC on server, how i can differ the persons (Secretary, Attorney, etc)???

Re: Problems using Commandline-Interface (thin client)

Posted: Wed Oct 05, 2011 9:59 am
by D. Van Haken
Dear byte,

First of all, ensure that user management is enabled in Production and in Demo.
Filemanager --> Tools --> Preferences --> System preferences (General) (2x, when logged on as Administrator in Production and Demo)

To be able to use the PMS interface you have to configure the client when logged on as an Administrator in Production.
Filemanager --> Tools --> Preferences --> System preferences

- Enable the PMS gateway in the PMS Gateway Interface panel, select Smart card.
Input the Pin for the Smart that you would like to use when signing/sending via the PMS Gateway. If you only import the application in draft then the smart card will not be used (leave the pincode blank).
- Make sure that the port used (by default 88) is available to the EPO Online Filing client and not blocked by firewall (normally it should be, it is also used for the help pages, hence if you are able to use the help in the Filemanager then it is available).

Please also check that you EPO Online filing client is installed in Client/server. If installed in Stand alone then the interface will only respond when the client is running. When no EPO online filing client is running but it is installed as Client/server (even if both are on the same machine) then all services should be running (check with the Servermanager --> Services).

Please contact support@epo.org if you require further assistance.

Re: Problems using Commandline-Interface (thin client)

Posted: Wed Oct 05, 2011 10:50 am
by byte
My Setup/Status
Client(s) : Windows XP, newest OLF Client as Standalone, Smardcards
Server : Windows 7 Enterprise, Serverinstallation (without Cardreader)
Settings : See below, UM enabeld, Folder enabeld, PMS enabeld, Smartcard, etc.
Status : OLF Client to Server works fine, Smartcard & Client do his jop (sigh&send), Server to EPO works fine. Demoapplication works and application number/pdf comes back.
First of all, ensure that user management is enabled in Production and in Demo.
check
Enable the PMS gateway in the PMS Gateway Interface panel, select Smart card.
check. All settings where like discribed in TechDoc.
Make sure that the port used (by default 88) is available to the EPO Online Filing client and not blocked by firewall
check. Help is available.
Please also check that you EPO Online filing client is installed in Client/server.

That's confusing me. I have to install Client/Server on Client to use PMS/Commandline?!?!
If installed in Stand alone then the interface will only respond when the client is running.
Testet this, works not for me. Same error occurs with runnig Client.