Post reply

DTSRUN.EXE APPLICATION ERROR(SQL SERVER 2000)

  • September 21, 2005 at 5:31 am

    #69645

    Hi All,

    Iam calling a stored procedure from a job,this stored procedure will call  10 dts.From the past 1 year it is executing properly.From the past one week an error is popup DTSRUN.EXE Application error.The memory cannot be read.These DTs will fetch the DATA from LOTUS NOTES DATABASES.

    I checked the hard disk , enough space is there.

    The error is occuring only when the job calls the stored procedure

    If i executed stored procedure from query analyzer then there is no problem.

    I searched almost all sites but i didnt find the solution.

    Thanks in advance,

    J.Aswani kumar.

     

     

     

  • September 21, 2005 at 6:33 am

    #591689

    "The error is occuring only when the job calls the stored procedure

    If i executed stored procedure from query analyzer then there is no problem. "

    Hmmm ... conflicting executions of this sort usually indicate a permission error somewhere.

    When you're executing in Query Analyzer, the package is executing in the context of the credetials used when you connected to the server.

    When the package executes from a scheduled job it executes under the seecurity context of the SQL Server Agent, or it proxy account.

    What account(s) are the SQL Services running under? Are you able to supply a bit more information about the error? Do you have package logging enabled? If so, at what step does the package fail?

     

    --------------------
    Colt 45 - the original point and click interface

  • September 21, 2005 at 6:52 am

    #591705

    Thanks phillcart for responding..

    The error is occuring in server.A message box will be popuped(DTSRUN.EXE ERROR-APPLICATION ERROR,THE MEMORY COULD NOT BE READ).Scheduled calls a stored procedure ,in that stored procedure DTS packages are called.The same error is not coming daily .we have 15 DTS packages it is not giving error in same DTS Daily.

     

  • September 21, 2005 at 7:03 am

    #591723

    In the stored procedure, are you using the sp_OA* procedures to execute the packages, or xp_cmdshell?

    The sp_OA* procedures a know to cause memory leaks. So if you are using them a better option would be to use xp_cmdshell, or even put the DTSRUN command in the scheduled job itself.

     

    --------------------
    Colt 45 - the original point and click interface

  • September 21, 2005 at 7:19 am

    #591738

    Thanks once again!!

    we are using xp_cmd shell to execute the dts.

    we will call 15 dts from Stored procedure and some logic is there in sp ,i cant call the dts from jobs.

    we have 15 dts and some logic is there in Stored procedure.

     

     

  • September 21, 2005 at 7:19 am

    #591737

    Thanks once again!!

    we are using xp_cmd shell to execute the dts.

    we will call 15 dts from Stored procedure and some logic is there in sp ,i cant call the dts from jobs.

    we have 15 dts and some logic is there in Stored procedure.

     

     

  • September 21, 2005 at 10:22 am

    #591880

    Maybe sometimes (as you told it happened not every time) the records from Lotus notes ate too long or the previous DTS overloaded memory and it can not read it (This behavior occurs because the operating system does not allocate a large enough buffer for the maximum string length permitted. When the data is greater than the buffer size, the Winlogon service terminates abnormally and your computer generates the error message. http://search.microsoft.com/search/results.aspx?st=b&na=88&View=en-us&qu=MEMORY+COULD+NOT+BE+READ)

    because the only Lotus Notes is changing every day (you are not changing your server settings daily, right), so I think the problem is in Lotus Notes

Viewing 7 posts - 1 through 6 (of 6 total)

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