Post reply

Perl error

  • April 14, 2003 at 7:35 am

    #101436

    Hi gurus,

    I know this is not a perl discussion board, but I guess my problem is kind of related to both perl and SQL Server 2000 (but I may be wrong also). My problem is as follow: I am running a web server with Windows 2000 server, IIS, SQL Server 2000, ASP. I am also using Active Perl and mySQL to do some functions.

    I am getting an error "Perl.exe application error. The instruction at 0x7ffde001 referenced memory at 0x00000001. The memory could not be written". This error is not consistent, but comes up randomly when I execute perl scripts. My perl script do make database connection to SQL server 2000. I tried rewriting my code, resetting IIS properties, but the error wont go away.

    all the help will be greatly appreciated,

    thanks in advance,

    vijju

  • April 17, 2003 at 8:00 am

    This was removed by the editor as SPAM

  • April 17, 2003 at 8:48 am

    #454558

    What version of Perl are you using? ActiveState or compiled yourself?

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley

  • April 17, 2003 at 10:25 am

    #454582

    I am using ActiveState perl Version 5.6.1 (version 635).

    thanks,

    vijju

  • April 19, 2003 at 6:42 am

    #454711

    You know, I saw the same thing when I upgraded to build 635 and I couldn't trace it to anything specifically, but I was connecting to SQL Server. I didn't see it on 633. What I ended up doing was making the database connection as short as possible. But even then I had the same error.

    Interestingly enough, when I put it on a system with a lot more memory, I haven't had a repeat of the error. I went from 256 MB to > 1 GB so I can't say for sure what the threshold is.

    Apparently, we're not alone in receiving this error. See here:

    http://bugs.activestate.com/ActivePerl/show_bug.cgi?id=19562

    I don't think ActiveState has pinned down what the issue is, but it's happening whenever an ODBC connection is made, whether through DBI or using ADO. I'd say to try 5.8.0, but the release notes indicate the compiler is still not production ready.

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply