Forum - export never finishes in 8.5 2020-01-07 (build 85330517)

export never finishes in 8.5 2020-01-07 (build 85330517)

Aldevinas Katkus

2-5-20

Linux server + Windows Clients
Windows server+ Windows Clients

If System>>optional features>>Performance>>Parallel reports<>OFF then following problems occur:
Maintenances don't run (e.g.,SL>>Create Interest Invoices does not create any invoices)
Exports never finish, e.g., NL>>Exports>>Tag/Object Balances, Accumulated Monthly P/L.
The file size is zero bytes and if we try to open it, we get the message telling the file is being used by another process.

This happens for at least 3 customers (all of them with HALs).
We cannot replicate this in demo.

Server log shows:
2020-02-05 15:09:27 (1) VK MAINTDEBUG: gp->gReportParaType!=kReportParallelityNone and ParaReportExists()
2020-02-05 15:09:27 (1) VK bg hal running is 1
2020-02-05 15:09:27 (1) VK -- process list start --
2020-02-05 15:09:27 (1) VK process id: 25 type S3
2020-02-05 15:09:27 (1) VK -- process list end --
... (same log lines are being repeated)

Any ideas

If we turn OFF Parallel reports, then Exports and maintenances work, however, only one report can be run at a time which is not acceptable in multi user environment.

The only

Björn Schwab

2-5-20

Have had same problem on Linux server
You have to make sure that the file owner is the same as running the process.

Customer had the hansa.hdb to be owned by root and the exe to be owned by hansasrvuser.

Clients could not create files.

Aldevinas Katkus

2-5-20

There is no difference between linux and windows servers. The point is, if we turn off parallel reports, then everything is fine with exports.

Bror-Erik Kotiranta

2-7-20

Hello,

so you are saying that

a) pararell reports are off

and when you then run things it gets maintenance debug. And if

b) its on

then all is good.

The problem is that maintenances etc are run on main thread, so if you only have one thread to do all things on, then this happens. So best to have multithread on. Or did i understand your problem wrong?
Br, Bror-Erik

Aldevinas Katkus

2-10-20

If we have multithread on, then it is not possible to export and run maintenances.

Bror-Erik Kotiranta

2-12-20

Ok, so you have multithread on - then it should be possible. you could try and add
system>settings>optional features>not supported > tick update web calls during reports

So everything that is not with hal works and those that you run with hal does not ?

Aldevinas Katkus

2-12-20

All customers with hals, including ourselves, which were upgraded to 8.5 2020-01-07 (build 85330517) experience the same problem, 8.5 2019-11-26 (build 85330317)did not have any problems.
If we turn multithreads off, then it is not possible to run reports in a multi user environment (only one report at a time?), if we turn on, then it is not possible to run exports and maintenances.
We already have "updating web calls while running reports" switched ON.
Previously we had 8.5 2019-11-26 (build 85330317) and did not experience problems with the same hals.

Bror-Erik Kotiranta

2-12-20

Interesting, really interesting. Are you able to report a bug on this + when you do, you need to attach sample halcust so we can see what is the problem here.
The first time I hear about an issue like this and a lot of customers with halcust have updated so. When you have reported bug + attached sample halcust please be in contact so we can have a look

Aldevinas Katkus

2-13-20

Our client and ourselves switched ON parallel reports and after restarting the server, everything started to work magically. One more client will switch parallel reports ON and restart the server. We will see if the magic happens again.

Maricelle B.

2-14-20

Hi Aldevinas,

Can we close this forum post for now?

Regards,

Maricelle

Aldevinas Katkus

2-14-20

Actually, today it does work again, so there is no solution yet. Yesterday a company with more than 10 users worked normally, but today it does not work again. They have windows 10.

I watched the customer via remote:
Customer got the enabler, then immediately tried to export the NL>>exports>>accumulated PL and it worked. After half a minute he could do the same export.

There are a lot of these in the server log.
2020-02-14 11:48:22 /THREAD(5) Error: Failed registering upload job
2020-02-14 11:48:35 /THREAD(5) *** Uploading backup D:\Backup\TB.TXT to cloud storage ***

client log:
2020-02-14 11:54:05 *** Using Clock Replacement ***
2020-02-14 11:54:05 *** using a freelist to keep track of free space ***
2020-02-14 11:54:05 enabler flag 2 set by using PACKFIELDMATRIX in halcust\Import70to81.hal:497
2020-02-14 11:54:06 Database ID is: 8B176FEBCF6B342E8F15B55CCEC63953
2020-02-14 11:54:06 aiting for HAL threads to finish connecting to server failed to setup connect
2020-02-14 11:54:06 connecting to server C5F9AD6B-586F4267-CED847CC-A82F177F-EBCAC167@10.20.205.15
2020-02-14 11:54:08 8.5 2020-01-07 (build 85330517)

...

Aldevinas Katkus

2-14-20

One more note. Today users tried to do exports (bank payments file) many times, and only one time the export was successful

Aldevinas Katkus

2-14-20

Created byAldevinas Katkus11:02 14 Feb 2020

Sorry, typo error, it DOES NOT work.

Aldevinas Katkus

2-17-20

We have 2 confirmed cases where renaming TB.TXT (without restarting the server) helped to solve exports problem. Still, we need to gather some more statistics on this.

Bror-Erik Kotiranta

2-17-20

Hello,

aa - yes. that upload bug was fixed in the version+builds below

8.5 2020-01-07 build 521 -> 523
Able to update to this one and test again?

Aldevinas Katkus

2-17-20

Just updated one client with build 524. Will see what happens.
One more note: I could still see the same errors "Error: Failed registering upload job" and at that moment server was not responding

Michael W.

2-18-20

Hi

Please can you test build 523? Build 524 will resolve the problem for customers updating from systems older than version 8.5 2019-11-26, however if you are experiencing this upload issue, it is best to use build 523.

Best regards,

HansaWorld Support

Aldevinas Katkus

2-19-20

all cases were with build 8.5 2020-01-07 (build 85330517), some of them upgraded from 8.4,8.2 some (ourselves) from 8.5 2019-11-26. While uprading from build 517 to 524 I have seen many of these in the log:
2020-02-17 12:29:39 (-1) M4JobVc

2020-02-17 12:29:39 (-1) Skipping import of softvar s3uploadi of type with value in register M4JobVc, unknown type.

When at some point after upgrade to build 524 the client became unresponsive, I moved all old TByyyymmdd.TXT to another folder and it became responsive again. That particular client has some very strict cisco firewall. Could the firewall with packet inspection feature be an extra problem?

Bror-Erik Kotiranta

2-21-20

If you´re talking about the spi then no, it will not. The problem here was the new dsp(data security plan) that was fixed in builds later than 514 on version 8.5 2020 01 07.
Could not upload job / skipping s3upload - are both related to that feature and should be fixed in builds greater than 519(so 520 and up)

Back to the list

New Message
Open Questions My Questions