InstaAlert Login Issues

[kami]

Hi;

We use InstaAlert in 2 workstations and none can login to the server. All was working in the last stable release but since we upgraded to the interims, due to IE 7 issues, the InstaAlert has problems.

The installation is:

Version: 3.10.00 (CVS) - 21 Jan 2007 01:13 AM

21/01/2007 10:37:11 Failed to get ticket data from server. Reason: 'Authentication has failed!'

Error: <No extended error information available>
21/01/2007 11:08:23 Logging in to 'https://support.clickandpledge.com/' with user name '*** DELETED FOR POSTING***'
21/01/2007 11:08:23 Failed to get ticket data from server. Reason: 'Authentication has failed!'

Error: <No extended error information available>

We have the same problem with SynchWorks. LiveResponse works fine and no problem with login issues so we know the userid & password works.

Any idea why this is the case?

Regards,
Kami

[Ryan Lederman]

This is because the later builds of SyncWorks and InstaAlert are using a different encoding scheme when sending User Names to the server in order to accommodate international user names.

You'll need to upgrade your server-side software in order to use the latest InstaAlert + SyncWorks builds.

[kami]

Hi Ryan:

I have the latest built and the latest of all packages as is included in the latest CVS.

Anytime I update the system I also update the InstaAlert, SynchWorks, and LiveSupport client.

It does not work.

Regards,
Kami

[Ryan Lederman]

Can you please e-mail me login credentials so I can test?

[Mark Worsnop]

I have the same problem. Roger (one of the developers) said he has found the problem with LiveResponse and is working on a fix now.
I hope to see something this week.

[Ryan Lederman]

Please upgrade to http://hotfix.kayako.com/instaalert/...LE-3.1.1.4.exe and let me know if the issue persists.

[kami]

Hi Ryan:

InstaAlert: Seems to be working now with the following built.

SyncWorks: Worked almost all the way to the end but gave the following error:

09/02/2007 08:30:25 An error occurred while attempting to communicate with the server:

Received unexpected response from server (invalid header)!

Data: (<br />
<b>Warning</b>: Invalid argument supplied for foreach() in <b>D:\InetPub\Kayako\modules\teamwork\syncworks_sy nc.php</b> on line <b>705</b><br />
<br />
<b>Warning</b>: Cannot modify header information - headers already sent by (output started at D:\InetPub\Kayako\modules\teamwork\syncworks_sync. php:705) in <b>D:\InetPub\Kayako\includes\functions.php</b> on line <b>2632</b><br />
compressed;e92f46482debb41bf8906bf3dd019c74;c4ca42 38a0b923820dcc509a6f75849b;9;1;x^3)

Error: <No extended error information available>
Installed version: Version: 3.10.00 (CVS) - 09 Feb 2007 01:13 AM

thanks
Kami

[Ryan Lederman]

kami,

I have seen this particular warning message from SyncWorks before. I've forwarded it to Varun so he can take a look. Do we already have FTP access to your server? If not I will need it.

[marrodbe]

Im having this error

05/03/2007 01:08:19 Logging in to 'http://www.gutshotgaming.com/support/upload/' with user name 'marco'
05/03/2007 01:08:22 Logged in successfully. Session ID = {c5d9c816cf4e826304f546fcb4032fc3}, Version = '3.00.81'
05/03/2007 01:08:22 Refreshing XML from 'http://www.gutshotgaming.com/support/upload/'
05/03/2007 01:08:24 Failed to get ticket data from server. Reason: 'Received unexpected response from server (invalid header)!

Can somebody help please cause i already bought this...

[Ryan Lederman]

Originally Posted by marrodbe

Im having this error

05/03/2007 01:08:19 Logging in to 'http://www.gutshotgaming.com/support/upload/' with user name 'marco'
05/03/2007 01:08:22 Logged in successfully. Session ID = {c5d9c816cf4e826304f546fcb4032fc3}, Version = '3.00.81'
05/03/2007 01:08:22 Refreshing XML from 'http://www.gutshotgaming.com/support/upload/'
05/03/2007 01:08:24 Failed to get ticket data from server. Reason: 'Received unexpected response from server (invalid header)!

Can somebody help please cause i already bought this...

We need to see the actual data sent by the server in order to properly diagnose the problem.