dts import agent: executing

Showing posts with label executing. Show all posts

Sunday, March 25, 2012

DTS Executable error

We just installed SP3. The problem is that when I'm executing a DTS package
remotely from my client machine, it bombs when on the task that call an exe
cutable (error #128).
I don't get this error when I execute the DTS on the Server.
ThanksDavid,
If you can't install SQL client tools on the client machine, you're going to
have fun now.
Visit: http://www.sqldts.com/default.aspx?6,105,225,0,1
James Hokes
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:6529CE21-68FF-4394-B2F3-0C3AF9F93959@.microsoft.com...

quote:

> We just installed SP3. The problem is that when I'm executing a DTS

package remotely from my client machine, it bombs when on the task that call
an executable (error #128).

quote:

> I don't get this error when I execute the DTS on the Server.
> Thanks

sql

DTS Executable error

We just installed SP3. The problem is that when I'm executing a DTS package remotely from my client machine, it bombs when on the task that call an executable (error #128)
I don't get this error when I execute the DTS on the Server
ThanksDavid,
If you can't install SQL client tools on the client machine, you're going to
have fun now.
Visit: http://www.sqldts.com/default.aspx?6,105,225,0,1
James Hokes
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:6529CE21-68FF-4394-B2F3-0C3AF9F93959@.microsoft.com...
> We just installed SP3. The problem is that when I'm executing a DTS
package remotely from my client machine, it bombs when on the task that call
an executable (error #128).
> I don't get this error when I execute the DTS on the Server.
> Thanks

DTS error when Copying Objects

I am getting the following error when executing a Copy SQL Server Objects Task. If it helps these objects are User Defined functions and also this had worked in the past it is only after changing the destination server to one that is offsite, has a different OS then the source and also runs as a DC. We are running SQL 2000 Server Standard with Spk 3a on both boxes.

Step 'DTSStep_DTSTransferObjectsTask_6' failed

Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 42S02)
Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetRightsAbbreviations'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetRights'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetTerritoryAbbreviations'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetTerritories'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetShow'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetTvEpisodes'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetTvSegments'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetTvSegmentsString'.
Step Error code: 800400D0
Step Error Help File:SQLDMO80.hlp
Step Error Help Context ID:1131Check object owner. This is the most common reason which is clearly seen from the error message you provided.sql

DTS Error 1st Time

Hi All,
I am executing a DTS Package from with in a Stored Procedure Like:
SET @.CMD = 'DTSRUN /S ' + @.SERVERNAME + ' /E /N ' + @.DTSNAME + ' ' +
@.GLOBLEVARIABLELIST + ''
EXECUTE @.ERR_NUM = master..xp_cmdshell @.CMD
The 1st Time when I call Stored procedure from My Code. It is Not Executing
the Package. But 2nd time onward that is executing the package and doing all
what ever i want to do.
What is happening in 1st time so that the package is fails? Is that setting
any environment in 1st time and executing the Package from 2nd time onward.
I am too Confused. Need Help.
Thanks
Prabhat
You've posted this at least 6 times already. Have you considered posting to
the DTS group, or having some patience?
http://www.aspfaq.com/
(Reverse address to reply.)
"Prabhat" <not_a_mail@.hotmail.com> wrote in message
news:#pWPr#kSEHA.1368@.TK2MSFTNGP11.phx.gbl...
> Hi All,
> I am executing a DTS Package from with in a Stored Procedure Like:
> SET @.CMD = 'DTSRUN /S ' + @.SERVERNAME + ' /E /N ' + @.DTSNAME + ' ' +
> @.GLOBLEVARIABLELIST + ''
> EXECUTE @.ERR_NUM = master..xp_cmdshell @.CMD
> The 1st Time when I call Stored procedure from My Code. It is Not
Executing
> the Package. But 2nd time onward that is executing the package and doing
all
> what ever i want to do.
> What is happening in 1st time so that the package is fails? Is that
setting
> any environment in 1st time and executing the Package from 2nd time
onward.
> I am too Confused. Need Help.
> Thanks
> Prabhat
>
>

DTS Error 1st Time

Hi All,
I am executing a DTS Package from with in a Stored Procedure Like:
SET @.CMD = 'DTSRUN /S ' + @.SERVERNAME + ' /E /N ' + @.DTSNAME + ' ' +
@.GLOBLEVARIABLELIST + ''
EXECUTE @.ERR_NUM = master..xp_cmdshell @.CMD
The 1st Time when I call Stored procedure from My Code. It is Not Executing
the Package. But 2nd time onward that is executing the package and doing all
what ever i want to do.
What is happening in 1st time so that the package is fails? Is that setting
any environment in 1st time and executing the Package from 2nd time onward.
I am too Confused. Need Help.
Thanks
PrabhatYou've posted this at least 6 times already. Have you considered posting to
the DTS group, or having some patience?
http://www.aspfaq.com/
(Reverse address to reply.)
"Prabhat" <not_a_mail@.hotmail.com> wrote in message
news:#pWPr#kSEHA.1368@.TK2MSFTNGP11.phx.gbl...
> Hi All,
> I am executing a DTS Package from with in a Stored Procedure Like:
> SET @.CMD = 'DTSRUN /S ' + @.SERVERNAME + ' /E /N ' + @.DTSNAME + ' ' +
> @.GLOBLEVARIABLELIST + ''
> EXECUTE @.ERR_NUM = master..xp_cmdshell @.CMD
> The 1st Time when I call Stored procedure from My Code. It is Not
Executing
> the Package. But 2nd time onward that is executing the package and doing
all
> what ever i want to do.
> What is happening in 1st time so that the package is fails? Is that
setting
> any environment in 1st time and executing the Package from 2nd time
onward.
> I am too Confused. Need Help.
> Thanks
> Prabhat
>
>sql

DTS Error 1st Time

Hi All,
I am executing a DTS Package from with in a Stored Procedure Like:
SET @.CMD = 'DTSRUN /S ' + @.SERVERNAME + ' /E /N ' + @.DTSNAME + ' ' +
@.GLOBLEVARIABLELIST + ''
EXECUTE @.ERR_NUM = master..xp_cmdshell @.CMD
The 1st Time when I call Stored procedure from My Code. It is Not Executing
the Package. But 2nd time onward that is executing the package and doing all
what ever i want to do.
What is happening in 1st time so that the package is fails? Is that setting
any environment in 1st time and executing the Package from 2nd time onward.
I am too Confused. Need Help.
Thanks
PrabhatYou've posted this at least 6 times already. Have you considered posting to
the DTS group, or having some patience?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Prabhat" <not_a_mail@.hotmail.com> wrote in message
news:#pWPr#kSEHA.1368@.TK2MSFTNGP11.phx.gbl...
> Hi All,
> I am executing a DTS Package from with in a Stored Procedure Like:
> SET @.CMD = 'DTSRUN /S ' + @.SERVERNAME + ' /E /N ' + @.DTSNAME + ' ' +
> @.GLOBLEVARIABLELIST + ''
> EXECUTE @.ERR_NUM = master..xp_cmdshell @.CMD
> The 1st Time when I call Stored procedure from My Code. It is Not
Executing
> the Package. But 2nd time onward that is executing the package and doing
all
> what ever i want to do.
> What is happening in 1st time so that the package is fails? Is that
setting
> any environment in 1st time and executing the Package from 2nd time
onward.
> I am too Confused. Need Help.
> Thanks
> Prabhat
>
>

Wednesday, March 21, 2012

DTS bulk load fails

Hi,
while executing a bulk insert DTS task, we sometimes experience an
'EXCEPTION_ACCESS_VIOLATION' error. We load several text files
into sql tables parrallel. The error occurs does not necessarily occur
on the same bulk load task, every we test the dts package. Sometimes
we don't even get the error at all.
We're running on sql server 2000 sp3 , any input or advice on this matter
would be highly appreciated.
Please find below the stack dump file...
Regards,
Erwin
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server 8.00.760
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is IBM - 1000
IBM BIOS Ver 1.05
Current time is 03:00:33 12/24/05.
4 Intel x86 level 15, 3000 Mhz processor(s).
Windows NT 5.2 Build 3790 CSD .
Memory
MemoryLoad = 60%
Total Physical = 3583 MB
Available Physical = 1403 MB
Total Page File = 5474 MB
Available Page File = 3466 MB
Total Virtual = 2047 MB
Available Virtual = 236 MB
*Stack Dump being sent to e:\MSSQL\log\SQLDump0001.txt
*
*****************************************************************************
**
*
* BEGIN STACK DUMP:
* 12/24/05 03:00:33 spid 61
*
* Exception Address = 06B824C5 (DDCS_Enter + 00000004 Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 06E1FF2C
* Input Buffer 468 bytes -
* BULK INSERT S_Import_IncrementalStock_InsertUpdates FROM 'e:\MerRep_Data
* \Work\DwMerchandise_UKwms_Batch00481_IncrementalStock_InsertUpdates.txt'
* WITH (CODEPAGE = 'RAW' , FIELDTERMINATOR = 'Â¿Â¿' , ROWTERMINATOR = ' ' ,
* MAXERRORS = 10 )
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00B2CFFF 0072d000
* ntdll 77F40000 77FF9FFF 000ba000
* kernel32 77E40000 77F33FFF 000f4000
* ADVAPI32 77DA0000 77E2FFFF 00090000
* RPCRT4 77C50000 77CF4FFF 000a5000
* USER32 77D00000 77D8EFFF 0008f000
* GDI32 77C00000 77C43FFF 00044000
* OPENDS60 41060000 41065FFF 00006000
* MSVCRT 77BA0000 77BF3FFF 00054000
* UMS 41070000 4107CFFF 0000d000
* SQLSORT 42AE0000 42B6FFFF 00090000
* MSVCIRT 60020000 6002FFFF 00010000
* sqlevn70 41080000 41086FFF 00007000
* NETAPI32 02C60000 02CB2FFF 00053000
* ole32 030D0000 031F4FFF 00125000
* XOLEHLP 03200000 03205FFF 00006000
* MSDTCPRX 03210000 03281FFF 00072000
* OLEAUT32 03290000 0330CFFF 0007d000
* MSVCP60 03310000 03370FFF 00061000
* MTXCLU 03380000 03397FFF 00018000
* VERSION 033A0000 033A7FFF 00008000
* WSOCK32 033B0000 033B8FFF 00009000
* WS2_32 033C0000 033D7FFF 00018000
* WS2HELP 033E0000 033E7FFF 00008000
* CLUSAPI 03430000 03440FFF 00011000
* RESUTILS 03450000 03461FFF 00012000
* USERENV 03470000 03529FFF 000ba000
* MFC42u 03530000 03623FFF 000f4000
* secur32 036B0000 036C2FFF 00013000
* mswsock 036E0000 03722FFF 00043000
* DNSAPI 03730000 03756FFF 00027000
* winrnr 037A0000 037A6FFF 00007000
* WLDAP32 037B0000 037DEFFF 0002f000
* rasadhlp 03800000 03804FFF 00005000
* SSNETLIB 00C70000 00C84FFF 00015000
* SSNMPN70 00C90000 00C95FFF 00006000
* security 042C0000 042C3FFF 00004000
* wshtcpip 04310000 04317FFF 00008000
* SSmsLPCn 04320000 04326FFF 00007000
* ntdsapi 04340000 04355FFF 00016000
* kerberos 04770000 047C5FFF 00056000
* cryptdll 047D0000 047DBFFF 0000c000
* MSASN1 047E0000 047F1FFF 00012000
* SQLFTQRY 04630000 04661FFF 00032000
* CLBCatQ 04B20000 04B9DFFF 0007e000
* COMRes 04BA0000 04C65FFF 000c6000
* sqloledb 04C90000 04D15FFF 00086000
* MSDART 04D20000 04D48FFF 00029000
* COMCTL32 04D50000 04DDFFFF 00090000
* comdlg32 04DE0000 04E26FFF 00047000
* SHLWAPI 04E30000 04E78FFF 00049000
* SHELL32 04E80000 0565DFFF 007de000
* MSDATL3 05660000 05677FFF 00018000
* comctl32 05690000 05775FFF 000e6000
* oledb32 05B20000 05B9CFFF 0007d000
* OLEDB32R 05BA0000 05BB0FFF 00011000
* msv1_0 05C50000 05C73FFF 00024000
* xpsqlbot 05C80000 05C85FFF 00006000
* xpstar 05CB0000 05CF6FFF 00047000
* SQLRESLD 05D00000 05D06FFF 00007000
* SQLSVC 05D10000 05D26FFF 00017000
* ODBC32 05D30000 05D69FFF 0003a000
* odbcbcp 05D70000 05D75FFF 00006000
* W95SCM 05D90000 05D9BFFF 0000c000
* SQLUNIRL 05DA0000 05DCCFFF 0002d000
* WINSPOOL 05DD0000 05DF5FFF 00026000
* SHFOLDER 05E00000 05E08FFF 00009000
* odbcint 05FF0000 06006FFF 00017000
* NDDEAPI 06110000 06116FFF 00007000
* SQLSVC 06120000 06125FFF 00006000
* xpstar 06130000 06138FFF 00009000
* rsaenh 0FFD0000 0FFFCFFF 0002d000
* PSAPI 05D80000 05D8AFFF 0000b000
* impprov 065D0000 065E8FFF 00019000
* sqlmap70 06580000 065A9FFF 0002a000
* MAPI32 065B0000 065CEFFF 0001f000
* MSMAPI32 06B80000 06CCDFFF 0014e000
* mso 07510000 080C1FFF 00bb2000
* iphlpapi 06F20000 06F36FFF 00017000
* MPRAPI 08270000 08286FFF 00017000
* ACTIVEDS 08290000 082C1FFF 00032000
* adsldpc 082D0000 082F5FFF 00026000
* credui 08300000 0832CFFF 0002d000
* ATL 08330000 08347FFF 00018000
* rtutils 08350000 0835AFFF 0000b000
* SAMLIB 08360000 0836FFFF 00010000
* SETUPAPI 08370000 0846FFFF 00100000
* netman 084D0000 08506FFF 00037000
* RASAPI32 08510000 0854AFFF 0003b000
* rasman 08550000 08560FFF 00011000
* TAPI32 08570000 0859DFFF 0002e000
* WINMM 085A0000 085CBFFF 0002c000
* CRYPT32 085D0000 08667FFF 00098000
* WZCSvc 08670000 086B6FFF 00047000
* WMI 08470000 08474FFF 00005000
* DHCPCSVC 086C0000 086DBFFF 0001c000
* WTSAPI32 086E0000 086E7FFF 00008000
* WINSTA 086F0000 086FFFFF 00010000
* ESENT 08700000 08807FFF 00108000
* WZCSAPI 08810000 08818FFF 00009000
* xplog70 06560000 06571FFF 00012000
* xplog70 09160000 09163FFF 00004000
* sqlvdi 09170000 0917BFFF 0000c000
* msi 0AA10000 0AC23FFF 00214000
* MAPIR 06F50000 0700FFFF 000c0000
* contab32 030B0000 030CEFFF 0001f000
* EMSABP32 06DA0000 06DD7FFF 00038000
* EMSMDB32 08F60000 09019FFF 000ba000
* uxtheme 09120000 09152FFF 00033000
* dbghelp 09720000 097D4FFF 000b5000
*
* Edi: 06E1FF14:
* Esi: 06E1FEF8:
* Eax: C0000000:
* Ebx: 00000000:
* Ecx: 06E1FF14:
* Edx: 00000020:
* Eip: 06B824C5:
* Ebp: 0A30EDF4: 0A30EE20 77D0612F 00EC019E 00000507 06E1FEF8
00000
000
* SegCs: 0000001B:
* EFlags: 00010246: 006D0065 00320033 0057005C 00650062 003B006D
003A0
043
* Esp: 0A30EDD8: 06B86F6F 06E1FF14 0A30EE6C 06E1FEF8 06B8510A
06E1F
EF8
* SegSs: 00000023:
*
*****************************************************************************
**
*
----
--
* Short Stack Dump
* 06B824C5 Module(MSMAPI32+000024C5) (DDCS_Enter+00000004)
* 77D0612F Module(USER32+0000612F)
* 77D069A5 Module(USER32+000069A5) (GetMessageW+000001EE)
* 77D06689 Module(USER32+00006689) (TranslateMessage+00000520)
* 77D0FAE4 Module(USER32+0000FAE4) (DispatchMessageA+0000000B)
* 065D2BB3 Module(impprov+00002BB3)
* 065DE84A Module(impprov+0000E84A) (DllRegisterServer+0000AA3A)
* 065E145C Module(impprov+0001145C) (DllRegisterServer+0000D64C)
* 065DE1DC Module(impprov+0000E1DC) (DllRegisterServer+0000A3CC)
* 0047E663 Module(sqlservr+0007E663)
(CBcpImport::CreateInprocProvider+000002EF
)
* 0047DB5A Module(sqlservr+0007DB5A) (CBcpImport::Init+0000029D)
* 0047D854 Module(sqlservr+0007D854) (BcpImportMain+0000014D)
* 0047D714 Module(sqlservr+0007D714) (CStmtBulkIns::XretExecute+0000005F)
* 0041B442 Module(sqlservr+0001B442)
(CMsqlExecContext::ExecuteStmts+000003B9)
* 0041AA88 Module(sqlservr+0001AA88) (CMsqlExecContext::Execute+000001B6)
* 0041B9B6 Module(sqlservr+0001B9B6) (CSQLSource::Execute+00000357)
* 0048A63B Module(sqlservr+0008A63B) (language_exec+000003E1)
* 0042708C Module(sqlservr+0002708C) (process_commands+0000010E)
* 41075002 Module(UMS+00005002) (ProcessWorkRequests+00000272)
* 41074698 Module(UMS+00004698) (ThreadStartRoutine+00000098)
* 77BC90A2 Module(MSVCRT+000290A2) (endthread+000000A6)
* 77E4A990 Module(kernel32+0000A990) (FlsSetValue+00000779)
----
* Location : 06B824C5 Module(MSMAPI32+000024C5) (DDCS_Enter+00000004)
* Return Addr: 77D0612F Module(USER32+0000612F)
Frame : 0A30EDF4
Parameters:
[1] 00EC019E: 00000240 00000000 00000000 00000000 00000000 00000000
[2] 00000507:
[3] 06E1FEF8:
[4] 00000000:
160 bytes of stack data from 0A30ED54 to 0A30EDF4
0A30ED54: 00000000 00000000 00000000 00000000 [............]
:::: 7 Duplicate lines detected
0A30EDD4: 00000000 06B86F6F 06E1FF14 0A30EE6C [...oo.....l.0.]
0A30EDE4: 06E1FEF8 06B8510A 06E1FEF8 06B850F4 [....Q......P..]
----
* Location : 77D0612F Module(USER32+0000612F)
* Return Addr: 77D069A5 Module(USER32+000069A5) (GetMessageW+000001EE)
Frame : 0A30EE20
Parameters:
[1] 06B850F4:
[2] 00EC019E: 00000240 00000000 00000000 00000000 00000000 00000000
[3] 00000507:
[4] 06E1FEF8:
44 bytes of stack data from 0A30EDF4 to 0A30EE20
0A30EDF4: 0A30EE20 77D0612F 00EC019E 00000507 [ .0./a.w......]
0A30EE04: 06E1FEF8 00000000 06B850F4 DCBAABCD [.......P.....]
0A30EE14: 00000000 0A30EE6C 06B850F4 [...l.0..P..]
..
PSS @.0x76D8D258
--
pspid = 61 m_dwLoginFlags = 0x1083e0 plsid = 1717878624
pbackground = 0
pbSid
--
01010000 00000005 12000000 .........
sSecFlags = 0x1e
pdeadlockpri = 0 poffsets = 0x0 pss_stats = 0x0
ptickcount = 1352914718 pcputickcount = 4059555816433772
ploginstamp = 10002 ptimestamp = 2005-12-24 03:00:33.530
plangid = 0 pdateformat = 1 pdatefirst = 7
Language = us_english UserName = NT AUTHORITY\SYSTEM
poptions = 0x28000020 poptions2 = 0x13f438 pline = 1
pcurstepno = 1 prowcount = 0 pstatlist = 0
pcurcmd = 240 pseqstat = 0 ptextsize = 2147483647
pretstat = 0 CNestLevel = 0 @.@.procid = 0
Xact_Begin_Time = 2005-12-24 03:00:33.543
pslastbatchstarttime = 2005-12-24 03:00:33.543 pmemusage = 5
hLicense = 0 tpFlags = 0x1 isolation_level = 0
fips_flag = 0x0 sSaveSecFlags = 0x0 psavedb = 0
pfetchstat = 0 pcrsrows = 0
pslastbatchtime = 2005-12-24 03:00:33.543 pNtUser = SYSTEM
pNtDomain = NT AUTHORITY pubexecdb = 0 fInReplicatedProcExec = 0
pMsqlXact = 0x76D8DE60 presSemCount = [0]170977488
presSemCount = [0]170977488 pcputot = 0
pcputotstart = 0 pcpucmdstart = 0 pbufread = 0
pbufreadstart = 0 plogbufread = 178 plogbufreadstart = 162
pbufwrite = 0 pbufwritestart = 0 pLockTimeout = 4294967295
pUtilResultSet = 0x00000000
pec
--
ec_pss->pspid = 61 ecid = 0 ec_stat = 0x0
ec_stat2 = 0x100001 ec_atomic = 0x0 pcurdb = 9
ec_lasterror = 0 ec_preverror = 0 ec_cpucur = 2408031
ec_cmderrs = 0 ec_timeslice = 84 ec_dbtable = 0x19EB0030
ec_reswait = 0x0 ec_dbindex = -1 ec_waittype = 0x0000
Waittime = 0 ec_umsContext->m_pSched->m_id (SchedulerId) = 0x2
ec_umsContext->m_workercntxt->m_id (threadId) = 0x9fc
ExecutionContext Summary @.0x76D8D580
--
ec_pss->pspid = 61 ecid = 0 ec_stat = 0x0
ec_stat2 = 0x100001 ec_atomic = 0x0 pcurdb = 9
ec_lasterror = 0 ec_preverror = 0 ec_cpucur = 2408031
ec_cmderrs = 0 ec_timeslice = 84 ec_dbtable = 0x19EB0030
ec_reswait = 0x0 ec_dbindex = -1 ec_waittype = 0x0000
Waittime = 0 ec_umsContext->m_pSched->m_id (SchedulerId) = 0x2
ec_umsContext->m_workercntxt->m_id (threadId) = 0x9fc
psrvproc->eclClient = 4 psrvproc->status = 8
psrvproc->state = SRV_RUNNING psrvproc->bNewPacket = 0
psrvproc->pmo = 0x76D84030
psrvproc->ums_context = 0x038A1950 psrvproc->threadId = 0x9fc
client threadId = 0xdc8
...Hi
This http://support.microsoft.com/default.aspx?scid=kb;en-us;839458 was
fixed after SP3, although you don't give any information about identity
values and I would not expect it to perform inconsistently as you describe;
but you may want to see if loading SP4 removes this issue. Something else you
may wish to try could be to run them all on the main thread.
John
"Erwin" wrote:
> Hi,
> while executing a bulk insert DTS task, we sometimes experience an
> 'EXCEPTION_ACCESS_VIOLATION' error. We load several text files
> into sql tables parrallel. The error occurs does not necessarily occur
> on the same bulk load task, every we test the dts package. Sometimes
> we don't even get the error at all.
> We're running on sql server 2000 sp3 , any input or advice on this matter
> would be highly appreciated.
> Please find below the stack dump file...
> Regards,
> Erwin
> =====================================================================> BugCheck Dump
> =====================================================================>
> This file is generated by Microsoft SQL Server 8.00.760
> upon detection of fatal unexpected error. Please return this file,
> the query or program that produced the bugcheck, the database and
> the error log, and any other pertinent information with a Service Request.
>
> Computer type is AT/AT COMPATIBLE.
> Bios Version is IBM - 1000
> IBM BIOS Ver 1.05
> Current time is 03:00:33 12/24/05.
> 4 Intel x86 level 15, 3000 Mhz processor(s).
> Windows NT 5.2 Build 3790 CSD .
>
> Memory
> MemoryLoad = 60%
> Total Physical = 3583 MB
> Available Physical = 1403 MB
> Total Page File = 5474 MB
> Available Page File = 3466 MB
> Total Virtual = 2047 MB
> Available Virtual = 236 MB
> *Stack Dump being sent to e:\MSSQL\log\SQLDump0001.txt
> *
> *****************************************************************************
> **
> *
> * BEGIN STACK DUMP:
> * 12/24/05 03:00:33 spid 61
> *
> * Exception Address = 06B824C5 (DDCS_Enter + 00000004 Line 0+00000000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address 06E1FF2C
> * Input Buffer 468 bytes -
> * BULK INSERT S_Import_IncrementalStock_InsertUpdates FROM 'e:\MerRep_Data
> * \Work\DwMerchandise_UKwms_Batch00481_IncrementalStock_InsertUpdates.txt'
> * WITH (CODEPAGE = 'RAW' , FIELDTERMINATOR = 'Â¿Â¿' , ROWTERMINATOR = ' ' ,
> * MAXERRORS = 10 )
> *
> *
> * MODULE BASE END SIZE
> * sqlservr 00400000 00B2CFFF 0072d000
> * ntdll 77F40000 77FF9FFF 000ba000
> * kernel32 77E40000 77F33FFF 000f4000
> * ADVAPI32 77DA0000 77E2FFFF 00090000
> * RPCRT4 77C50000 77CF4FFF 000a5000
> * USER32 77D00000 77D8EFFF 0008f000
> * GDI32 77C00000 77C43FFF 00044000
> * OPENDS60 41060000 41065FFF 00006000
> * MSVCRT 77BA0000 77BF3FFF 00054000
> * UMS 41070000 4107CFFF 0000d000
> * SQLSORT 42AE0000 42B6FFFF 00090000
> * MSVCIRT 60020000 6002FFFF 00010000
> * sqlevn70 41080000 41086FFF 00007000
> * NETAPI32 02C60000 02CB2FFF 00053000
> * ole32 030D0000 031F4FFF 00125000
> * XOLEHLP 03200000 03205FFF 00006000
> * MSDTCPRX 03210000 03281FFF 00072000
> * OLEAUT32 03290000 0330CFFF 0007d000
> * MSVCP60 03310000 03370FFF 00061000
> * MTXCLU 03380000 03397FFF 00018000
> * VERSION 033A0000 033A7FFF 00008000
> * WSOCK32 033B0000 033B8FFF 00009000
> * WS2_32 033C0000 033D7FFF 00018000
> * WS2HELP 033E0000 033E7FFF 00008000
> * CLUSAPI 03430000 03440FFF 00011000
> * RESUTILS 03450000 03461FFF 00012000
> * USERENV 03470000 03529FFF 000ba000
> * MFC42u 03530000 03623FFF 000f4000
> * secur32 036B0000 036C2FFF 00013000
> * mswsock 036E0000 03722FFF 00043000
> * DNSAPI 03730000 03756FFF 00027000
> * winrnr 037A0000 037A6FFF 00007000
> * WLDAP32 037B0000 037DEFFF 0002f000
> * rasadhlp 03800000 03804FFF 00005000
> * SSNETLIB 00C70000 00C84FFF 00015000
> * SSNMPN70 00C90000 00C95FFF 00006000
> * security 042C0000 042C3FFF 00004000
> * wshtcpip 04310000 04317FFF 00008000
> * SSmsLPCn 04320000 04326FFF 00007000
> * ntdsapi 04340000 04355FFF 00016000
> * kerberos 04770000 047C5FFF 00056000
> * cryptdll 047D0000 047DBFFF 0000c000
> * MSASN1 047E0000 047F1FFF 00012000
> * SQLFTQRY 04630000 04661FFF 00032000
> * CLBCatQ 04B20000 04B9DFFF 0007e000
> * COMRes 04BA0000 04C65FFF 000c6000
> * sqloledb 04C90000 04D15FFF 00086000
> * MSDART 04D20000 04D48FFF 00029000
> * COMCTL32 04D50000 04DDFFFF 00090000
> * comdlg32 04DE0000 04E26FFF 00047000
> * SHLWAPI 04E30000 04E78FFF 00049000
> * SHELL32 04E80000 0565DFFF 007de000
> * MSDATL3 05660000 05677FFF 00018000
> * comctl32 05690000 05775FFF 000e6000
> * oledb32 05B20000 05B9CFFF 0007d000
> * OLEDB32R 05BA0000 05BB0FFF 00011000
> * msv1_0 05C50000 05C73FFF 00024000
> * xpsqlbot 05C80000 05C85FFF 00006000
> * xpstar 05CB0000 05CF6FFF 00047000
> * SQLRESLD 05D00000 05D06FFF 00007000
> * SQLSVC 05D10000 05D26FFF 00017000
> * ODBC32 05D30000 05D69FFF 0003a000
> * odbcbcp 05D70000 05D75FFF 00006000
> * W95SCM 05D90000 05D9BFFF 0000c000
> * SQLUNIRL 05DA0000 05DCCFFF 0002d000
> * WINSPOOL 05DD0000 05DF5FFF 00026000
> * SHFOLDER 05E00000 05E08FFF 00009000
> * odbcint 05FF0000 06006FFF 00017000
> * NDDEAPI 06110000 06116FFF 00007000
> * SQLSVC 06120000 06125FFF 00006000
> * xpstar 06130000 06138FFF 00009000
> * rsaenh 0FFD0000 0FFFCFFF 0002d000
> * PSAPI 05D80000 05D8AFFF 0000b000
> * impprov 065D0000 065E8FFF 00019000
> * sqlmap70 06580000 065A9FFF 0002a000
> * MAPI32 065B0000 065CEFFF 0001f000
> * MSMAPI32 06B80000 06CCDFFF 0014e000
> * mso 07510000 080C1FFF 00bb2000
> * iphlpapi 06F20000 06F36FFF 00017000
> * MPRAPI 08270000 08286FFF 00017000
> * ACTIVEDS 08290000 082C1FFF 00032000
> * adsldpc 082D0000 082F5FFF 00026000
> * credui 08300000 0832CFFF 0002d000
> * ATL 08330000 08347FFF 00018000
> * rtutils 08350000 0835AFFF 0000b000
> * SAMLIB 08360000 0836FFFF 00010000
> * SETUPAPI 08370000 0846FFFF 00100000
> * netman 084D0000 08506FFF 00037000
> * RASAPI32 08510000 0854AFFF 0003b000
> * rasman 08550000 08560FFF 00011000
> * TAPI32 08570000 0859DFFF 0002e000
> * WINMM 085A0000 085CBFFF 0002c000
> * CRYPT32 085D0000 08667FFF 00098000
> * WZCSvc 08670000 086B6FFF 00047000
> * WMI 08470000 08474FFF 00005000
> * DHCPCSVC 086C0000 086DBFFF 0001c000
> * WTSAPI32 086E0000 086E7FFF 00008000
> * WINSTA 086F0000 086FFFFF 00010000
> * ESENT 08700000 08807FFF 00108000
> * WZCSAPI 08810000 08818FFF 00009000
> * xplog70 06560000 06571FFF 00012000
> * xplog70 09160000 09163FFF 00004000
> * sqlvdi 09170000 0917BFFF 0000c000
>

DTS bulk load fails

Hi,
while executing a bulk insert DTS task, we sometimes experience an
'EXCEPTION_ACCESS_VIOLATION' error. We load several text files
into sql tables parrallel. The error occurs does not necessarily occur
on the same bulk load task, every we test the dts package. Sometimes
we don't even get the error at all.
We're running on sql server 2000 sp3 , any input or advice on this matter
would be highly appreciated.
Please find below the stack dump file...
Regards,
Erwin
========================================
=============================
BugCheck Dump
========================================
=============================
This file is generated by Microsoft SQL Server 8.00.760
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is IBM - 1000
IBM BIOS Ver 1.05
Current time is 03:00:33 12/24/05.
4 Intel x86 level 15, 3000 Mhz processor(s).
Windows NT 5.2 Build 3790 CSD .
Memory
MemoryLoad = 60%
Total Physical = 3583 MB
Available Physical = 1403 MB
Total Page File = 5474 MB
Available Page File = 3466 MB
Total Virtual = 2047 MB
Available Virtual = 236 MB
*Stack Dump being sent to e:\MSSQL\log\SQLDump0001.txt
*
****************************************
************************************
*
**
*
* BEGIN STACK DUMP:
* 12/24/05 03:00:33 spid 61
*
* Exception Address = 06B824C5 (DDCS_Enter + 00000004 Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 06E1FF2C
* Input Buffer 468 bytes -
* BULK INSERT S_Import_IncrementalStock_InsertUpdates FROM 'e:\MerRep_Data
* \Work\DwMerchandise_UKwms_Batch00481_Inc
rementalStock_InsertUpdates.txt'
* WITH (CODEPAGE = 'RAW' , FIELDTERMINATOR = '??' , ROWTERMINATOR = ' '
,
* MAXERRORS = 10 )
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00B2CFFF 0072d000
* ntdll 77F40000 77FF9FFF 000ba000
* kernel32 77E40000 77F33FFF 000f4000
* ADVAPI32 77DA0000 77E2FFFF 00090000
* RPCRT4 77C50000 77CF4FFF 000a5000
* USER32 77D00000 77D8EFFF 0008f000
* GDI32 77C00000 77C43FFF 00044000
* OPENDS60 41060000 41065FFF 00006000
* MSVCRT 77BA0000 77BF3FFF 00054000
* UMS 41070000 4107CFFF 0000d000
* SQLSORT 42AE0000 42B6FFFF 00090000
* MSVCIRT 60020000 6002FFFF 00010000
* sqlevn70 41080000 41086FFF 00007000
* NETAPI32 02C60000 02CB2FFF 00053000
* ole32 030D0000 031F4FFF 00125000
* XOLEHLP 03200000 03205FFF 00006000
* MSDTCPRX 03210000 03281FFF 00072000
* OLEAUT32 03290000 0330CFFF 0007d000
* MSVCP60 03310000 03370FFF 00061000
* MTXCLU 03380000 03397FFF 00018000
* VERSION 033A0000 033A7FFF 00008000
* WSOCK32 033B0000 033B8FFF 00009000
* WS2_32 033C0000 033D7FFF 00018000
* WS2HELP 033E0000 033E7FFF 00008000
* CLUSAPI 03430000 03440FFF 00011000
* RESUTILS 03450000 03461FFF 00012000
* USERENV 03470000 03529FFF 000ba000
* MFC42u 03530000 03623FFF 000f4000
* secur32 036B0000 036C2FFF 00013000
* mswsock 036E0000 03722FFF 00043000
* DNSAPI 03730000 03756FFF 00027000
* winrnr 037A0000 037A6FFF 00007000
* WLDAP32 037B0000 037DEFFF 0002f000
* rasadhlp 03800000 03804FFF 00005000
* SSNETLIB 00C70000 00C84FFF 00015000
* SSNMPN70 00C90000 00C95FFF 00006000
* security 042C0000 042C3FFF 00004000
* wshtcpip 04310000 04317FFF 00008000
* SSmsLPCn 04320000 04326FFF 00007000
* ntdsapi 04340000 04355FFF 00016000
* kerberos 04770000 047C5FFF 00056000
* cryptdll 047D0000 047DBFFF 0000c000
* MSASN1 047E0000 047F1FFF 00012000
* SQLFTQRY 04630000 04661FFF 00032000
* CLBCatQ 04B20000 04B9DFFF 0007e000
* COMRes 04BA0000 04C65FFF 000c6000
* sqloledb 04C90000 04D15FFF 00086000
* MSDART 04D20000 04D48FFF 00029000
* COMCTL32 04D50000 04DDFFFF 00090000
* comdlg32 04DE0000 04E26FFF 00047000
* SHLWAPI 04E30000 04E78FFF 00049000
* SHELL32 04E80000 0565DFFF 007de000
* MSDATL3 05660000 05677FFF 00018000
* comctl32 05690000 05775FFF 000e6000
* oledb32 05B20000 05B9CFFF 0007d000
* OLEDB32R 05BA0000 05BB0FFF 00011000
* msv1_0 05C50000 05C73FFF 00024000
* xpsqlbot 05C80000 05C85FFF 00006000
* xpstar 05CB0000 05CF6FFF 00047000
* SQLRESLD 05D00000 05D06FFF 00007000
* SQLSVC 05D10000 05D26FFF 00017000
* ODBC32 05D30000 05D69FFF 0003a000
* odbcbcp 05D70000 05D75FFF 00006000
* W95SCM 05D90000 05D9BFFF 0000c000
* SQLUNIRL 05DA0000 05DCCFFF 0002d000
* WINSPOOL 05DD0000 05DF5FFF 00026000
* SHFOLDER 05E00000 05E08FFF 00009000
* odbcint 05FF0000 06006FFF 00017000
* NDDEAPI 06110000 06116FFF 00007000
* SQLSVC 06120000 06125FFF 00006000
* xpstar 06130000 06138FFF 00009000
* rsaenh 0FFD0000 0FFFCFFF 0002d000
* PSAPI 05D80000 05D8AFFF 0000b000
* impprov 065D0000 065E8FFF 00019000
* sqlmap70 06580000 065A9FFF 0002a000
* MAPI32 065B0000 065CEFFF 0001f000
* MSMAPI32 06B80000 06CCDFFF 0014e000
* mso 07510000 080C1FFF 00bb2000
* iphlpapi 06F20000 06F36FFF 00017000
* MPRAPI 08270000 08286FFF 00017000
* ACTIVEDS 08290000 082C1FFF 00032000
* adsldpc 082D0000 082F5FFF 00026000
* credui 08300000 0832CFFF 0002d000
* ATL 08330000 08347FFF 00018000
* rtutils 08350000 0835AFFF 0000b000
* SAMLIB 08360000 0836FFFF 00010000
* SETUPAPI 08370000 0846FFFF 00100000
* netman 084D0000 08506FFF 00037000
* RASAPI32 08510000 0854AFFF 0003b000
* rasman 08550000 08560FFF 00011000
* TAPI32 08570000 0859DFFF 0002e000
* WINMM 085A0000 085CBFFF 0002c000
* CRYPT32 085D0000 08667FFF 00098000
* WZCSvc 08670000 086B6FFF 00047000
* WMI 08470000 08474FFF 00005000
* DHCPCSVC 086C0000 086DBFFF 0001c000
* WTSAPI32 086E0000 086E7FFF 00008000
* WINSTA 086F0000 086FFFFF 00010000
* ESENT 08700000 08807FFF 00108000
* WZCSAPI 08810000 08818FFF 00009000
* xplog70 06560000 06571FFF 00012000
* xplog70 09160000 09163FFF 00004000
* sqlvdi 09170000 0917BFFF 0000c000
* msi 0AA10000 0AC23FFF 00214000
* MAPIR 06F50000 0700FFFF 000c0000
* contab32 030B0000 030CEFFF 0001f000
* EMSABP32 06DA0000 06DD7FFF 00038000
* EMSMDB32 08F60000 09019FFF 000ba000
* uxtheme 09120000 09152FFF 00033000
* dbghelp 09720000 097D4FFF 000b5000
*
* Edi: 06E1FF14:
* Esi: 06E1FEF8:
* Eax: C0000000:
* Ebx: 00000000:
* Ecx: 06E1FF14:
* Edx: 00000020:
* Eip: 06B824C5:
* Ebp: 0A30EDF4: 0A30EE20 77D0612F 00EC019E 00000507 06E1FEF8
00000
000
* SegCs: 0000001B:
* EFlags: 00010246: 006D0065 00320033 0057005C 00650062 003B006D
003A0
043
* Esp: 0A30EDD8: 06B86F6F 06E1FF14 0A30EE6C 06E1FEF8 06B8510A
06E1F
EF8
* SegSs: 00000023:
*
****************************************
************************************
*
**
*
----
-
--
* Short Stack Dump
* 06B824C5 Module(MSMAPI32+000024C5) (DDCS_Enter+00000004)
* 77D0612F Module(USER32+0000612F)
* 77D069A5 Module(USER32+000069A5) (GetMessageW+000001EE)
* 77D06689 Module(USER32+00006689) (TranslateMessage+00000520)
* 77D0FAE4 Module(USER32+0000FAE4) (DispatchMessageA+0000000B)
* 065D2BB3 Module(impprov+00002BB3)
* 065DE84A Module(impprov+0000E84A) (DllRegisterServer+0000AA3A)
* 065E145C Module(impprov+0001145C) (DllRegisterServer+0000D64C)
* 065DE1DC Module(impprov+0000E1DC) (DllRegisterServer+0000A3CC)
* 0047E663 Module(sqlservr+0007E663)
(CBcpImport::CreateInprocProvider+000002
EF
)
* 0047DB5A Module(sqlservr+0007DB5A) (CBcpImport::Init+0000029D)
* 0047D854 Module(sqlservr+0007D854) (BcpImportMain+0000014D)
* 0047D714 Module(sqlservr+0007D714) (CStmtBulkIns::XretExecute+0000005F)
* 0041B442 Module(sqlservr+0001B442)
(CMsqlExecContext::ExecuteStmts+000003B9
)
* 0041AA88 Module(sqlservr+0001AA88) (CMsqlExecContext::Execute+000001B6)
* 0041B9B6 Module(sqlservr+0001B9B6) (CSQLSource::Execute+00000357)
* 0048A63B Module(sqlservr+0008A63B) (language_exec+000003E1)
* 0042708C Module(sqlservr+0002708C) (process_commands+0000010E)
* 41075002 Module(UMS+00005002) (ProcessWorkRequests+00000272)
* 41074698 Module(UMS+00004698) (ThreadStartRoutine+00000098)
* 77BC90A2 Module(MSVCRT+000290A2) (endthread+000000A6)
* 77E4A990 Module(kernel32+0000A990) (FlsSetValue+00000779)
----
--
* Location : 06B824C5 Module(MSMAPI32+000024C5) (DDCS_Enter+00000004)
* Return Addr: 77D0612F Module(USER32+0000612F)
Frame : 0A30EDF4
Parameters:
[1] 00EC019E: 00000240 00000000 00000000 00000000 00000000 00000000
[2] 00000507:
[3] 06E1FEF8:
[4] 00000000:
160 bytes of stack data from 0A30ED54 to 0A30EDF4
0A30ED54: 00000000 00000000 00000000 00000000 [............]
:::: 7 Duplicate lines detected
0A30EDD4: 00000000 06B86F6F 06E1FF14 0A30EE6C [...oo.....l.0.]
0A30EDE4: 06E1FEF8 06B8510A 06E1FEF8 06B850F4 [....Q......P..]
----
--
* Location : 77D0612F Module(USER32+0000612F)
* Return Addr: 77D069A5 Module(USER32+000069A5) (GetMessageW+000001EE)
Frame : 0A30EE20
Parameters:
[1] 06B850F4:
[2] 00EC019E: 00000240 00000000 00000000 00000000 00000000 00000000
[3] 00000507:
[4] 06E1FEF8:
44 bytes of stack data from 0A30EDF4 to 0A30EE20
0A30EDF4: 0A30EE20 77D0612F 00EC019E 00000507 [ .0./a.w......]
0A30EE04: 06E1FEF8 00000000 06B850F4 DCBAABCD [.......P.....]
0A30EE14: 00000000 0A30EE6C 06B850F4 [...l.0..P..]
.
PSS @.0x76D8D258
--
pspid = 61 m_dwLoginFlags = 0x1083e0 plsid = 1717878624
pbackground = 0
pbSid
--
01010000 00000005 12000000 .........
sSecFlags = 0x1e
pdeadlockpri = 0 poffsets = 0x0 pss_stats = 0x0
ptickcount = 1352914718 pcputickcount = 4059555816433772
ploginstamp = 10002 ptimestamp = 2005-12-24 03:00:33.530
plangid = 0 pdateformat = 1 pdatefirst = 7
Language = us_english UserName = NT AUTHORITY\SYSTEM
poptions = 0x28000020 poptions2 = 0x13f438 pline = 1
pcurstepno = 1 prowcount = 0 pstatlist = 0
pcurcmd = 240 pseqstat = 0 ptextsize = 2147483647
pretstat = 0 CNestLevel = 0 @.@.procid = 0
Xact_Begin_Time = 2005-12-24 03:00:33.543
pslastbatchstarttime = 2005-12-24 03:00:33.543 pmemusage = 5
hLicense = 0 tpFlags = 0x1 isolation_level = 0
fips_flag = 0x0 sSaveSecFlags = 0x0 psavedb = 0
pfetchstat = 0 pcrsrows = 0
pslastbatchtime = 2005-12-24 03:00:33.543 pNtUser = SYSTEM
pNtDomain = NT AUTHORITY pubexecdb = 0 fInReplicatedProcExec =
0
pMsqlXact = 0x76D8DE60 presSemCount = [0]170977488
presSemCount = [0]170977488 pcputot = 0
pcputotstart = 0 pcpucmdstart = 0 pbufread = 0
pbufreadstart = 0 plogbufread = 178 plogbufreadstart = 162
pbufwrite = 0 pbufwritestart = 0 pLockTimeout =
4294967295
pUtilResultSet = 0x00000000
pec
--
ec_pss->pspid = 61 ecid = 0 ec_stat = 0x0
ec_stat2 = 0x100001 ec_atomic = 0x0 pcurdb = 9
ec_lasterror = 0 ec_preverror = 0 ec_cpucur = 2408031
ec_cmderrs = 0 ec_timeslice = 84 ec_dbtable = 0x19EB0030
ec_reswait = 0x0 ec_dbindex = -1 ec_waittype = 0x0000
Waittime = 0 ec_umsContext->m_pSched->m_id (SchedulerId) = 0x2
ec_umsContext->m_workercntxt->m_id (threadId) = 0x9fc
ExecutionContext Summary @.0x76D8D580
--
ec_pss->pspid = 61 ecid = 0 ec_stat = 0x0
ec_stat2 = 0x100001 ec_atomic = 0x0 pcurdb = 9
ec_lasterror = 0 ec_preverror = 0 ec_cpucur = 2408031
ec_cmderrs = 0 ec_timeslice = 84 ec_dbtable = 0x19EB0030
ec_reswait = 0x0 ec_dbindex = -1 ec_waittype = 0x0000
Waittime = 0 ec_umsContext->m_pSched->m_id (SchedulerId) = 0x2
ec_umsContext->m_workercntxt->m_id (threadId) = 0x9fc
psrvproc->eclClient = 4 psrvproc->status = 8
psrvproc->state = SRV_RUNNING psrvproc->bNewPacket = 0
psrvproc->pmo = 0x76D84030
psrvproc->ums_context = 0x038A1950 psrvproc->threadId =
0x9fc
client threadId = 0xdc8
...Hi
This http://support.microsoft.com/defaul...kb;en-us;839458 was
fixed after SP3, although you don't give any information about identity
values and I would not expect it to perform inconsistently as you describe;
but you may want to see if loading SP4 removes this issue. Something else yo
u
may wish to try could be to run them all on the main thread.
John
"Erwin" wrote:

> Hi,
> while executing a bulk insert DTS task, we sometimes experience an
> 'EXCEPTION_ACCESS_VIOLATION' error. We load several text files
> into sql tables parrallel. The error occurs does not necessarily occur
> on the same bulk load task, every we test the dts package. Sometimes
> we don't even get the error at all.
> We're running on sql server 2000 sp3 , any input or advice on this matter
> would be highly appreciated.
> Please find below the stack dump file...
> Regards,
> Erwin
> ========================================
=============================
> BugCheck Dump
> ========================================
=============================
>
> This file is generated by Microsoft SQL Server 8.00.760
> upon detection of fatal unexpected error. Please return this file,
> the query or program that produced the bugcheck, the database and
> the error log, and any other pertinent information with a Service Request.
>
> Computer type is AT/AT COMPATIBLE.
> Bios Version is IBM - 1000
> IBM BIOS Ver 1.05
> Current time is 03:00:33 12/24/05.
> 4 Intel x86 level 15, 3000 Mhz processor(s).
> Windows NT 5.2 Build 3790 CSD .
>
> Memory
> MemoryLoad = 60%
> Total Physical = 3583 MB
> Available Physical = 1403 MB
> Total Page File = 5474 MB
> Available Page File = 3466 MB
> Total Virtual = 2047 MB
> Available Virtual = 236 MB
> *Stack Dump being sent to e:\MSSQL\log\SQLDump0001.txt
> *
> ****************************************
**********************************
***
> **
> *
> * BEGIN STACK DUMP:
> * 12/24/05 03:00:33 spid 61
> *
> * Exception Address = 06B824C5 (DDCS_Enter + 00000004 Line 0+00000000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address 06E1FF2C
> * Input Buffer 468 bytes -
> * BULK INSERT S_Import_IncrementalStock_InsertUpdates FROM 'e:\MerRep_Dat
a
> * \Work\DwMerchandise_UKwms_Batch00481_Inc
rementalStock_InsertUpdates.txt
'
> * WITH (CODEPAGE = 'RAW' , FIELDTERMINATOR = '??' , ROWTERMINATOR = '
' ,
> * MAXERRORS = 10 )
> *
> *
> * MODULE BASE END SIZE
> * sqlservr 00400000 00B2CFFF 0072d000
> * ntdll 77F40000 77FF9FFF 000ba000
> * kernel32 77E40000 77F33FFF 000f4000
> * ADVAPI32 77DA0000 77E2FFFF 00090000
> * RPCRT4 77C50000 77CF4FFF 000a5000
> * USER32 77D00000 77D8EFFF 0008f000
> * GDI32 77C00000 77C43FFF 00044000
> * OPENDS60 41060000 41065FFF 00006000
> * MSVCRT 77BA0000 77BF3FFF 00054000
> * UMS 41070000 4107CFFF 0000d000
> * SQLSORT 42AE0000 42B6FFFF 00090000
> * MSVCIRT 60020000 6002FFFF 00010000
> * sqlevn70 41080000 41086FFF 00007000
> * NETAPI32 02C60000 02CB2FFF 00053000
> * ole32 030D0000 031F4FFF 00125000
> * XOLEHLP 03200000 03205FFF 00006000
> * MSDTCPRX 03210000 03281FFF 00072000
> * OLEAUT32 03290000 0330CFFF 0007d000
> * MSVCP60 03310000 03370FFF 00061000
> * MTXCLU 03380000 03397FFF 00018000
> * VERSION 033A0000 033A7FFF 00008000
> * WSOCK32 033B0000 033B8FFF 00009000
> * WS2_32 033C0000 033D7FFF 00018000
> * WS2HELP 033E0000 033E7FFF 00008000
> * CLUSAPI 03430000 03440FFF 00011000
> * RESUTILS 03450000 03461FFF 00012000
> * USERENV 03470000 03529FFF 000ba000
> * MFC42u 03530000 03623FFF 000f4000
> * secur32 036B0000 036C2FFF 00013000
> * mswsock 036E0000 03722FFF 00043000
> * DNSAPI 03730000 03756FFF 00027000
> * winrnr 037A0000 037A6FFF 00007000
> * WLDAP32 037B0000 037DEFFF 0002f000
> * rasadhlp 03800000 03804FFF 00005000
> * SSNETLIB 00C70000 00C84FFF 00015000
> * SSNMPN70 00C90000 00C95FFF 00006000
> * security 042C0000 042C3FFF 00004000
> * wshtcpip 04310000 04317FFF 00008000
> * SSmsLPCn 04320000 04326FFF 00007000
> * ntdsapi 04340000 04355FFF 00016000
> * kerberos 04770000 047C5FFF 00056000
> * cryptdll 047D0000 047DBFFF 0000c000
> * MSASN1 047E0000 047F1FFF 00012000
> * SQLFTQRY 04630000 04661FFF 00032000
> * CLBCatQ 04B20000 04B9DFFF 0007e000
> * COMRes 04BA0000 04C65FFF 000c6000
> * sqloledb 04C90000 04D15FFF 00086000
> * MSDART 04D20000 04D48FFF 00029000
> * COMCTL32 04D50000 04DDFFFF 00090000
> * comdlg32 04DE0000 04E26FFF 00047000
> * SHLWAPI 04E30000 04E78FFF 00049000
> * SHELL32 04E80000 0565DFFF 007de000
> * MSDATL3 05660000 05677FFF 00018000
> * comctl32 05690000 05775FFF 000e6000
> * oledb32 05B20000 05B9CFFF 0007d000
> * OLEDB32R 05BA0000 05BB0FFF 00011000
> * msv1_0 05C50000 05C73FFF 00024000
> * xpsqlbot 05C80000 05C85FFF 00006000
> * xpstar 05CB0000 05CF6FFF 00047000
> * SQLRESLD 05D00000 05D06FFF 00007000
> * SQLSVC 05D10000 05D26FFF 00017000
> * ODBC32 05D30000 05D69FFF 0003a000
> * odbcbcp 05D70000 05D75FFF 00006000
> * W95SCM 05D90000 05D9BFFF 0000c000
> * SQLUNIRL 05DA0000 05DCCFFF 0002d000
> * WINSPOOL 05DD0000 05DF5FFF 00026000
> * SHFOLDER 05E00000 05E08FFF 00009000
> * odbcint 05FF0000 06006FFF 00017000
> * NDDEAPI 06110000 06116FFF 00007000
> * SQLSVC 06120000 06125FFF 00006000
> * xpstar 06130000 06138FFF 00009000
> * rsaenh 0FFD0000 0FFFCFFF 0002d000
> * PSAPI 05D80000 05D8AFFF 0000b000
> * impprov 065D0000 065E8FFF 00019000
> * sqlmap70 06580000 065A9FFF 0002a000
> * MAPI32 065B0000 065CEFFF 0001f000
> * MSMAPI32 06B80000 06CCDFFF 0014e000
> * mso 07510000 080C1FFF 00bb2000
> * iphlpapi 06F20000 06F36FFF 00017000
> * MPRAPI 08270000 08286FFF 00017000
> * ACTIVEDS 08290000 082C1FFF 00032000
> * adsldpc 082D0000 082F5FFF 00026000
> * credui 08300000 0832CFFF 0002d000
> * ATL 08330000 08347FFF 00018000
> * rtutils 08350000 0835AFFF 0000b000
> * SAMLIB 08360000 0836FFFF 00010000
> * SETUPAPI 08370000 0846FFFF 00100000
> * netman 084D0000 08506FFF 00037000
> * RASAPI32 08510000 0854AFFF 0003b000
> * rasman 08550000 08560FFF 00011000
> * TAPI32 08570000 0859DFFF 0002e000
> * WINMM 085A0000 085CBFFF 0002c000
> * CRYPT32 085D0000 08667FFF 00098000
> * WZCSvc 08670000 086B6FFF 00047000
> * WMI 08470000 08474FFF 00005000
> * DHCPCSVC 086C0000 086DBFFF 0001c000
> * WTSAPI32 086E0000 086E7FFF 00008000
> * WINSTA 086F0000 086FFFFF 00010000
> * ESENT 08700000 08807FFF 00108000
> * WZCSAPI 08810000 08818FFF 00009000
> * xplog70 06560000 06571FFF 00012000
> * xplog70 09160000 09163FFF 00004000
> * sqlvdi 09170000 0917BFFF 0000c000
>

DTS bulk load fails

Hi,
while executing a bulk insert DTS task, we sometimes experience an
'EXCEPTION_ACCESS_VIOLATION' error. We load several text files
into sql tables parrallel. The error occurs does not necessarily occur
on the same bulk load task, every we test the dts package. Sometimes
we don't even get the error at all.
We're running on sql server 2000 sp3 , any input or advice on this matter
would be highly appreciated.
Please find below the stack dump file...
Regards,
Erwin
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server 8.00.760
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is IBM - 1000
IBM BIOS Ver 1.05
Current time is 03:00:33 12/24/05.
4 Intel x86 level 15, 3000 Mhz processor(s).
Windows NT 5.2 Build 3790 CSD .
Memory
MemoryLoad = 60%
Total Physical = 3583 MB
Available Physical = 1403 MB
Total Page File = 5474 MB
Available Page File = 3466 MB
Total Virtual = 2047 MB
Available Virtual = 236 MB
*Stack Dump being sent to e:\MSSQL\log\SQLDump0001.txt
*
************************************************** ***************************
**
*
* BEGIN STACK DUMP:
* 12/24/05 03:00:33 spid 61
*
* Exception Address = 06B824C5 (DDCS_Enter + 00000004 Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 06E1FF2C
* Input Buffer 468 bytes -
* BULK INSERT S_Import_IncrementalStock_InsertUpdates FROM 'e:\MerRep_Data
* \Work\DwMerchandise_UKwms_Batch00481_IncrementalSt ock_InsertUpdates.txt'
* WITH (CODEPAGE = 'RAW' , FIELDTERMINATOR = '??' , ROWTERMINATOR = ' ' ,
* MAXERRORS = 10 )
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00B2CFFF 0072d000
* ntdll 77F40000 77FF9FFF 000ba000
* kernel32 77E40000 77F33FFF 000f4000
* ADVAPI32 77DA0000 77E2FFFF 00090000
* RPCRT4 77C50000 77CF4FFF 000a5000
* USER32 77D00000 77D8EFFF 0008f000
* GDI32 77C00000 77C43FFF 00044000
* OPENDS60 41060000 41065FFF 00006000
* MSVCRT 77BA0000 77BF3FFF 00054000
* UMS 41070000 4107CFFF 0000d000
* SQLSORT 42AE0000 42B6FFFF 00090000
* MSVCIRT 60020000 6002FFFF 00010000
* sqlevn70 41080000 41086FFF 00007000
* NETAPI32 02C60000 02CB2FFF 00053000
* ole32 030D0000 031F4FFF 00125000
* XOLEHLP 03200000 03205FFF 00006000
* MSDTCPRX 03210000 03281FFF 00072000
* OLEAUT32 03290000 0330CFFF 0007d000
* MSVCP60 03310000 03370FFF 00061000
* MTXCLU 03380000 03397FFF 00018000
* VERSION 033A0000 033A7FFF 00008000
* WSOCK32 033B0000 033B8FFF 00009000
* WS2_32 033C0000 033D7FFF 00018000
* WS2HELP 033E0000 033E7FFF 00008000
* CLUSAPI 03430000 03440FFF 00011000
* RESUTILS 03450000 03461FFF 00012000
* USERENV 03470000 03529FFF 000ba000
* MFC42u 03530000 03623FFF 000f4000
* secur32 036B0000 036C2FFF 00013000
* mswsock 036E0000 03722FFF 00043000
* DNSAPI 03730000 03756FFF 00027000
* winrnr 037A0000 037A6FFF 00007000
* WLDAP32 037B0000 037DEFFF 0002f000
* rasadhlp 03800000 03804FFF 00005000
* SSNETLIB 00C70000 00C84FFF 00015000
* SSNMPN70 00C90000 00C95FFF 00006000
* security 042C0000 042C3FFF 00004000
* wshtcpip 04310000 04317FFF 00008000
* SSmsLPCn 04320000 04326FFF 00007000
* ntdsapi 04340000 04355FFF 00016000
* kerberos 04770000 047C5FFF 00056000
* cryptdll 047D0000 047DBFFF 0000c000
* MSASN1 047E0000 047F1FFF 00012000
* SQLFTQRY 04630000 04661FFF 00032000
* CLBCatQ 04B20000 04B9DFFF 0007e000
* COMRes 04BA0000 04C65FFF 000c6000
* sqloledb 04C90000 04D15FFF 00086000
* MSDART 04D20000 04D48FFF 00029000
* COMCTL32 04D50000 04DDFFFF 00090000
* comdlg32 04DE0000 04E26FFF 00047000
* SHLWAPI 04E30000 04E78FFF 00049000
* SHELL32 04E80000 0565DFFF 007de000
* MSDATL3 05660000 05677FFF 00018000
* comctl32 05690000 05775FFF 000e6000
* oledb32 05B20000 05B9CFFF 0007d000
* OLEDB32R 05BA0000 05BB0FFF 00011000
* msv1_0 05C50000 05C73FFF 00024000
* xpsqlbot 05C80000 05C85FFF 00006000
* xpstar 05CB0000 05CF6FFF 00047000
* SQLRESLD 05D00000 05D06FFF 00007000
* SQLSVC 05D10000 05D26FFF 00017000
* ODBC32 05D30000 05D69FFF 0003a000
* odbcbcp 05D70000 05D75FFF 00006000
* W95SCM 05D90000 05D9BFFF 0000c000
* SQLUNIRL 05DA0000 05DCCFFF 0002d000
* WINSPOOL 05DD0000 05DF5FFF 00026000
* SHFOLDER 05E00000 05E08FFF 00009000
* odbcint 05FF0000 06006FFF 00017000
* NDDEAPI 06110000 06116FFF 00007000
* SQLSVC 06120000 06125FFF 00006000
* xpstar 06130000 06138FFF 00009000
* rsaenh 0FFD0000 0FFFCFFF 0002d000
* PSAPI 05D80000 05D8AFFF 0000b000
* impprov 065D0000 065E8FFF 00019000
* sqlmap70 06580000 065A9FFF 0002a000
* MAPI32 065B0000 065CEFFF 0001f000
* MSMAPI32 06B80000 06CCDFFF 0014e000
* mso 07510000 080C1FFF 00bb2000
* iphlpapi 06F20000 06F36FFF 00017000
* MPRAPI 08270000 08286FFF 00017000
* ACTIVEDS 08290000 082C1FFF 00032000
* adsldpc 082D0000 082F5FFF 00026000
* credui 08300000 0832CFFF 0002d000
* ATL 08330000 08347FFF 00018000
* rtutils 08350000 0835AFFF 0000b000
* SAMLIB 08360000 0836FFFF 00010000
* SETUPAPI 08370000 0846FFFF 00100000
* netman 084D0000 08506FFF 00037000
* RASAPI32 08510000 0854AFFF 0003b000
* rasman 08550000 08560FFF 00011000
* TAPI32 08570000 0859DFFF 0002e000
* WINMM 085A0000 085CBFFF 0002c000
* CRYPT32 085D0000 08667FFF 00098000
* WZCSvc 08670000 086B6FFF 00047000
* WMI 08470000 08474FFF 00005000
* DHCPCSVC 086C0000 086DBFFF 0001c000
* WTSAPI32 086E0000 086E7FFF 00008000
* WINSTA 086F0000 086FFFFF 00010000
* ESENT 08700000 08807FFF 00108000
* WZCSAPI 08810000 08818FFF 00009000
* xplog70 06560000 06571FFF 00012000
* xplog70 09160000 09163FFF 00004000
* sqlvdi 09170000 0917BFFF 0000c000
* msi 0AA10000 0AC23FFF 00214000
* MAPIR 06F50000 0700FFFF 000c0000
* contab32 030B0000 030CEFFF 0001f000
* EMSABP32 06DA0000 06DD7FFF 00038000
* EMSMDB32 08F60000 09019FFF 000ba000
* uxtheme 09120000 09152FFF 00033000
* dbghelp 09720000 097D4FFF 000b5000
*
* Edi: 06E1FF14:
* Esi: 06E1FEF8:
* Eax: C0000000:
* Ebx: 00000000:
* Ecx: 06E1FF14:
* Edx: 00000020:
* Eip: 06B824C5:
* Ebp: 0A30EDF4: 0A30EE20 77D0612F 00EC019E 00000507 06E1FEF8
00000
000
* SegCs: 0000001B:
* EFlags: 00010246: 006D0065 00320033 0057005C 00650062 003B006D
003A0
043
* Esp: 0A30EDD8: 06B86F6F 06E1FF14 0A30EE6C 06E1FEF8 06B8510A
06E1F
EF8
* SegSs: 00000023:
*
************************************************** ***************************
**
*
* Short Stack Dump
* 06B824C5 Module(MSMAPI32+000024C5) (DDCS_Enter+00000004)
* 77D0612F Module(USER32+0000612F)
* 77D069A5 Module(USER32+000069A5) (GetMessageW+000001EE)
* 77D06689 Module(USER32+00006689) (TranslateMessage+00000520)
* 77D0FAE4 Module(USER32+0000FAE4) (DispatchMessageA+0000000B)
* 065D2BB3 Module(impprov+00002BB3)
* 065DE84A Module(impprov+0000E84A) (DllRegisterServer+0000AA3A)
* 065E145C Module(impprov+0001145C) (DllRegisterServer+0000D64C)
* 065DE1DC Module(impprov+0000E1DC) (DllRegisterServer+0000A3CC)
* 0047E663 Module(sqlservr+0007E663)
(CBcpImport::CreateInprocProvider+000002EF
)
* 0047DB5A Module(sqlservr+0007DB5A) (CBcpImport::Init+0000029D)
* 0047D854 Module(sqlservr+0007D854) (BcpImportMain+0000014D)
* 0047D714 Module(sqlservr+0007D714) (CStmtBulkIns::XretExecute+0000005F)
* 0041B442 Module(sqlservr+0001B442)
(CMsqlExecContext::ExecuteStmts+000003B9)
* 0041AA88 Module(sqlservr+0001AA88) (CMsqlExecContext::Execute+000001B6)
* 0041B9B6 Module(sqlservr+0001B9B6) (CSQLSource::Execute+00000357)
* 0048A63B Module(sqlservr+0008A63B) (language_exec+000003E1)
* 0042708C Module(sqlservr+0002708C) (process_commands+0000010E)
* 41075002 Module(UMS+00005002) (ProcessWorkRequests+00000272)
* 41074698 Module(UMS+00004698) (ThreadStartRoutine+00000098)
* 77BC90A2 Module(MSVCRT+000290A2) (endthread+000000A6)
* 77E4A990 Module(kernel32+0000A990) (FlsSetValue+00000779)
* Location : 06B824C5 Module(MSMAPI32+000024C5) (DDCS_Enter+00000004)
* Return Addr: 77D0612F Module(USER32+0000612F)
Frame : 0A30EDF4
Parameters:
[1] 00EC019E: 00000240 00000000 00000000 00000000 00000000 00000000
[2] 00000507:
[3] 06E1FEF8:
[4] 00000000:
160 bytes of stack data from 0A30ED54 to 0A30EDF4
0A30ED54: 00000000 00000000 00000000 00000000 [............]
:::: 7 Duplicate lines detected
0A30EDD4: 00000000 06B86F6F 06E1FF14 0A30EE6C [...oo.....l.0.]
0A30EDE4: 06E1FEF8 06B8510A 06E1FEF8 06B850F4 [....Q......P..]
* Location : 77D0612F Module(USER32+0000612F)
* Return Addr: 77D069A5 Module(USER32+000069A5) (GetMessageW+000001EE)
Frame : 0A30EE20
Parameters:
[1] 06B850F4:
[2] 00EC019E: 00000240 00000000 00000000 00000000 00000000 00000000
[3] 00000507:
[4] 06E1FEF8:
44 bytes of stack data from 0A30EDF4 to 0A30EE20
0A30EDF4: 0A30EE20 77D0612F 00EC019E 00000507 [ .0./a.w......]
0A30EE04: 06E1FEF8 00000000 06B850F4 DCBAABCD [.......P.....]
0A30EE14: 00000000 0A30EE6C 06B850F4 [...l.0..P..]
..
PSS @.0x76D8D258
pspid = 61 m_dwLoginFlags = 0x1083e0 plsid = 1717878624
pbackground = 0
pbSid
01010000 00000005 12000000 .........
sSecFlags = 0x1e
pdeadlockpri = 0 poffsets = 0x0 pss_stats = 0x0
ptickcount = 1352914718 pcputickcount = 4059555816433772
ploginstamp = 10002 ptimestamp = 2005-12-24 03:00:33.530
plangid = 0 pdateformat = 1 pdatefirst = 7
Language = us_english UserName = NT AUTHORITY\SYSTEM
poptions = 0x28000020 poptions2 = 0x13f438 pline = 1
pcurstepno = 1 prowcount = 0 pstatlist = 0
pcurcmd = 240 pseqstat = 0 ptextsize = 2147483647
pretstat = 0 CNestLevel = 0 @.@.procid = 0
Xact_Begin_Time = 2005-12-24 03:00:33.543
pslastbatchstarttime = 2005-12-24 03:00:33.543 pmemusage = 5
hLicense = 0 tpFlags = 0x1 isolation_level = 0
fips_flag = 0x0 sSaveSecFlags = 0x0 psavedb = 0
pfetchstat = 0 pcrsrows = 0
pslastbatchtime = 2005-12-24 03:00:33.543 pNtUser = SYSTEM
pNtDomain = NT AUTHORITY pubexecdb = 0 fInReplicatedProcExec =
0
pMsqlXact = 0x76D8DE60 presSemCount = [0]170977488
presSemCount = [0]170977488 pcputot = 0
pcputotstart = 0 pcpucmdstart = 0 pbufread = 0
pbufreadstart = 0 plogbufread = 178 plogbufreadstart = 162
pbufwrite = 0 pbufwritestart = 0 pLockTimeout =
4294967295
pUtilResultSet = 0x00000000
pec
ec_pss->pspid = 61 ecid = 0 ec_stat = 0x0
ec_stat2 = 0x100001 ec_atomic = 0x0 pcurdb = 9
ec_lasterror = 0 ec_preverror = 0 ec_cpucur = 2408031
ec_cmderrs = 0 ec_timeslice = 84 ec_dbtable = 0x19EB0030
ec_reswait = 0x0 ec_dbindex = -1 ec_waittype = 0x0000
Waittime = 0 ec_umsContext->m_pSched->m_id (SchedulerId) = 0x2
ec_umsContext->m_workercntxt->m_id (threadId) = 0x9fc
ExecutionContext Summary @.0x76D8D580
ec_pss->pspid = 61 ecid = 0 ec_stat = 0x0
ec_stat2 = 0x100001 ec_atomic = 0x0 pcurdb = 9
ec_lasterror = 0 ec_preverror = 0 ec_cpucur = 2408031
ec_cmderrs = 0 ec_timeslice = 84 ec_dbtable = 0x19EB0030
ec_reswait = 0x0 ec_dbindex = -1 ec_waittype = 0x0000
Waittime = 0 ec_umsContext->m_pSched->m_id (SchedulerId) = 0x2
ec_umsContext->m_workercntxt->m_id (threadId) = 0x9fc
psrvproc->eclClient = 4 psrvproc->status = 8
psrvproc->state = SRV_RUNNING psrvproc->bNewPacket = 0
psrvproc->pmo = 0x76D84030
psrvproc->ums_context = 0x038A1950 psrvproc->threadId =
0x9fc
client threadId = 0xdc8
...
Hi
This http://support.microsoft.com/default...b;en-us;839458 was
fixed after SP3, although you don't give any information about identity
values and I would not expect it to perform inconsistently as you describe;
but you may want to see if loading SP4 removes this issue. Something else you
may wish to try could be to run them all on the main thread.
John
"Erwin" wrote:

> Hi,
> while executing a bulk insert DTS task, we sometimes experience an
> 'EXCEPTION_ACCESS_VIOLATION' error. We load several text files
> into sql tables parrallel. The error occurs does not necessarily occur
> on the same bulk load task, every we test the dts package. Sometimes
> we don't even get the error at all.
> We're running on sql server 2000 sp3 , any input or advice on this matter
> would be highly appreciated.
> Please find below the stack dump file...
> Regards,
> Erwin
> ================================================== ===================
> BugCheck Dump
> ================================================== ===================
>
> This file is generated by Microsoft SQL Server 8.00.760
> upon detection of fatal unexpected error. Please return this file,
> the query or program that produced the bugcheck, the database and
> the error log, and any other pertinent information with a Service Request.
>
> Computer type is AT/AT COMPATIBLE.
> Bios Version is IBM - 1000
> IBM BIOS Ver 1.05
> Current time is 03:00:33 12/24/05.
> 4 Intel x86 level 15, 3000 Mhz processor(s).
> Windows NT 5.2 Build 3790 CSD .
>
> Memory
> MemoryLoad = 60%
> Total Physical = 3583 MB
> Available Physical = 1403 MB
> Total Page File = 5474 MB
> Available Page File = 3466 MB
> Total Virtual = 2047 MB
> Available Virtual = 236 MB
> *Stack Dump being sent to e:\MSSQL\log\SQLDump0001.txt
> *
> ************************************************** ***************************
> **
> *
> * BEGIN STACK DUMP:
> * 12/24/05 03:00:33 spid 61
> *
> * Exception Address = 06B824C5 (DDCS_Enter + 00000004 Line 0+00000000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address 06E1FF2C
> * Input Buffer 468 bytes -
> * BULK INSERT S_Import_IncrementalStock_InsertUpdates FROM 'e:\MerRep_Data
> * \Work\DwMerchandise_UKwms_Batch00481_IncrementalSt ock_InsertUpdates.txt'
> * WITH (CODEPAGE = 'RAW' , FIELDTERMINATOR = '??' , ROWTERMINATOR = ' ' ,
> * MAXERRORS = 10 )
> *
> *
> * MODULE BASE END SIZE
> * sqlservr 00400000 00B2CFFF 0072d000
> * ntdll 77F40000 77FF9FFF 000ba000
> * kernel32 77E40000 77F33FFF 000f4000
> * ADVAPI32 77DA0000 77E2FFFF 00090000
> * RPCRT4 77C50000 77CF4FFF 000a5000
> * USER32 77D00000 77D8EFFF 0008f000
> * GDI32 77C00000 77C43FFF 00044000
> * OPENDS60 41060000 41065FFF 00006000
> * MSVCRT 77BA0000 77BF3FFF 00054000
> * UMS 41070000 4107CFFF 0000d000
> * SQLSORT 42AE0000 42B6FFFF 00090000
> * MSVCIRT 60020000 6002FFFF 00010000
> * sqlevn70 41080000 41086FFF 00007000
> * NETAPI32 02C60000 02CB2FFF 00053000
> * ole32 030D0000 031F4FFF 00125000
> * XOLEHLP 03200000 03205FFF 00006000
> * MSDTCPRX 03210000 03281FFF 00072000
> * OLEAUT32 03290000 0330CFFF 0007d000
> * MSVCP60 03310000 03370FFF 00061000
> * MTXCLU 03380000 03397FFF 00018000
> * VERSION 033A0000 033A7FFF 00008000
> * WSOCK32 033B0000 033B8FFF 00009000
> * WS2_32 033C0000 033D7FFF 00018000
> * WS2HELP 033E0000 033E7FFF 00008000
> * CLUSAPI 03430000 03440FFF 00011000
> * RESUTILS 03450000 03461FFF 00012000
> * USERENV 03470000 03529FFF 000ba000
> * MFC42u 03530000 03623FFF 000f4000
> * secur32 036B0000 036C2FFF 00013000
> * mswsock 036E0000 03722FFF 00043000
> * DNSAPI 03730000 03756FFF 00027000
> * winrnr 037A0000 037A6FFF 00007000
> * WLDAP32 037B0000 037DEFFF 0002f000
> * rasadhlp 03800000 03804FFF 00005000
> * SSNETLIB 00C70000 00C84FFF 00015000
> * SSNMPN70 00C90000 00C95FFF 00006000
> * security 042C0000 042C3FFF 00004000
> * wshtcpip 04310000 04317FFF 00008000
> * SSmsLPCn 04320000 04326FFF 00007000
> * ntdsapi 04340000 04355FFF 00016000
> * kerberos 04770000 047C5FFF 00056000
> * cryptdll 047D0000 047DBFFF 0000c000
> * MSASN1 047E0000 047F1FFF 00012000
> * SQLFTQRY 04630000 04661FFF 00032000
> * CLBCatQ 04B20000 04B9DFFF 0007e000
> * COMRes 04BA0000 04C65FFF 000c6000
> * sqloledb 04C90000 04D15FFF 00086000
> * MSDART 04D20000 04D48FFF 00029000
> * COMCTL32 04D50000 04DDFFFF 00090000
> * comdlg32 04DE0000 04E26FFF 00047000
> * SHLWAPI 04E30000 04E78FFF 00049000
> * SHELL32 04E80000 0565DFFF 007de000
> * MSDATL3 05660000 05677FFF 00018000
> * comctl32 05690000 05775FFF 000e6000
> * oledb32 05B20000 05B9CFFF 0007d000
> * OLEDB32R 05BA0000 05BB0FFF 00011000
> * msv1_0 05C50000 05C73FFF 00024000
> * xpsqlbot 05C80000 05C85FFF 00006000
> * xpstar 05CB0000 05CF6FFF 00047000
> * SQLRESLD 05D00000 05D06FFF 00007000
> * SQLSVC 05D10000 05D26FFF 00017000
> * ODBC32 05D30000 05D69FFF 0003a000
> * odbcbcp 05D70000 05D75FFF 00006000
> * W95SCM 05D90000 05D9BFFF 0000c000
> * SQLUNIRL 05DA0000 05DCCFFF 0002d000
> * WINSPOOL 05DD0000 05DF5FFF 00026000
> * SHFOLDER 05E00000 05E08FFF 00009000
> * odbcint 05FF0000 06006FFF 00017000
> * NDDEAPI 06110000 06116FFF 00007000
> * SQLSVC 06120000 06125FFF 00006000
> * xpstar 06130000 06138FFF 00009000
> * rsaenh 0FFD0000 0FFFCFFF 0002d000
> * PSAPI 05D80000 05D8AFFF 0000b000
> * impprov 065D0000 065E8FFF 00019000
> * sqlmap70 06580000 065A9FFF 0002a000
> * MAPI32 065B0000 065CEFFF 0001f000
> * MSMAPI32 06B80000 06CCDFFF 0014e000
> * mso 07510000 080C1FFF 00bb2000
> * iphlpapi 06F20000 06F36FFF 00017000
> * MPRAPI 08270000 08286FFF 00017000
> * ACTIVEDS 08290000 082C1FFF 00032000
> * adsldpc 082D0000 082F5FFF 00026000
> * credui 08300000 0832CFFF 0002d000
> * ATL 08330000 08347FFF 00018000
> * rtutils 08350000 0835AFFF 0000b000
> * SAMLIB 08360000 0836FFFF 00010000
> * SETUPAPI 08370000 0846FFFF 00100000
> * netman 084D0000 08506FFF 00037000
> * RASAPI32 08510000 0854AFFF 0003b000
> * rasman 08550000 08560FFF 00011000
> * TAPI32 08570000 0859DFFF 0002e000
> * WINMM 085A0000 085CBFFF 0002c000
> * CRYPT32 085D0000 08667FFF 00098000
> * WZCSvc 08670000 086B6FFF 00047000
> * WMI 08470000 08474FFF 00005000
> * DHCPCSVC 086C0000 086DBFFF 0001c000
> * WTSAPI32 086E0000 086E7FFF 00008000
> * WINSTA 086F0000 086FFFFF 00010000
> * ESENT 08700000 08807FFF 00108000
> * WZCSAPI 08810000 08818FFF 00009000
> * xplog70 06560000 06571FFF 00012000
> * xplog70 09160000 09163FFF 00004000
> * sqlvdi 09170000 0917BFFF 0000c000
>

Wednesday, March 7, 2012

DTS - SQL SERVER

Does the possibility exist of executing a DTS created in SQL Server 7
through a Query using a page ASP or Visual Basic?Hi Frank.
DTS has a COM API, so you can invoke packages (& even create / edit
packages) via the COM interfaces.
You can find examples of how to do this in VB here:
http://www.sqldts.com/default.aspx?208
Or in T-SQL here:
http://www.databasejournal.com/features/mssql/article.php/1459181
HTH
Regards,
Greg Linwood
SQL Server MVP
"Frank Dulk" <fdulk@.bol.com.br> wrote in message
news:Oj4MW3bnDHA.1656@.tk2msftngp13.phx.gbl...
>
> Does the possibility exist of executing a DTS created in SQL Server 7
> through a Query using a page ASP or Visual Basic?
>
>

DTS - Execute Package Task Problem

I have five DTS packages on a server.

Instead of executing these DTS packages individually, I have decided to create a 'parent' DTS package that will fire off each of the five 'child' DTS packages using 'On Success' precedences.

This seemed like a pretty straight forward task, but when one of the child DTS packages fails, the 'parent' DTS package continues to execute the next 'child' DTS package through the 'On Success' precedence. I was expecting the 'parent' DTS to fire off an 'on failure' precendence and stop executing

Can anyone tell me why the 'parent' DTS package continues with the 'on success' precedence after one of the 'child' DTS packages has failed.

Thanks in advance.Hi Krispy

I can't answer your question directly however I tend to use the below to execute my DTSs from code. I now include about as little as possible in my DTSs (the transformation only in fact) and wrap everything else up in a sproc.
So - the long and the short of my answer would be - perhaps look at replacing your masater DTS with some T-SQL code - makes trouble shooting and execution flow much easier IMHO.
http://www.pengoworks.com/index.cfm?action=articles:spExecuteDTS

HTH|||Thanks for the swift response Pootle Flump - much appreciated.

I did a bit of digging and found this in the SQL Server 2005 books online. I probably should have said that we are running SQL Server 2000.

Alternatively, sometimes you want the parent and child packages to fail together as one unit, or you might not want to incur the additional overhead of another process. For example, if a child process fails and subsequent processing in the parent process of the package depends on success of the child process, the child package should run in the process of the parent package.

By default, the ExecuteOutOfProcess property of the Execute Package task is set to False, and the child package runs in the same process as the parent package. If you set this property to True, you can debug only packages that contain limited functionality. To debug all packages supported by your edition of SQL Server 2005, you must install Integration Services.

Does anyone know if it is possible to set the ExecuteOutOfProcess property on SQL Server 2000, or is this specific to SQL Server 2005?

Sunday, February 26, 2012

DTS

Hi,

What is good way of executing .dtsx jobs in sql 2005, when stored in file format, or msdb database. Can my sql agent read jobs from file format as well as msdb database ?

Thanks &Regards

Nitu

Yes SQLAgent can execute file system or msdb packages. I'm surprised you could not find that information in Books Online. The online version is here ...

http://msdn2.microsoft.com/en-us/library/ms141701(SQL.90).aspx

At the bottom of every Books Online page there is an option to vote for the usefulness of the content. You can do that to help us improve the content - I'm concerned that you are not finding this information there, so any help you can give us would be appreciated.

Donald Farmer

DTS

Could you help me with this problem: I have a DTS
executing .bat file and when try to run it in enterprise
management error occurs "The device is not
ready." Other DTSs with SQL queries work fine.I'd guess that DTS is trying to access a physical drive letter that
doesn't exist or isn't mapped. Use UNC paths instead of drive letters
and see if the problem goes away.
--
David Portas
SQL Server MVP
--|||I am using the UNC path
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1121875027.700950.158000@.g43g2000cwa.googlegroups.com...
> I'd guess that DTS is trying to access a physical drive letter that
> doesn't exist or isn't mapped. Use UNC paths instead of drive letters
> and see if the problem goes away.
> --
> David Portas
> SQL Server MVP
> --
>|||docsql wrote:
> I am using the UNC path
> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in
> message news:1121875027.700950.158000@.g43g2000cwa.googlegroups.com...
>> I'd guess that DTS is trying to access a physical drive letter that
>> doesn't exist or isn't mapped. Use UNC paths instead of drive letters
>> and see if the problem goes away.
>> --
>> David Portas
>> SQL Server MVP
>> --
Are you sure the account running the DTS script has access to the UNC
you provide?
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||yes
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:%23At6ZwUjFHA.3540@.TK2MSFTNGP14.phx.gbl...
> docsql wrote:
>> I am using the UNC path
>> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in
>> message news:1121875027.700950.158000@.g43g2000cwa.googlegroups.com...
>> I'd guess that DTS is trying to access a physical drive letter that
>> doesn't exist or isn't mapped. Use UNC paths instead of drive letters
>> and see if the problem goes away.
>> --
>> David Portas
>> SQL Server MVP
>> --
> Are you sure the account running the DTS script has access to the UNC you
> provide?
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com|||Hello,
Similar issue will occur when using the DTS import/Export wizard, select
the option "Copy Objects and data between SQL server databases" and the
script file directory pointing to a wrong drive.
If this is the case, to narrow down the issue, copy the script file to the
local hard drive and recreate a new DTS package to test.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Friday, February 24, 2012

DTExec Reporting Options

Currently, we are running a Master Package with sub-Packages that are executed as a result. We run multiple days by executing a .bat file of DTExec commands. For Example:

Code Snippet

DTExec /FILE E:\ETL\FinancialDataMart\Master.dtsx /SET \Package.Variables[ReportingDate].Value;"1/02/2007" > etl_20070102.log
mkdir E:\ETL\ErrorLogs\Archive\20070102
copy E:\ETL\ErrorLogs\Processing\*.txt E:\ETL\ErrorLogs\Archive\20070102

Date values are incremented for as many days as we want to run. The log gives progress information and the Started, Finished, Elapsed time for the the Master package.

We are interested in manipulating the script entries to get the Start, Finished, Elapsed time for the sub-Packages that are initiated by this script. I think that I could use the Reporting option:

Code Snippet

/Rep[orting] level [;event_guid_or_name[;event_guid_or_name[...]]

Of course I can't find a good example to model the script. Is there anyone else using DTExec to get the run time statistics for each and every package? If so, can you forward that part of the script that accomplishes this task? BTW, we are going to implement run-time auditing to a table at some point but we are not there yet. Of course, my manager would like statistics now.

Thanks in advance.

You could get all those details by enabling package logging on each package; that is just a few clicks away. You can choose where the log information is going to be: file, table etc.

Package logging is enable/disable at the package level, so you need to edit each package.

|||

If my package itself fails to load for some reason, the logging will not happen (this is my assumption), so how do I capture that. The DTEXEC return codes just says the package failed to load. For eg when I executing one of the packages I got the return code as 1, but the console displayed the below error.

Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80040E14
(Only the owner of DTS Package 'kk-test' or a member of the sysadmin role may create new versions of it.).
The SQL statement that was issued has failed.

I dont think there is any way for me to capture this error.

Thanks

|||

You could try redirecting the output from DTEXEC to a file.

Code Snippet

DTEXEC [your package params] > log.txt

|||

Visual SSIS package execution stats (e.g. # executions, most recent execution timestamp, avg runtime , # failures, # successes, and all by machine) is available for "free" via SQL Server Reporting services, provided one uses the stock SQL Server log provider in each package.

These run time stats can be had via the following BI project: SSIS Log Provider Reports .

The stock SQL Server log provider writes to table named sysdtslog90 via the stored procedure sp_dts_addlogentry in whatever server instance/database is pointed to by the log provider's connection manager.

Now, since the report does hit the table directly, its probably a more reasonable approach to push the logging data into a cube periodically, reporting from there, but that feature is not included.

|||

jwelch wrote:

You could try redirecting the output from DTEXEC to a file.

Code Snippet
DTEXEC [your package params] > log.txt

This works if I execute the DTEXEC directly in the command prompt, but when I execute using WScript shell in vbscript it fails with return value 6 saying "The utility encountered an internal error of syntactic or semantic errors in the command line"

Code Snippet

strShellCommand = "DTEXEC /SQL "\pkg-1 " /SERVER MBIXDEV1 /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E > \\serv1\logs\test.tmp"
Set objWshShell = WScript.CreateObject("WScript.Shell")

lngReturnValue = objWshShell.Run(strShellCommand , vbNormalFocus, True)

So how do I make this work? If I copy the strShellCommand value to command prompt and run it works.

Thanks

|||

See Michael's post here: http://blogs.msdn.com/michen/archive/2007/08/02/redirecting-output-of-execute-process-task.aspx

You probably need to run it as CMD.EXE /C DTEXEC [rest of your commandline] > log.txt

|||

Karunakaran,

We invoke a .bat file from the vbs script:

Code Snippet

IF (colFiles1.Count = 1 _
AND colFiles2.Count = 1 _
AND colFiles3.Count = 1 _
AND colFiles4.Count = 1 _
AND colFiles5.Count = 1 _
AND colFiles6.Count = 1 _
AND colFiles7.Count = 1) THEN
Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run "E:\\ETL\\daily_import_and_etl_with_cmd_input.bat 0807 8/7"
Wscript.Quit
END IF

The .bat file looks like this basically:

Code Snippet

DTExec /FILE E:\ETL\FinancialDataMart\Master.dtsx /DECRYPT masterpwd /SET \Package.Variables[ReportingDate].Value;"%2/2007" > E:\ETL\ErrorLogs\Processing\etl_2007%1log.txt
IF NOT %ERRORLEVEL%==0 GOTO ERROR%ERRORLEVEL%
MKDIR E:\ETL\ErrorLogs\Archive\2007%1
MOVE E:\ETL\ErrorLogs\Processing\*.txt E:\ETL\ErrorLogs\Archive\2007%1

The vbs looks for files and then kicks off the ETL. The .bat file has the commands for the ETL.|||

Thanks John, cmd did the trick.

Unfortunately I cannot take the batch file approach because my sys admins will not allow, thanks for suggesting that though.

DTExec Reporting Options

Currently, we are running a Master Package with sub-Packages that are executed as a result. We run multiple days by executing a .bat file of DTExec commands. For Example:

Code Snippet

Date values are incremented for as many days as we want to run. The log gives progress information and the Started, Finished, Elapsed time for the the Master package.

We are interested in manipulating the script entries to get the Start, Finished, Elapsed time for the sub-Packages that are initiated by this script. I think that I could use the Reporting option:

Code Snippet

/Rep[orting] level [;event_guid_or_name[;event_guid_or_name[...]]

Thanks in advance.

You could get all those details by enabling package logging on each package; that is just a few clicks away. You can choose where the log information is going to be: file, table etc.

Package logging is enable/disable at the package level, so you need to edit each package.

|||

I dont think there is any way for me to capture this error.

Thanks

|||

You could try redirecting the output from DTEXEC to a file.

Code Snippet

DTEXEC [your package params] > log.txt

|||

These run time stats can be had via the following BI project: SSIS Log Provider Reports .

Now, since the report does hit the table directly, its probably a more reasonable approach to push the logging data into a cube periodically, reporting from there, but that feature is not included.

|||

jwelch wrote:

You could try redirecting the output from DTEXEC to a file.

Code Snippet
DTEXEC [your package params] > log.txt

Code Snippet

strShellCommand = "DTEXEC /SQL "\pkg-1 " /SERVER MBIXDEV1 /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E > \\serv1\logs\test.tmp"
Set objWshShell = WScript.CreateObject("WScript.Shell")

lngReturnValue = objWshShell.Run(strShellCommand , vbNormalFocus, True)

So how do I make this work? If I copy the strShellCommand value to command prompt and run it works.

Thanks

|||

See Michael's post here: http://blogs.msdn.com/michen/archive/2007/08/02/redirecting-output-of-execute-process-task.aspx

You probably need to run it as CMD.EXE /C DTEXEC [rest of your commandline] > log.txt

|||

Karunakaran,

We invoke a .bat file from the vbs script:

Code Snippet

The .bat file looks like this basically:

Code Snippet

The vbs looks for files and then kicks off the ETL. The .bat file has the commands for the ETL.|||

Thanks John, cmd did the trick.

Unfortunately I cannot take the batch file approach because my sys admins will not allow, thanks for suggesting that though.

DTExec is the only redist for executing dtsx file?

Question:

trying to execute SSIS package "Package.dtsx" from another machine. What are the requirements to do this without installing full SSIS?
I presume that we need .Net framework 2.0, but what are the minimum component or files I need to run a package?

thanks
HorseshoeMy understaning is that SSIS is not redistributable as DTS was. Either way there are more files than just dtexec. All the tasks and components are spread accross several assemblies for example. If it is redistributable, then it will be covered in redist.txt or the equivalent if that has changed from SQL 2000. I believe it is now licencsed as server component, so you need a server licence for any machine you install it on.|||Darren's absolutely right. For a headless install (without UI) on a server, you can select to not install the Tools, but you still need a license and the SQL Server setup to install SSIS on another machine.

regards
ash

Sunday, February 19, 2012

DTEXEC / LoadFromSQLServer Failed

When I try to execute a package (in sql server) using DTEXEC I get the following error. The creator of the package is different from the executing user of the package. But I have also set EncryptionLevel FROM EncryptWithUserKey TO DontSaveSensitive (Which I assume should resolve this issue), re-imported the package to sql server, but the error remains the same. Any pointers?

The utility was unable to load the requested package. The package could not be loaded.

Started: 3:18:56 PM

Could not load package "\test1" because of error 0xC0014062.

Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80040E14 (Only the owner of DTS Package 'test1' or a member of the sysadmin role may create new versions of it.). The SQL statement that was issued has failed.

Source:

Started: 3:18:56 PM

Finished: 3:18:56 PM

Elapsed: 0.328 seconds

Can somebody help me on this?

This is blocking my entire deployment. By the way the package is stored in sql server under MSDB folder.

The package is executed with this command

Code Snippet

DTEXEC /SQL "\pkg-1 " /SERVER server1 /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E

Thanks

|||Was this resolved in your other thread?

|||

Yes John.

Basically we gave the executing user the role db_dtsoperator. Not sure if its a good idea though.

Edit: Included link for the other post.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1980391&SiteID=1

Thanks

DTC issue or SQL Syntax issue

Hi All,
The sending server is SQL 2005 Enterprise SP2 64 bit. The destination
server is SQL 2000 Enterprise SP4.
I am executing this sql in query analyzer:
create table #StoreInfoTraits (
[record type] varchar(3),
[site id] int,
[current effective date] smalldatetime,
[trait id] varchar(50),
[trait value] int
)
DECLARE @.cmd as varchar(200)
SET @.cmd = '[co-dbdev-01].storeinfo.dbo.pr_traitassignments'
insert into #StoreInfoTraits exec(@.cmd)
DROP TABLE #StoreInfoTraits
And getting this error:
OLE DB provider "SQLNCLI" for linked server "co-dbdev-01" returned message
"The transaction manager has disabled its support for remote/network
transactions.".
Msg 7391, Level 16, State 2, Line 1
The operation could not be performed because OLE DB provider "SQLNCLI" for
linked server "co-dbdev-01" was unable to begin a distributed transaction.
Iâ've checked the DTC services per the following link and both DTC services
are running under a domain account and configured properly.
http://groups.google.com/group/microsoft.public.sqlserver.server/msg/127255ab5a3a1fe0?hl=en&lr=&ie=UTF-8&oe=UTF-8
This executes and returns the recordset:
Exec [co-dbdev-01].storeinfo.dbo.pr_traitassignments
Since the remote stored proc returns the records when executing the stored
proc, is it a DTC issue or is this syntax correct ?
insert into #StoreInfoTraits exec(@.cmd)Hi
I think Bill's post covered most things in
http://msdn2.microsoft.com/en-us/library/aa561924.aspx if dtcping/dtctester
work OK then dtc itself can be ruled out.
Your syntax should work (well my test does on mine) providing dtc is running
correctly!
If you don't want to start a distributed transaction you could try
INSERT INTO #StoreInfoTraits ([record type], [site id], [current effective
date], [trait id], [trait value] )
SELECT * FROM OPENQUERY ( co-dbdev-01, 'EXEC
storeinfo.dbo.pr_traitassignments' )
DECLARE @.cmd varchar(400)
SET @.cmd = 'INSERT INTO #StoreInfoTraits ([record type], [site id], [current
effective date], [trait id], [trait value] )
SELECT * FROM OPENQUERY ( co-dbdev-01, ''EXEC
storeinfo.dbo.pr_traitassignments'' ) '
EXEC ( @.cmd )
John
"brymer28303" wrote:
> Hi All,
> The sending server is SQL 2005 Enterprise SP2 64 bit. The destination
> server is SQL 2000 Enterprise SP4.
> I am executing this sql in query analyzer:
> create table #StoreInfoTraits (
> [record type] varchar(3),
> [site id] int,
> [current effective date] smalldatetime,
> [trait id] varchar(50),
> [trait value] int
> )
> DECLARE @.cmd as varchar(200)
> SET @.cmd = '[co-dbdev-01].storeinfo.dbo.pr_traitassignments'
> insert into #StoreInfoTraits exec(@.cmd)
> DROP TABLE #StoreInfoTraits
> And getting this error:
> OLE DB provider "SQLNCLI" for linked server "co-dbdev-01" returned message
> "The transaction manager has disabled its support for remote/network
> transactions.".
> Msg 7391, Level 16, State 2, Line 1
> The operation could not be performed because OLE DB provider "SQLNCLI" for
> linked server "co-dbdev-01" was unable to begin a distributed transaction.
> Iâ've checked the DTC services per the following link and both DTC services
> are running under a domain account and configured properly.
> http://groups.google.com/group/microsoft.public.sqlserver.server/msg/127255ab5a3a1fe0?hl=en&lr=&ie=UTF-8&oe=UTF-8
> This executes and returns the recordset:
> Exec [co-dbdev-01].storeinfo.dbo.pr_traitassignments
> Since the remote stored proc returns the records when executing the stored
> proc, is it a DTC issue or is this syntax correct ?
> insert into #StoreInfoTraits exec(@.cmd)
>
>|||Thanks John. I tried this
INSERT INTO #StoreInfoTraits ([record type], [site id], [current effective
date], [trait id], [trait value] )
SELECT * FROM OPENQUERY ([CO-DBDEV-01], 'EXEC
storeinfo.dbo.pr_TraitAssignments' )
and got this:
Msg 7357, Level 16, State 2, Line 1
Cannot process the object "EXEC storeinfo.dbo.pr_TraitAssignments". The OLE
DB provider "SQLNCLI" for linked server "CO-DBDEV-01" indicates that either
the object has no columns or the current user does not have permissions on
that object.
I can execute this Exec [co-dbdev-01].storeinfo.dbo.pr_traitassignments.
and it returns:
TVA 50 08-30-2006 ACQUISITION 0
TVA 51 08-30-2006 ACQUISITION 0
TVA 52 08-30-2006 ACQUISITION 0
TVA 53 08-30-2006 ACQUISITION 0
TVA 54 08-30-2006 ACQUISITION 0
And, we apparently have a dtc issue I found when I ran the dtctester.exe --
unable to connect.
"John Bell" wrote:
> Hi
> I think Bill's post covered most things in
> http://msdn2.microsoft.com/en-us/library/aa561924.aspx if dtcping/dtctester
> work OK then dtc itself can be ruled out.
> Your syntax should work (well my test does on mine) providing dtc is running
> correctly!
> If you don't want to start a distributed transaction you could try
> INSERT INTO #StoreInfoTraits ([record type], [site id], [current effective
> date], [trait id], [trait value] )
> SELECT * FROM OPENQUERY ( co-dbdev-01, 'EXEC
> storeinfo.dbo.pr_traitassignments' )
> DECLARE @.cmd varchar(400)
> SET @.cmd = 'INSERT INTO #StoreInfoTraits ([record type], [site id], [current
> effective date], [trait id], [trait value] )
> SELECT * FROM OPENQUERY ( co-dbdev-01, ''EXEC
> storeinfo.dbo.pr_traitassignments'' ) '
> EXEC ( @.cmd )
> John
> "brymer28303" wrote:
> > Hi All,
> >
> > The sending server is SQL 2005 Enterprise SP2 64 bit. The destination
> > server is SQL 2000 Enterprise SP4.
> >
> > I am executing this sql in query analyzer:
> >
> > create table #StoreInfoTraits (
> > [record type] varchar(3),
> > [site id] int,
> > [current effective date] smalldatetime,
> > [trait id] varchar(50),
> > [trait value] int
> > )
> > DECLARE @.cmd as varchar(200)
> > SET @.cmd = '[co-dbdev-01].storeinfo.dbo.pr_traitassignments'
> > insert into #StoreInfoTraits exec(@.cmd)
> > DROP TABLE #StoreInfoTraits
> >
> > And getting this error:
> >
> > OLE DB provider "SQLNCLI" for linked server "co-dbdev-01" returned message
> > "The transaction manager has disabled its support for remote/network
> > transactions.".
> > Msg 7391, Level 16, State 2, Line 1
> > The operation could not be performed because OLE DB provider "SQLNCLI" for
> > linked server "co-dbdev-01" was unable to begin a distributed transaction.
> >
> > Iâ've checked the DTC services per the following link and both DTC services
> > are running under a domain account and configured properly.
> > http://groups.google.com/group/microsoft.public.sqlserver.server/msg/127255ab5a3a1fe0?hl=en&lr=&ie=UTF-8&oe=UTF-8
> >
> > This executes and returns the recordset:
> > Exec [co-dbdev-01].storeinfo.dbo.pr_traitassignments
> >
> > Since the remote stored proc returns the records when executing the stored
> > proc, is it a DTC issue or is this syntax correct ?
> > insert into #StoreInfoTraits exec(@.cmd)
> >
> >
> >|||Hi
The user for the remote server will be determined by how the linked server
was created.
The dtctester error looks like you are not even making it to the remote
server! If you go through Bill's post and check out the networking issues it
may show something. You could also try DTCPing.
John
"brymer28303" wrote:
> Thanks John. I tried this
> INSERT INTO #StoreInfoTraits ([record type], [site id], [current effective
> date], [trait id], [trait value] )
> SELECT * FROM OPENQUERY ([CO-DBDEV-01], 'EXEC
> storeinfo.dbo.pr_TraitAssignments' )
> and got this:
> Msg 7357, Level 16, State 2, Line 1
> Cannot process the object "EXEC storeinfo.dbo.pr_TraitAssignments". The OLE
> DB provider "SQLNCLI" for linked server "CO-DBDEV-01" indicates that either
> the object has no columns or the current user does not have permissions on
> that object.
> I can execute this Exec [co-dbdev-01].storeinfo.dbo.pr_traitassignments.
> and it returns:
> TVA 50 08-30-2006 ACQUISITION 0
> TVA 51 08-30-2006 ACQUISITION 0
> TVA 52 08-30-2006 ACQUISITION 0
> TVA 53 08-30-2006 ACQUISITION 0
> TVA 54 08-30-2006 ACQUISITION 0
> And, we apparently have a dtc issue I found when I ran the dtctester.exe --
> unable to connect.
> "John Bell" wrote:
> > Hi
> >
> > I think Bill's post covered most things in
> > http://msdn2.microsoft.com/en-us/library/aa561924.aspx if dtcping/dtctester
> > work OK then dtc itself can be ruled out.
> >
> > Your syntax should work (well my test does on mine) providing dtc is running
> > correctly!
> >
> > If you don't want to start a distributed transaction you could try
> >
> > INSERT INTO #StoreInfoTraits ([record type], [site id], [current effective
> > date], [trait id], [trait value] )
> > SELECT * FROM OPENQUERY ( co-dbdev-01, 'EXEC
> > storeinfo.dbo.pr_traitassignments' )
> >
> > DECLARE @.cmd varchar(400)
> > SET @.cmd = 'INSERT INTO #StoreInfoTraits ([record type], [site id], [current
> > effective date], [trait id], [trait value] )
> > SELECT * FROM OPENQUERY ( co-dbdev-01, ''EXEC
> > storeinfo.dbo.pr_traitassignments'' ) '
> >
> > EXEC ( @.cmd )
> >
> > John
> >
> > "brymer28303" wrote:
> >
> > > Hi All,
> > >
> > > The sending server is SQL 2005 Enterprise SP2 64 bit. The destination
> > > server is SQL 2000 Enterprise SP4.
> > >
> > > I am executing this sql in query analyzer:
> > >
> > > create table #StoreInfoTraits (
> > > [record type] varchar(3),
> > > [site id] int,
> > > [current effective date] smalldatetime,
> > > [trait id] varchar(50),
> > > [trait value] int
> > > )
> > > DECLARE @.cmd as varchar(200)
> > > SET @.cmd = '[co-dbdev-01].storeinfo.dbo.pr_traitassignments'
> > > insert into #StoreInfoTraits exec(@.cmd)
> > > DROP TABLE #StoreInfoTraits
> > >
> > > And getting this error:
> > >
> > > OLE DB provider "SQLNCLI" for linked server "co-dbdev-01" returned message
> > > "The transaction manager has disabled its support for remote/network
> > > transactions.".
> > > Msg 7391, Level 16, State 2, Line 1
> > > The operation could not be performed because OLE DB provider "SQLNCLI" for
> > > linked server "co-dbdev-01" was unable to begin a distributed transaction.
> > >
> > > Iâ've checked the DTC services per the following link and both DTC services
> > > are running under a domain account and configured properly.
> > > http://groups.google.com/group/microsoft.public.sqlserver.server/msg/127255ab5a3a1fe0?hl=en&lr=&ie=UTF-8&oe=UTF-8
> > >
> > > This executes and returns the recordset:
> > > Exec [co-dbdev-01].storeinfo.dbo.pr_traitassignments
> > >
> > > Since the remote stored proc returns the records when executing the stored
> > > proc, is it a DTC issue or is this syntax correct ?
> > > insert into #StoreInfoTraits exec(@.cmd)
> > >
> > >
> > >

Sunday, March 25, 2012

DTS Executable error

DTS Executable error

DTS error when Copying Objects

DTS Error 1st Time

DTS Error 1st Time

DTS Error 1st Time

Wednesday, March 21, 2012

DTS bulk load fails

DTS bulk load fails

DTS bulk load fails

Wednesday, March 7, 2012

DTS - SQL SERVER

DTS - Execute Package Task Problem

Sunday, February 26, 2012

DTS

DTS

Friday, February 24, 2012

DTExec Reporting Options

DTExec Reporting Options

DTExec is the only redist for executing dtsx file?

Sunday, February 19, 2012

DTEXEC / LoadFromSQLServer Failed

DTC issue or SQL Syntax issue

DTC issue or SQL Syntax issue

dts import agent

Blog Archive

About Me