Home› AMX User Forum› NetLinx Studio

GetString / CopyString Error

thomas.judthomas.jud Posts: 44
in NetLinx Studio
Hi Folks,

Any ideas to fix this diagnostic errors ?

Line 2298 (18:44:40):: Connected Successfully
Line 2299 (18:44:40):: CIpEvent::OnLine 0:21:1
Line 2300 (18:44:43):: accepted a connection from 192.168.26.161
Line 2301 (18:44:43):: No more client connections allowed on port 25, closing listening socket
Line 2302 (18:44:43):: CIpEvent::OnLine 0:17:1
Line 2303 (18:44:43):: Exiting TCP Read thread - closing this socket for local port 17
Line 2304 (18:44:43):: CIpEvent::OffLine 0:17:1
Line 2305 (18:44:55):: Exiting TCP Read thread - closing this socket for local port 20
Line 2306 (18:44:55):: CIpEvent::OffLine 0:20:1
Line 2307 (18:44:55):: Connected Successfully
Line 2308 (18:44:55):: CIpEvent::OnLine 0:20:1
> Line 2309 (18:44:56):: GetString - Error 1 Tk=0x0000
> Line 2310 (18:44:56):: CopyString (Reference) - Error 2 S=0x0000 D=0x1033
Line 2311 (18:45:10):: Exiting TCP Read thread - closing this socket for local port 21
Line 2312 (18:45:10):: CIpEvent::OffLine 0:21:1
Line 2313 (18:45:10):: Connected Successfully

Thanks Thomas

