SERP on WINDOWS machine
Mārcis Krūmiņš
11-26-19
Hi!

Version: STDERP_8.5-2019-09-15-1019

I try to install SERP server on the Windows 2012R2 machine.
After installation, I can't connect with SERP client. I get error msg "Server not responding on that IP and port". SERP server is running on port 1200 and Client is on the same machine, but I can't connect to the server. (I tried to connect with IP 127.0.0.1 and port 1200) Server is with demo data.
On this windows server is Windows Firewall, I allowed Inbound TCP 1200

hansa.log:
2019-11-26 13:48:08 Windows Service version
2019-11-26 13:48:08 Starting application...
2019-11-26 13:48:08 *** running with new mail receiving and parsing ***
2019-11-26 13:48:08 *** using a freelist to keep track of free space ***
2019-11-26 13:48:08 Database ID changed from: 00000000000000000000000000000000 to: A5A4EB00465566DC1125DB1793C65383
2019-11-26 13:48:08 Database ID changed from: A5A4EB00465566DC1125DB1793C65383 to: B7E831AD9DDD715C4AA0A97E529E3407

2019-11-26 13:48:08 Duration in seconds: 0

2019-11-26 13:48:08 File Imported GBR/DBDEF.TXT
2019-11-26 13:48:08 FIREWALL: Add failed: 80070005
2019-11-26 13:48:08 Listening on port: 1200 (Clients)
2019-11-26 13:48:15 Listening on port: 1080 (HTTP)
2019-11-26 13:48:15 Importing text file: GBR-Sample.TXT
2019-11-26 13:48:22 Duration in seconds: 6
2019-11-26 13:48:22 File Imported GBR-Sample.TXT

2019-11-26 13:48:23 Server process running

2019-11-26 13:48:23 8.5 2019-09-15 (build 85321019)
2019-11-26 13:48:23 Close database

2019-11-26 13:48:23 Quitting application...


parameters.txt
--port 1200
--webport 1080


"2019-11-26 13:48:08 FIREWALL: Add failed: 80070005"
Question:
What is that number that SERP wants to add to the firewall? What does this error message mean?




Omar Dottin
11-27-19
Hi Marcis! The message

"2019-11-26 13:48:08 FIREWALL: Add failed: 80070005"


is the Standard ERP server attempting to configure the Windows Firewall to allow communication on the ports it is configured to listen to.

There can be any number of reasons for it failing. Reasons could be (Not limited to this list): Server running with insufficient permissions, Firewall not available etc.

Please investigate your Windows event viewer. If you have further questions, please let us know.

Best Regards,
Omar
HW Support
Swati D.
12-3-19
Hi Marcis

Has your problem been resolved? Or do you need further assistance?


Swati
HW Support
Mārcis Krūmiņš
12-3-19
Hi!

We didn't solve the problem. We decided not to spend more time on this issue.
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Back to the list
Latest Posts
Paul Timms
I've found an issue which I'm trying to find the best way to resolve. An integrated proof of delivery system sends two pieces of data to the SERP API, in two separate calls - let's c...
17:59 20 Feb 2026
Andis Blicāns, Grasko
There are some topics in this Q&A related to this question, but none of them is about Idle users - Concurrent or Named. If timeout minutes are specified in Optional Features, then all idle users are...
15:53 18 Feb 2026