LeakBuster error message

[dackjaniels]

Thanks, will download the new beta and try it out.

[Leak Buster Support]

Ok I have tried modifying the hosts file and it has not worked. I wonder if reinstalling PostgreSQL would help?

Pm'd again so we can schedule a session.

[Enecosse]

My last pm was on the 18th Oct with the initial reg code. I am away for a few days, but when I get back will try the latest HM beta. From what I can see I will need a new reg code?

[Enecosse]

I have installed Beta 41, I have done the hosts file, .pid things, with a reboot. Also turned off windows firewall. Still get the same error message. Only difference is that I see something flash real quick in the top left corner before the error message comes up, (when LB is trying to connect to the .db).

I have several .db on my computer with postreSQL 8.2 and 8.3 with HM on 8.3. The server name is 127.0.0.1 on port 5433 which is slightly different from the default 5432. HM runs with no other problems other than a very brief ''not responding' when it starts, I assume that is becasue I have a large .db

Any other ideas?

[Leak Buster Support]

Yes, we e-mailed that test program, and I need you to run the second one I sent you so we can check out your connection log. That will be the biggest clue for us to see what's going on with your particular system. I re-sent it to you just not, just in case you didn't get it (I know you got the first one we sent out).

[Enecosse]

Your last two posts.......I just don't have a clue what your talking about. Where they directed at me or someone else? And yes I have checked my spam folder.

[Leak Buster Support]

I may have gotten you confused with another person in this thread... sorry. Please PM me with your e-mail address and I will send you the program that will check your connection.

[RedBarracuda]

beta .42

Npgsql.NpgsqlException:
Connection establishment timeout. Increase Timeout value in ConnectionString.
at Npgsql.NpgsqlState.ProcessBackendResponsesEnum(Npg sqlConnector context)
at Npgsql.NpgsqlReadyState.QueryEnum(NpgsqlConnector context, NpgsqlCommand command)
at Npgsql.NpgsqlConnector.QueryEnum(NpgsqlCommand queryCommand)
at Npgsql.NpgsqlCommand.GetReader(CommandBehavior cb)
at Npgsql.NpgsqlCommand.ExecuteReader(CommandBehavior cb)
at Npgsql.NpgsqlCommand.ExecuteReader()
at PostgresConnection.f_OlDbReader(String query)
at c.b8(Boolean A_0, Boolean A_1, Boolean A_2, Boolean A_3, DateTime A_4, DateTime A_5)
at c.b8(Boolean A_0, Boolean A_1, Boolean A_2, Boolean A_3, Boolean A_4)
at LeakBuster2._.Mainf.b(Object A_0, DoWorkEventArgs A_1)

[Leak Buster Support]

beta .42

Can you give a few more details about your error. What OS are you running, and what were you doing when you got the error? What kind of import were you attempting to do? Does this always happen, or just sometimes. Thanks.

[RedBarracuda]

Can you give a few more details about your error. What OS are you running, and what were you doing when you got the error? What kind of import were you attempting to do? Does this always happen, or just sometimes. Thanks.

I didn't have problems before beta .40.

I am running XP x64 and I tried to import by stake level. Then it goes into "obtaining my data, please be patient" but ends up with that error message.

Although, I tried it right now, and it worked just fine. I guess the problem was there just yesterday (all day long)?