Comments

  • ericmedleyericmedley Posts: 4,177
    IIt's telling you that you have a runtime error in your code at line 2309 and 2310. Post your code block that includes those lines numbers and we'll see what's going on.
  • John NagyJohn Nagy Posts: 1,742
    Eric, the line numbers are all sequential, and appear to be from NetLinx Studio's reporting window, they are not referencing lines of code.
  • Andrew G WelkerAndrew G Welker Posts: 124
    True, but it seems to happen right after whatever IP device is on port 20 comes online. I'm willing to bet its something in the online event of that device that is throwing the error.
  • ericmedleyericmedley Posts: 4,177
    John Nagy wrote: »
    Eric, the line numbers are all sequential, and appear to be from NetLinx Studio's reporting window, they are not referencing lines of code.

    Ah, try Dat.
    I Lethe indentation fool me. My bad
    E
  • thomas.judthomas.jud Posts: 44
    more diagnostic

    Line 370 (07:43:43):: Exiting TCP Read thread - closing this socket for local port 12
    Line 371 (07:43:43):: CIpEvent::OffLine 0:12:1
    Line 372 (07:43:43):: Connected Successfully
    Line 373 (07:43:43):: CIpEvent::OnLine 0:12:1
    Line 374 (07:43:44):: Exiting TCP Read thread - closing this socket for local port 12
    Line 375 (07:43:44):: CIpEvent::OffLine 0:12:1
    Line 376 (07:43:44):: Connected Successfully
    Line 377 (07:43:45):: CIpEvent::OnLine 0:12:1
    > Line 378 (07:43:45):: GetString - Error 1 Tk=0x0000
    > Line 379 (07:43:45):: CopyString (Reference) - Error 2 S=0x0000 D=0x1033
    Line 380 (07:43:45):: Exiting TCP Read thread - closing this socket for local port 12
    Line 381 (07:43:46):: CIpEvent::OffLine 0:12:1
    Line 382 (07:43:46):: Connected Successfully
    Line 383 (07:43:46):: CIpEvent::OnLine 0:12:1
    Line 384 (07:43:47):: Exiting TCP Read thread - closing this socket for local port 12
    Line 385 (07:43:47):: CIpEvent::OffLine 0:12:1
    Line 386 (07:43:47):: Connected Successfully
    Line 387 (07:43:47):: CIpEvent::OnLine 0:12:1
    Line 388 (07:43:48):: Exiting TCP Read thread - closing this socket for local port 12
    Line 389 (07:43:48):: CIpEvent::OffLine 0:12:1
    Line 390 (07:43:48):: Connected Successfully
    Line 391 (07:43:48):: CIpEvent::OnLine 0:12:1
    Line 392 (07:43:49):: Exiting TCP Read thread - closing this socket for local port 12
    Line 393 (07:43:49):: CIpEvent::OffLine 0:12:1
    Line 394 (07:43:49):: Connected Successfully
    Line 395 (07:43:49):: CIpEvent::OnLine 0:12:1
    Line 396 (07:43:50):: Exiting TCP Read thread - closing this socket for local port 12
    Line 397 (07:43:50):: CIpEvent::OffLine 0:12:1
    Line 398 (07:43:50):: Connected Successfully
    Line 399 (07:43:50):: CIpEvent::OnLine 0:12:1
    Line 400 (07:43:51):: Exiting TCP Read thread - closing this socket for local port 12
    Line 401 (07:43:51):: CIpEvent::OffLine 0:12:1
    Line 402 (07:43:51):: Connected Successfully
    Line 403 (07:43:51):: CIpEvent::OnLine 0:12:1
    Line 404 (07:43:52):: Exiting TCP Read thread - closing this socket for local port 12
    Line 405 (07:43:52):: CIpEvent::OffLine 0:12:1
    Line 406 (07:43:52):: Connected Successfully
    Line 407 (07:43:52):: CIpEvent::OnLine 0:12:1
    Line 408 (07:43:53):: accepted a connection from 192.168.26.166
    Line 409 (07:43:53):: No more client connections allowed on port 25, closing listening socket
    Line 410 (07:43:53):: CIpEvent::OnLine 0:17:1
    Line 411 (07:43:53):: Exiting TCP Read thread - closing this socket for local port 12
    Line 412 (07:43:53):: CIpEvent::OffLine 0:12:1
    Line 413 (07:43:53):: Connected Successfully
    Line 414 (07:43:53):: CIpEvent::OnLine 0:12:1
    Line 415 (07:43:53):: Exiting TCP Read thread - closing this socket for local port 20
    Line 416 (07:43:53):: CIpEvent::OffLine 0:20:1
    Line 417 (07:43:53):: Connected Successfully
    Line 418 (07:43:53):: CIpEvent::OnLine 0:20:1
    Line 419 (07:43:53):: Exiting TCP Read thread - closing this socket for local port 17
    Line 420 (07:43:53):: CIpEvent::OffLine 0:17:1
    Line 421 (07:43:54):: Exiting TCP Read thread - closing this socket for local port 12
    Line 422 (07:43:54):: CIpEvent::OffLine 0:12:1
    Line 423 (07:43:54):: Connected Successfully
    Line 424 (07:43:54):: CIpEvent::OnLine 0:12:1
    Line 425 (07:43:55):: Exiting TCP Read thread - closing this socket for local port 12
    Line 426 (07:43:55):: CIpEvent::OffLine 0:12:1
    Line 427 (07:43:55):: Connected Successfully
    Line 428 (07:43:55):: CIpEvent::OnLine 0:12:1
    Line 429 (07:43:56):: Exiting TCP Read thread - closing this socket for local port 12
    Line 430 (07:43:56):: CIpEvent::OffLine 0:12:1
    Line 431 (07:43:56):: Connected Successfully
    Line 432 (07:43:56):: CIpEvent::OnLine 0:12:1
    Line 433 (07:43:57):: Exiting TCP Read thread - closing this socket for local port 12
    Line 434 (07:43:57):: CIpEvent::OffLine 0:12:1
    Line 435 (07:43:57):: Connected Successfully
    Line 436 (07:43:57):: CIpEvent::OnLine 0:12:1
    Line 437 (07:43:58):: Exiting TCP Read thread - closing this socket for local port 12
    Line 438 (07:43:58):: CIpEvent::OffLine 0:12:1
    Line 439 (07:43:58):: Connected Successfully
    Line 440 (07:43:58):: CIpEvent::OnLine 0:12:1
    Line 441 (07:43:59):: Exiting TCP Read thread - closing this socket for local port 12
    Line 442 (07:43:59):: CIpEvent::OffLine 0:12:1
    Line 443 (07:43:59):: Connected Successfully
    Line 444 (07:43:59):: CIpEvent::OnLine 0:12:1
    Line 445 (07:44:00):: Exiting TCP Read thread - closing this socket for local port 12
    Line 446 (07:44:00):: CIpEvent::OffLine 0:12:1
    Line 447 (07:44:00):: Connected Successfully
    Line 448 (07:44:00):: CIpEvent::OnLine 0:12:1
    Line 449 (07:44:01):: Exiting TCP Read thread - closing this socket for local port 12
    Line 450 (07:44:01):: CIpEvent::OffLine 0:12:1
    Line 451 (07:44:01):: Connected Successfully
    Line 452 (07:44:01):: CIpEvent::OnLine 0:12:1
    Line 453 (07:44:02):: Exiting TCP Read thread - closing this socket for local port 12
    Line 454 (07:44:02):: CIpEvent::OffLine 0:12:1
    Line 455 (07:44:02):: Connected Successfully
    Line 456 (07:44:02):: CIpEvent::OnLine 0:12:1
    Line 457 (07:44:03):: Exiting TCP Read thread - closing this socket for local port 12
    Line 458 (07:44:03):: CIpEvent::OffLine 0:12:1
    Line 459 (07:44:03):: Connected Successfully
    Line 460 (07:44:03):: CIpEvent::OnLine 0:12:1
    Line 461 (07:44:04):: Exiting TCP Read thread - closing this socket for local port 12
    Line 462 (07:44:04):: CIpEvent::OffLine 0:12:1
    Line 463 (07:44:04):: Connected Successfully
    Line 464 (07:44:04):: CIpEvent::OnLine 0:12:1
    > Line 465 (07:44:05):: GetString - Error 1 Tk=0x0000
    > Line 466 (07:44:05):: CopyString (Reference) - Error 2 S=0x0000 D=0x1033
    Line 467 (07:44:05):: Exiting TCP Read thread - closing this socket for local port 12
    Line 468 (07:44:05):: CIpEvent::OffLine 0:12:1
    Line 469 (07:44:05):: Connected Successfully
    Line 470 (07:44:05):: CIpEvent::OnLine 0:12:1
    Line 471 (07:44:06):: Exiting TCP Read thread - closing this socket for local port 12
    Line 472 (07:44:06):: CIpEvent::OffLine 0:12:1
    Line 473 (07:44:06):: Connected Successfully
    Line 474 (07:44:06):: CIpEvent::OnLine 0:12:1
    Line 475 (07:44:06):: Exiting TCP Read thread - closing this socket for local port 21
    Line 476 (07:44:06):: CIpEvent::OffLine 0:21:1
    Line 477 (07:44:06):: Connected Successfully
    Line 478 (07:44:06):: CIpEvent::OnLine 0:21:1
    Line 479 (07:44:07):: Exiting TCP Read thread - closing this socket for local port 12
    Line 480 (07:44:07):: CIpEvent::OffLine 0:12:1
    Line 481 (07:44:07):: Connected Successfully
    Line 482 (07:44:07):: CIpEvent::OnLine 0:12:1
    Line 483 (07:44:08):: Exiting TCP Read thread - closing this socket for local port 12
    Line 484 (07:44:08):: CIpEvent::OffLine 0:12:1
    Line 485 (07:44:08):: Connected Successfully
    Line 486 (07:44:08):: CIpEvent::OnLine 0:12:1
    Line 487 (07:44:09):: Exiting TCP Read thread - closing this socket for local port 12
    Line 488 (07:44:09):: CIpEvent::OffLine 0:12:1
    Line 489 (07:44:09):: Connected Successfully
    Line 490 (07:44:09):: CIpEvent::OnLine 0:12:1
    Line 491 (07:44:10):: Exiting TCP Read thread - closing this socket for local port 12
    Line 492 (07:44:10):: CIpEvent::OffLine 0:12:1
    Line 493 (07:44:10):: Connected Successfully
    Line 494 (07:44:10):: CIpEvent::OnLine 0:12:1
    Line 495 (07:44:11):: Exiting TCP Read thread - closing this socket for local port 12
    Line 496 (07:44:11):: CIpEvent::OffLine 0:12:1
    Line 497 (07:44:11):: Connected Successfully
    Line 498 (07:44:11):: CIpEvent::OnLine 0:12:1



    Its not even on each IP connection but sometimes.
    I've about 20 IP Sockets and 1 telnet server on this AMX.
    Sometimes this error is on connection/disconnection from port 12 sometimes from port 17,21....
  • John NagyJohn Nagy Posts: 1,742
    What are the devices on 12 and the other problem ports?
    What code runs upon connect? Look for some parsing or metadata manipulation that could have to do with string lengths.

    What you posted is a little like a picture of the smoke, and you are asking what started the fire.
  • DHawthorneDHawthorne Posts: 4,584
    John Nagy wrote: »
    What are the devices on 12 and the other problem ports?
    What code runs upon connect? Look for some parsing or metadata manipulation that could have to do with string lengths.

    What you posted is a little like a picture of the smoke, and you are asking what started the fire.

    I like that analogy. I've always hated that some errors, notoriously string manipulations, don't generate line numbers in the runtime error notifications. Bad enough that 90% of the time the errors that do generate line numbers generate the wrong one, but at least they get you in the ballpark.

    That said, the error may not have a thing to do with the online events. It's the first place to look, but it might be pure coincidence. The only thing to do if you can't find it just looking at the source code, is to start commenting things out until it goes away so you can isolate the problem.
Sign In or Register to comment.