Community
Showing results for 
Search instead for 
Do you mean 
Reply

APFW v18 EN: Thread was being aborted

Copper Contributor
Posts: 26
Country: Switzerland

APFW v18 EN: Thread was being aborted

New installation of APWF v18 EN
Server: Windows 2012 10GB 4Core x64
Act! and IIS on the same server

Login trough web takes at least 45 to 90 and sometimes more seconds.

Windows eventlog shows the following error (if the error has occured, the logon process to APFW has finished and the user is logged on):

 

SOURCE: Act.Web
MESSAGE: Thread was being aborted.
FORM: __EVENTTARGET=&__EVENTARGUMENT=&__VIEWSTATE=%2fwEPDwUKMTAzODE1OTQxNQ9kFggCAQ9kFgICBA9kFgJmDxYCHgRUZXh0BRUjUEFHRV9USVRMRSMgLSBMb2cgb25kAgMPDxYCHwAFJ1ByZXBhcmluZyB5b3VyIGRhdGFiYXNlLiBQbGVhc2Ugd2FpdC4uLmRkAgUPZBYKAgEPDxYEHwBlHgdWaXNpYmxlaGRkAgMPDxYCHwAFCkxvZyBvbiB0bzpkZAIFDxBkDxYBZhYBEAUDQUNUBRxBQ1R8Q0hSVjcwNzQuY29ycC5nd3BuZXQuY29tZ2RkAgcPPCsACgEADxYCHghVc2VyTmFtZWVkFgJmD2QWBgIBDw8WAh8ABQlVc2VybmFtZTpkZAIHDw8WAh8ABQlQYXNzd29yZDpkZAIPDw8WAh8ABRRSZW1lbWJlciBteSB1c2VybmFtZWRkAgkPDxYCHwAFB1ZlcnNpb25kZAIHDxYCHwFoZBgBBR5fX0NvbnRyb2xzUmVxdWlyZVBvc3RCYWNrS2V5X18WAQUfbG9naW5Db250cm9sJGN4UmVtZW1iZXJVc2VybmFtZcGX8Y4%2baBreIRvS2x8GT7cAf7qNWNLfiuAfapzdYHCe&ddlDatabaseSelector=ACT%7cCHRV7074.corp.gwpnet.com&loginControl%24UserName=sa&loginControl%24Password=M00nBase&loginControl%24LoginButton=&__VIEWSTATEGENERATOR=636BDFFB
QUERYSTRING: ReturnUrl=%2fAPFW
TARGETSITE: Boolean ValidateUser(System.String, System.String)
STACKTRACE: at Act.Web.ACTMembershipProvider.ValidateUser(String username, String password)
REFERER: http://chrv7074.corp.gwpnet.com/APFW/default.aspx?ReturnUrl=%2fAPFW

2016-01-15 12_26_49-Clipboard.png

 

Does someone have a solution for that?

Stefan Koehli
ACT! Cerified Consultant
KÖHLI INFORMATIK AG
Moderator
Posts: 68
Country: United_Kingdom

Re: APFW v18 EN: Thread was being aborted

Hi Stefan,

 

If you add another database to the existing virtual directory, does this give the same problem?

 

I would also make sure KB 25125 has been followed on the server to make sure the anti-virus and firewalls are not interfering.

 

Peter

Copper Contributor
Posts: 26
Country: Switzerland

Re: APFW v18 EN: Thread was being aborted

Hi Peter

 

Yes, we have tested with the Demo database, this gives the same error.

 

I check with the customer if we can exclude any anti-virus and firewalls.

 

Stefan

 

Stefan Koehli
ACT! Cerified Consultant
KÖHLI INFORMATIK AG
Copper Contributor
Posts: 26
Country: Switzerland

Re: APFW v18 EN: Thread was being aborted

Peter, 

 

We have now all Act! related parts exluded from anti-virus, as recommended in KB 25125. A firewall ist not existing an not startet on the server.

 

We still have the same problem: Login into APWF takes sometimes 180 seconds and after the login we recognize the error message in windows event log (as described in the start of this thread).

Stefan Koehli
ACT! Cerified Consultant
KÖHLI INFORMATIK AG
Moderator
Posts: 68
Country: United_Kingdom

Re: APFW v18 EN: Thread was being aborted

Hi Stefan,

 

From everything you have tested it sounds like the problem is either program or Virtual directory related.

 

Can try re-creating the Virtual directory as per the following KB: http://kb.swiftpage.com/app/answers/detail/a_id/14868/kw/create%20virtual%20directory

 

If that doesn't work, try reinstalling the Act! program.

 

See if any of those fixes help.

 

Peter

Copper Contributor
Posts: 26
Country: Switzerland

Re: APFW v18 EN: Thread was being aborted

Hi Peter,

 

We found out that Act! connects to 2 IP adresses with port 80 during the logon process:

 

207.97.197.145
157.55.193.87

 

We don't have actually more information about the reason why Act! connects to these adresses. But this is most likely the reason why the logon process takes such a long time, when the customer firewall blocks access to any IP adresses.

 

Of corse we can define an exception for the two adresses, but before we have to know what is going because the customer is an international finance service supplier with very high security restrictions. 

 

The ceonnections to these IP adresses have nothing in common with KB15244. KB15244 explains how to add anexception on the firewall for the licencse activation and this connection is made with port 443 to the host license.ntitles.net

 

Stefan

Stefan Koehli
ACT! Cerified Consultant
KÖHLI INFORMATIK AG
New Member
Posts: 1
Country: Canada

Re: APFW v18 EN: Thread was being aborted

[ Edited ]

Hi Stefan,

 

Did you ever come up with a solution to this?

Bronze Elite Contributor
Posts: 1,426
Country: United_Kingdom

Re: APFW v18 EN: Thread was being aborted

[ Edited ]

I expect this is ACT's licencing system Protexis tying to contact to the monitoring site.