ok, waiting next build
Message was edited by: victorae
victorae wrote:
ok, waiting next build
? I haven’'t the slightest idea what you are trying to say with this thread.
I have described the problem, but it has appeared that it is present at all.
Therefore has corrected contents of posting.
So, are you saying that the problem you were experiencing is fixed in 1.0 beta 6a?
I am sorry. Probably has in vain modified the message. I shall repeat -
wildfire 3.1.1, beta 6a, db mssql7
add plugin file, create tables via script
psi 0.10 - ICQ Transport - register - its done,
console :9090 - gateways - registration - its done
psi ICQ Transport GREY - LogIn - Green
add ICQ contact - send message - allert from icq.myserver -
“You are not currently logged into the ICQ transport”
if recreate registration and enter NOT valid password for uin - green status.
WF 3.1.1 on Windows 2003, IM Gateway beta6a, db in MSSQL2000.
beta5a is worked, but beta6a not.
trk wrote:
WF 3.1.1 on Windows 2003, IM Gateway beta6a, db in MSSQL2000.
beta5a is worked, but beta6a not.
Define “not”. What broke?
victorae wrote:
I am sorry. Probably has in vain modified the message. I shall repeat -
wildfire 3.1.1, beta 6a, db mssql7
add plugin file, create tables via script
psi 0.10 - ICQ Transport - register - its done,
console :9090 - gateways - registration - its done
psi ICQ Transport GREY - LogIn - Green
add ICQ contact - send message - allert from icq.myserver -
“You are not currently logged into the ICQ transport”
if recreate registration and enter NOT valid password for uin - green status.
Hrm. If you are seeing the not currently logged in message, the plugin believes that you aren’‘t completely logged into ICQ. And this worked under beta 5a? (the reason I ask is, I was told that ICQ seems to have changed something in their protocol and that pyicqt doesn’‘t seem to be working well at the moment) I’‘m wondering if that’'s bleeding over to this ICQ transport now. What do you see in your debug logs?
yes, im stop server, delete file gateway.jar and folder gateway. copy file gateway.jar 5a and start
server - all work exlude russion charset. but im need russian.
debug log 6a
====
2006.12.19 18:02:19 Received iq packet:
2006.12.19 18:07:34 icq: contactAdded victor_ae:152316775@icq.im.papir.kiev.ua
2006.12.19 18:07:34 contact = 152316775, grouplist =
2006.12.19 18:07:34 Found group item: GroupItem for , groupid=0x1, buddies: none at id 1
2006.12.19 18:07:34 Found buddy item: BuddyItem for 152316775 (buddy 0x1 in group 0x1): alias=152316775, comment=“null”, alerts: at id 1
2006.12.19 18:07:34 icq: contactUpdated victor_ae:152316775@icq.im.papir.kiev.ua
2006.12.19 18:07:34 contact = 152316775, grouplist =
2006.12.19 18:07:34 Found buddy item: BuddyItem for 152316775 (buddy 0x2 in group 0x1): alias=152316775, comment=“null”, alerts: at id 2
2006.12.19 18:07:34 Received presence packet:
Message was edited by: victorae
victorae wrote:
yes, im stop server, delete file gateway.jar and folder gateway. copy file gateway.jar 5a and start
server - all work exlude russion charset. but im need russian.
That’‘s… bizarre. Off the top of my head I couldn’‘t tell you what would be causing this. I didn’'t change that much of the actual functionality of the transports! Most of my work was with the admin interface. Hrm.
maybe sql base problem? sql script gateway -sqlserver.sql not correctly work with mssql7.0
datatype BIGINT not preset, edited to INT and registrationDate to numeric
gatewayRegistration
NOT NULL ,
…
(18, 0) NOT NULL ,
NULL
victorae wrote:
maybe sql base problem? sql script gateway -sqlserver.sql not correctly work with mssql7.0
datatype BIGINT not preset, edited to INT and registrationDate to numeric
gatewayRegistration
NOT NULL ,
…
(18, 0) NOT NULL ,
NULL
ack! does BIGINT exist in another iteration of MSSQL? Looks like generally a bad db file on my part. I’‘ll get that fixed! The only change I’‘m going to make is using CHAR(15) instead of numeric(18,0) I’‘m doing this because it’'s consistent with what wildfire itself is doing. (also INTEGER instead of INT, though I imagine those are the same) Thanks!!
BIGINT present in mssql2000 and maybe 2005.
Tell that to me to do - to migrate on sql2000, to correct structure of the table mssql7 or to wait for updating plugin?
Message was edited by: victorae
What’'s extremely bizarre about that is… beta 5a had the same db files. =) I just added a new table as of beta 6, but it still had a BIGINT entry in the very first table I ever created.
i’'m create base on mssql2000, run original script, edit config wildfire to new database, restart and have same problem.
after installing gateway plugin version 1.0 beta 6a, our icq transport doesn’‘t work any more (all other transports works great). icq using psi just delivers a green online icon, but doesn’'t show any contacts. viewing “last login” in gateway registrations shows “never”.
debug log says:
2006.12.19 21:36:25 Received presence packet:
2006.12.19 21:36:25 A new session has come online: user@cyber-worker.de/Psi
2006.12.19 21:36:25 Created icq session for user@cyber-worker.de/Psi as ‘‘myRealICQuin’’
2006.12.19 21:36:25 OSCAR login service state change from NOT_CONNECTED to INITING
2006.12.19 21:36:25 OSCAR login service state change from INITING to RESOLVING
2006.12.19 21:36:25 OSCAR login service state change from RESOLVING to CONNECTING
2006.12.19 21:36:25 OSCAR login service state change from CONNECTING to CONNECTED
2006.12.19 21:36:46 Received presence packet:
but obviously no icq-connection is established.
any suggestions?
i have same problem, just like akurtz and victorae described.
All the same - green status, show “connected” on client side with any icq uin and password. pyICQ work fine.
This is interesting … as of this evening I can no longer log into ICQ either. I wonder if they’‘re actively updating something? I’'ve had on an off reports about PyICQt not working anymore.
I have two jabber-server, wildfire 3.1.1 with pyICQ 0.7b on windows and jabberd 1.4 with pyICQ 0.8 on linux. Both is work now.
trk wrote:
i have same problem, just like akurtz and victorae described.
All the same - green status, show “connected” on client side with any icq uin and password. pyICQ work fine.
I have exactly the same problem.