Post reply

entrypoint not found in SQLRESLD.dll

  • February 11, 2004 at 5:26 am

    #81989

    Hi everybody,

    I have an testinstallation of SQL Server 7.0 on an old NT4 machine with SQL 2000 Client utilities installed later. Everything works fine on this machine except from following problem.

    When I schedule a DTS package which runs well when startet directly and will also run when startet in the same useraccount the SQL Server agent is running, the job always fails with:

     

    DTSRun.exe - entrypoint not found

    procedure entrypoint ?SQLUIUpdateRegistryfromResource@@YAJHPAUInstance_@@IKPAPBG1@Z not found in dynamic link library "SQLRESLD.dll"

    I tried to replace the dll by other versions but it is no use.

    Has anyone have had something like this before or can someone interpret that cryptic name of the entrypoint?

    Many thanks in advance

    Karsten

  • February 11, 2004 at 5:32 am

    #493603

    What Service Pack is installed on the SQL server? I seem to recall something along those lines fixed in SP 3 or 4 but I don't fully recall.

  • February 11, 2004 at 5:50 am

    #493610

    Thank you very much for this hint. I have installed no service packs at all since this installation is for test purposes only. But I will try to obtain an SP3 or SP4 for SQL Server 7.0. I do hope they are still available on the MS download sites.

     

  • February 11, 2004 at 5:53 am

    #493612

    They were last I looked but if you cannot find I should still have a copy on CD here, let me know.

  • February 13, 2004 at 3:43 am

    #493964

    Hi,

    I have found an SP3 on the microsoft site and installed it. Afterwards I could no longer start Client Utilities of SQL Server 2000 so I tried to set up and run a scheduled DTS package using another client, but the job could not start the DTS Package either.

    Now I have installed SQL Server 2000 Client utilities on my test machine again. Trying to run a scheduled DTS package job now provides the same error as before. What else can I try?

    Karsten 

  • February 13, 2004 at 4:07 am

    #493967

    I did came across simmilar situation. Just check the enviornment settings "path " (goto command prompt. and type PATH)

    also test by giving command dtsrun from command prompt (from c:\ only) this should give you same error. you would be able to run the dtsrun command properly from either one of c:\mssql7\bin or c:\program files\microsoft sql server\mssql\binn\  directory.  

    as you have multiple instance of client libraries and hence DTS related files, these clash is comming up.

    Solution

    1.  hardcode the dtsrun.exe command in scheduled with the directory name from where it is running properly (i guess it would be c:\mssql7\binn\ )

    2. remove C:\program files\microsoft sql server\mssql\binn\ from path variable.

     

    This solved my problem with dtsrun.

     

    -- Amit


    -- Amit


    "There is no 'patch' for stupidity."


    Download the Updated SQL Server 2005 Books Online.

  • February 13, 2004 at 7:23 am

    #493977

    Hi Amit,

    many thanks for your suggestion. It works now on the SQL Server 2000 directory. Unfortunatly, after completing the package an access violation error on memory access pops up. This does not harm package execution but puts in failed state the scheduled entry always wether the package ran fine or not.

    Do you have any idea for that as well?

    Thanks in advance

    Karsten

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

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