Tuesday, May 26, 2009

froglogic squish fail

Has it ever happened to you to use squish without problems... and then out of a sudden, the server log shows this:

Debug: Client thread created, sock: 1368
Debug: Client thread destroyed, sock: 1460
Debug: Client thread destroyed, sock: 1488
Debug: Connection established to 127.0.0.1
Debug: Client thread created, sock: 1468
Debug: Connection established to 127.0.0.1
Debug: Qt Warning: IPC::sendData: couldn't write to socket, the peer closed the connection


No configured application starts any longer! What gives?
My initial answer (and very emotional one considering I wasted more than one hour with this) is that "Squish sux!!!!"

But that's not the information I want to share with you. What fixed the problem for me was going into the [C:\Documents and Settings\%username%\Application Data\froglogic\Squish\ver1\] folder and edit the ide.ini file. It's a simple ini file.
It seems that a line that looks like this appears out of nowhere:
Data = 37

(You should find it in the neighourhood of:
ControlBarWidth = 571
ControlBarX = 1074
ControlBarY = 451
Data = 37
DebugLogOptions = ""
DefaultLanguage = "JavaScript")

Just remove the evil red line and it should work again.

5 comments:

  1. That worked perfectly!

    Thank you : )

    ReplyDelete
  2. Awesome, thanks a bunch. This probably saved me hours of time.

    ReplyDelete
  3. Thanks, that helped!!

    ReplyDelete
  4. This worked, but you have to ask WHY???

    Thanks so much! Saved me a lot of time!

    ReplyDelete
  5. It is a fail-safe from Froglogic,
    Whenever an invalid (or unexisting) license key file was read, Squish will write "Data = 37" into the ide.ini, making the software completely useless.
    Since deleting the line worked, it seems that this was a bug in Squish. Because whenever Squish would start, it would try to read the license key file and write that line into ide.ini.

    ReplyDelete