![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Darren, Thanks for your response. I will look into the various options you suggested. The funny thing is that I have the same DTS package running on a SQL server on a W2K machine and it works fine. I will post something here when and if it gets resolved. thanks again. Eric O. -----Original Message----- It does sound rather like it is an MDAC issue, but I'm not sure what yu can do. The 281735 issue woudl be something inside DTS itself that would need changing. 814410 would require you to open a PSS case, which I think may be the best option. I appear to have several VFP drivers on my system, all available in the connection type dop down, perhaps a different driver may work. -- Darren Green http://www.sqldts.com/http://www.sqldts.com "Eric Obrecht" wrote in message news:006801c331ca$4db9c180$a401280a (AT) phx (DOT) gbl"]news:006801c3- 31ca$4db9c180$a401280a (AT) phx (DOT) gbl[/url]... Darren, Thanks for responding. Yes it was a typo the KB article was Q281735, sorry about that. The reason I thought it might be related to KB 814410 was that the package was running fine until I upgraded to SQL2K SP3 and MDAC 2.7. The problem only occurs on one package and it occurs when the package copies several foxpro tables into an SQL tables of the same structure. I beleive it kicks out while its copying one table in particular with 250,000 records and 56 columns. I have set the allowable errors up to 200(its only recording 41 in the error txt file). The SQL table is 58 records short if you subtract the 41 errors it ends up 17 short. So its getting most of the records. Any help would be appreciated. Any insight would -----Original Message----- KB 281375 talks about Outlook 2002, typo? I am not sure why KB 814410 relates to this issue. Does this happen for all packages? If not, can you identify at what stage in your package it breaks? What tasks are running or about to run? -- Darren Green http://www.sqldts.com/http://www.sqldts.com "Eric Obrecht" wrote in message news:034a01c32c62$cd5c6ef0$a301280a (AT) phx (DOT) gbl"]news:034a0- 1c32c62$cd5c6ef0$a301280a (AT) phx (DOT) gbl[/url]... I have upgraded to SQL2K SP3a on NT 4.0 server and I am trying to run a DTS package and I keep on getting this error: "DTSRun.exe Application error - The instruction at 0x77f83632 referenced memory at 0x000cld3d. The memory could not be read. Click OK to terminate the Application." Another time it gave me this message: "DTSRun.exe Application error - The instruction at 0x77f7dd66e referenced memory at 0x30373534. The memory could not be written. Click OK to terminate the Application." I look at Knowledge Base article 281375 Which discusses a fix which that states - Remove the explicit FreeLibrary call for the dll that is using Odbc32.dll. That's nice but how does one go about removing the Freelibrary call? Is there another fix for this problem? They hinted there was at the following site: http://support.microsoft.com/default.aspx?scid=kb;EN-- http://support.microsoft.com/default.aspx?scid=kb;EN- US;814410 Any help would be greatly appreciated. Thanks in advance. Eric O. . . |
#2
| |||
| |||
|
|
I'm having the exact same problem. I'm importing a DBF file using the Visual Foxpro ODBC driver. I've tried all the other drivers that handle DBF files with the same result. However, I did discover that if I preview the data in the DTS package before running the package, the data imports fine. Did you happen to find a solution? Thanks, Chris |
|
Darren, Thanks for your response. I will look into the various options you suggested. The funny thing is that I have the same DTS package running on a SQL server on a W2K machine and it works fine. I will post something here when and if it gets resolved. thanks again. Eric O. -----Original Message----- It does sound rather like it is an MDAC issue, but I'm not sure what yu can do. The 281735 issue woudl be something inside DTS itself that would need changing. 814410 would require you to open a PSS case, which I think may be the best option. I appear to have several VFP drivers on my system, all available in the connection type dop down, perhaps a different driver may work. -- Darren Green http://www.sqldts.com/http://www.sqldts.com "Eric Obrecht" wrote in message news:006801c331ca$4db9c180$a401280a (AT) phx (DOT) gbl"]news:006801c3- 31ca$4db9c180$a401280a (AT) phx (DOT) gbl[/url]... Darren, Thanks for responding. Yes it was a typo the KB article was Q281735, sorry about that. The reason I thought it might be related to KB 814410 was that the package was running fine until I upgraded to SQL2K SP3 and MDAC 2.7. The problem only occurs on one package and it occurs when the package copies several foxpro tables into an SQL tables of the same structure. I beleive it kicks out while its copying one table in particular with 250,000 records and 56 columns. I have set the allowable errors up to 200(its only recording 41 in the error txt file). The SQL table is 58 records short if you subtract the 41 errors it ends up 17 short. So its getting most of the records. Any help would be appreciated. Any insight would -----Original Message----- KB 281375 talks about Outlook 2002, typo? I am not sure why KB 814410 relates to this issue. Does this happen for all packages? If not, can you identify at what stage in your package it breaks? What tasks are running or about to run? -- Darren Green http://www.sqldts.com/http://www.sqldts.com "Eric Obrecht" wrote in message news:034a01c32c62$cd5c6ef0$a301280a (AT) phx (DOT) gbl"]news:034a0- 1c32c62$cd5c6ef0$a301280a (AT) phx (DOT) gbl[/url]... I have upgraded to SQL2K SP3a on NT 4.0 server and I am trying to run a DTS package and I keep on getting this error: "DTSRun.exe Application error - The instruction at 0x77f83632 referenced memory at 0x000cld3d. The memory could not be read. Click OK to terminate the Application." Another time it gave me this message: "DTSRun.exe Application error - The instruction at 0x77f7dd66e referenced memory at 0x30373534. The memory could not be written. Click OK to terminate the Application." I look at Knowledge Base article 281375 Which discusses a fix which that states - Remove the explicit FreeLibrary call for the dll that is using Odbc32.dll. That's nice but how does one go about removing the Freelibrary call? Is there another fix for this problem? They hinted there was at the following site: http://support.microsoft.com/default.aspx?scid=kb;EN-- http://support.microsoft.com/default.aspx?scid=kb;EN- US;814410 Any help would be greatly appreciated. Thanks in advance. Eric O. . . -- Posted via http://dbforums.com |
![]() |
| Thread Tools | |
| Display Modes | |
| |