Showing posts with label linked. Show all posts
Showing posts with label linked. Show all posts

Friday, March 23, 2012

Excuting distributed queries in parallel

Hi,

Is it possible to execute queries in parallel on multiple linked servers? I retrieve the checksum of a table on a linked servers like this:

SELECT * FROM OPENQUERY(Server1, 'SELECT CHECKSUM_AGG(BINARY_CHECKSUM(*) FROM Table1')

I need to do this on multiple linked servers at the same time - is this possible? I tried the following but my workstation executes the queries sequentially:

SELECT ("Query Server1"), ("Query Server2"), ("Query Server3"),..

Any suggestions?

Rgds

Bob

TSQL statement execution is always serial in a batch or module. You can run the statements in parallel by doing one of the following:

1. Use on-demand SQL Agent jobs which contain TSQL task with each distributed query. You can then start each job in your TSQL code and wait for their completion

2. In SQL Server 2005, you can use service broker messaging infrastructure to activate multiple procs in parallel with each one executing a specific query

However, it is not clear if you are returning the results to client or processing on the server side itself. If you are returning the results to client then these techniques will not be efficient because you will have to dump the results into a table and then query it back. So you might as well run 3 different commands from the client code.

Monday, March 19, 2012

Exchange Server as a LINKED SERVER

I have successfuly link Exchange to my sql server...what i
am trying to do is fetch all the data of the Exchange and
archive it to an SQL database... my question is it
possible when i got all the information from exchange and
archive it... i can use that archive to restore my
exchange mailboxes or something similar? any suggestions
is highly appreciated...
I don't think so as it's not in the same format needed by Exchange.
You'd want to look at just backing up Exchange. For individual
mailboxes, you could look at brick level backup/restore.
-Sue
On Thu, 9 Sep 2004 01:51:13 -0700, "perry" <kenzai_chuz@.yahoo.com>
wrote:

>I have successfuly link Exchange to my sql server...what i
>am trying to do is fetch all the data of the Exchange and
>archive it to an SQL database... my question is it
>possible when i got all the information from exchange and
>archive it... i can use that archive to restore my
>exchange mailboxes or something similar? any suggestions
>is highly appreciated...
|||Yeah, I think you're right. But my problem is this. If i
use the ExMerge Utility of microsoft, it only permits me
to backup not more that 2gb of file? I am using E2K
server...any suggestions? Because our mails are larger
than 2GB because of the attachments and one more thing...
will ExMerge backup or archive the attachments?
|||No suggestions on the ExMerge issues. You'd probably be
better off posting questions on ExMerge in one of the
Exchange newsgroups. Try:
microsoft.public.exchange2000.admin
-Sue
On Sun, 12 Sep 2004 17:55:14 -0700,
<anonymous@.discussions.microsoft.com> wrote:

>Yeah, I think you're right. But my problem is this. If i
>use the ExMerge Utility of microsoft, it only permits me
>to backup not more that 2gb of file? I am using E2K
>server...any suggestions? Because our mails are larger
>than 2GB because of the attachments and one more thing...
>will ExMerge backup or archive the attachments?

Exchange Linked Server

I'm trying to run a view that calls a table in a linked server (linked to
Exchange on an SBS 03 box)
The linked server shows the correct tables in the Exchange public folders.
The query is;
CREATE VIEW dbo.vw_Exchange_Contacts
AS
SELECT CONVERT(nvarchar(50), [DAV:id]) AS DAVUID, CONVERT(nvarchar(50),
[urn:schemas:Customers:title]) AS Title, CONVERT(nvarchar(50),
[urn:schemas:Customers:sn]) AS Surname,
CONVERT(nvarchar(50), [urn:schemas:Customers:o]) AS Company,
CONVERT(nvarchar(50),
[urn:schemas:Customers:mailingstreet]) AS
Mailing_Street, CONVERT(nvarchar(25), [urn:schemas:Customers:mailingstate])
AS Mailing_State,
CONVERT(nvarchar(25),
[urn:schemas:Customers:mailingpostalcode]) AS Mailing_Postal_Code,
CONVERT(nvarchar(50),
[urn:schemas:Customers:mailingpostaladdress]) AS
Mailing_Postal_Address, CONVERT(nvarchar(50),
[urn:schemas:Customers:mailingcity])
AS Mailing_City, CONVERT(nvarchar(50),
[urn:schemas:Customers:fileas]) AS FileAS, CONVERT(nvarchar(50),
[urn:schemas:Customers:telephoneNumber]) AS Tel,
CONVERT(nvarchar(50), [urn:schemas:Customers:givenName]) AS FirstName
FROM OPENQUERY(Exchange,
'SELECT
"DAV:id","urn:schemas:Customers:title","urn:schema s:Customers:sn","urn:schemas:Customers:o","urn:sch emas:Customers:mailingstreet","urn:schemas:Custome rs:mailingstate","urn:schemas:Customers:mailingpos talcode","urn:schemas:Customers:mailingpostaladdre ss","
urn:schemas:Customers:mailingcity","urn:schemas:Cu stomers:fileas"
,"urn:schemas:Customers:telephoneNumber" ,"urn:schemas:Customers:givenName"
FROM "http://vj-sbs/public/Customers"')
Rowset_2
The problem is that the only field that is returned correctly is the DAV:ID
field; the rest are returned as NULL.
I've run the same sort of view on another SBS 2000 box correctly.
Any thoughts?
I should have added that if there is a better way to achieve the same thing,
i.e. bringing in the contacts from an exchange public folder then I'd also
love to hear about it.
Thanks in advance,
Mike
OnSite Applications.
"Mike" <yada@.yada.com> wrote in message news:42bf610c$1@.quokka.wn.com.au...
> I'm trying to run a view that calls a table in a linked server (linked to
> Exchange on an SBS 03 box)
> The linked server shows the correct tables in the Exchange public folders.
> The query is;
> CREATE VIEW dbo.vw_Exchange_Contacts
> AS
> SELECT CONVERT(nvarchar(50), [DAV:id]) AS DAVUID,
> CONVERT(nvarchar(50), [urn:schemas:Customers:title]) AS Title,
> CONVERT(nvarchar(50),
> [urn:schemas:Customers:sn]) AS Surname,
> CONVERT(nvarchar(50), [urn:schemas:Customers:o]) AS Company,
> CONVERT(nvarchar(50),
> [urn:schemas:Customers:mailingstreet]) AS
> Mailing_Street, CONVERT(nvarchar(25),
> [urn:schemas:Customers:mailingstate]) AS Mailing_State,
> CONVERT(nvarchar(25),
> [urn:schemas:Customers:mailingpostalcode]) AS Mailing_Postal_Code,
> CONVERT(nvarchar(50),
> [urn:schemas:Customers:mailingpostaladdress]) AS
> Mailing_Postal_Address, CONVERT(nvarchar(50),
> [urn:schemas:Customers:mailingcity])
> AS Mailing_City, CONVERT(nvarchar(50),
> [urn:schemas:Customers:fileas]) AS FileAS, CONVERT(nvarchar(50),
> [urn:schemas:Customers:telephoneNumber]) AS Tel,
> CONVERT(nvarchar(50), [urn:schemas:Customers:givenName]) AS FirstName
> FROM OPENQUERY(Exchange,
> 'SELECT
> "DAV:id","urn:schemas:Customers:title","urn:schema s:Customers:sn","urn:schemas:Customers:o","urn:sch emas:Customers:mailingstreet","urn:schemas:Custome rs:mailingstate","urn:schemas:Customers:mailingpos talcode","urn:schemas:Customers:mailingpostaladdre ss"
,"urn:schemas:Customers:mailingcity","urn:schemas: Customers:fileas"
> ,"urn:schemas:Customers:telephoneNumber"
> ,"urn:schemas:Customers:givenName" FROM "http://vj-sbs/public/Customers"')
> Rowset_2
> The problem is that the only field that is returned correctly is the
> DAV:ID field; the rest are returned as NULL.
> I've run the same sort of view on another SBS 2000 box correctly.
> Any thoughts?
>

Exchange Linked Server

I'm trying to run a view that calls a table in a linked server (linked to
Exchange on an SBS 03 box)
The linked server shows the correct tables in the Exchange public folders.
The query is;
CREATE VIEW dbo.vw_Exchange_Contacts
AS
SELECT CONVERT(nvarchar(50), [DAV:id]) AS DAVUID, CONVERT(nvarchar(5
0),
[urn:schemas:Customers:title]) AS Title, CONVERT(nvarchar(50),
[urn:schemas:Customers:sn]) AS Surname,
CONVERT(nvarchar(50), [urn:schemas:Customers:o]) AS Company,
CONVERT(nvarchar(50),
& #91;urn:schemas:Customers:mailingstreet]
) AS
Mailing_Street, CONVERT(nvarchar(25), [urn:schemas:Customers:mailingstat
e])
AS Mailing_State,
CONVERT(nvarchar(25),
& #91;urn:schemas:Customers:mailingpostalc
ode]) AS Mailing_Postal_Code,
CONVERT(nvarchar(50),
& #91;urn:schemas:Customers:mailingpostala
ddress]) AS
Mailing_Postal_Address, CONVERT(nvarchar(50),
[urn:schemas:Customers:mailingcity])
AS Mailing_City, CONVERT(nvarchar(50),
[urn:schemas:Customers:fileas]) AS FileAS, CONVERT(nvarchar(50),
& #91;urn:schemas:Customers:telephoneNumbe
r]) AS Tel,
CONVERT(nvarchar(50), [urn:schemas:Customers:givenName]) AS FirstName
FROM OPENQUERY(Exchange,
'SELECT
"DAV:id","urn:schemas:Customers:title","urn:schemas:Customers:sn","urn:schem
as:Customers:o","urn:schemas:Customers:mailingstreet","urn:schemas:Customers
:mailingstate","urn:schemas:Customers:mailingpostalcode","urn:schemas:Custom
ers:mailingpostaladdress","
urn:schemas:Customers:mailingcity","urn:schemas:Customers:fileas"
,"urn:schemas:Customers:telephoneNumber" ,"urn:schemas:Customers:givenName"
FROM "http://vj-sbs/public/Customers"')
Rowset_2
The problem is that the only field that is returned correctly is the DAV:ID
field; the rest are returned as NULL.
I've run the same sort of view on another SBS 2000 box correctly.
Any thoughts?I should have added that if there is a better way to achieve the same thing,
i.e. bringing in the contacts from an exchange public folder then I'd also
love to hear about it.
Thanks in advance,
Mike
OnSite Applications.
"Mike" <yada@.yada.com> wrote in message news:42bf610c$1@.quokka.wn.com.au...
> I'm trying to run a view that calls a table in a linked server (linked to
> Exchange on an SBS 03 box)
> The linked server shows the correct tables in the Exchange public folders.
> The query is;
> CREATE VIEW dbo.vw_Exchange_Contacts
> AS
> SELECT CONVERT(nvarchar(50), [DAV:id]) AS DAVUID,
> CONVERT(nvarchar(50), [urn:schemas:Customers:title]) AS Title,
> CONVERT(nvarchar(50),
> [urn:schemas:Customers:sn]) AS Surname,
> CONVERT(nvarchar(50), [urn:schemas:Customers:o]) AS Company,
> CONVERT(nvarchar(50),
> & #91;urn:schemas:Customers:mailingstreet]
) AS
> Mailing_Street, CONVERT(nvarchar(25),
> & #91;urn:schemas:Customers:mailingstate])
AS Mailing_State,
> CONVERT(nvarchar(25),
> & #91;urn:schemas:Customers:mailingpostalc
ode]) AS Mailing_Postal_Code,
> CONVERT(nvarchar(50),
> & #91;urn:schemas:Customers:mailingpostala
ddress]) AS
> Mailing_Postal_Address, CONVERT(nvarchar(50),
> [urn:schemas:Customers:mailingcity])
> AS Mailing_City, CONVERT(nvarchar(50),
> [urn:schemas:Customers:fileas]) AS FileAS, CONVERT(nvarchar(50),
> & #91;urn:schemas:Customers:telephoneNumbe
r]) AS Tel,
> CONVERT(nvarchar(50), [urn:schemas:Customers:givenName]) AS FirstName
> FROM OPENQUERY(Exchange,
> 'SELECT
> "DAV:id","urn:schemas:Customers:title","urn:schemas:Customers:sn","urn:schemas:Cus
tomers:o","urn:schemas:Customers:mailingstreet","urn:schemas:Customers:mailingstate"
,"urn:schemas:Customers:mailingpostalcode"," urn:schemas:Customers:mailingpostaladdre
ss"
,"urn:schemas:Customers:mailingcity","urn:schemas:Customers:fileas"
> ,"urn:schemas:Customers:telephoneNumber"
> ,"urn:schemas:Customers:givenName" FROM "http://vj-sbs/public/Customers"')
> Rowset_2
> The problem is that the only field that is returned correctly is the
> DAV:ID field; the rest are returned as NULL.
> I've run the same sort of view on another SBS 2000 box correctly.
> Any thoughts?
>

Sunday, February 26, 2012

Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION reading address 637B7FC0 at 0x77387EAC

Hi i am connecting to a DB2 database on a AS400 machine from SQL server 2005.
I have setup a linked server to connect to the DB2 database.

Most of the time the query ( select * from OPENQUERY(lnkd_svrname,'select abc from svr_name.lib_name.tablename') ) works fine but at times it comes up with the following error.

I am running SQL server 2000 Std. Edition on a WIN 2000 machine.

Any help would be appreciated .

*****ERROR*****

From the Exception.Log file


11/30/06 09:38:59 spid 69 Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION reading address 637B7FC0 at 0x77387EAC

STACK DUMP -

=====================================================================
BugCheck Dump
=====================================================================

This file is generated by Microsoft SQL Server
version 9.00.1399.06
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.


***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0024.txt
SqlDumpExceptionHandler: Process 69 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 11/30/06 09:38:59 spid 69
*
*
* Exception Address = 77387EAC Module(USER32+00007EAC)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 637B7FC0
* Input Buffer 182 bytes -
* select * from OPENQUERY(lnkd_svrname,'select abc from svr_name.lib_name.tablename')

*
*
MODULE BASE END SIZE
* sqlservr 01000000 02BA7FFF 01ba8000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C47FFF 00048000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* Secur32 76F50000 76F62FFF 00013000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* USERENV 76920000 769E3FFF 000c4000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 49DE0000 49E37FFF 00058000
* SHELL32 7C8D0000 7D0D3FFF 00804000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* comctl32 77420000 77522FFF 00103000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* sqlevn70 4F610000 4F7A0FFF 00191000
* SQLOS 344D0000 344D4FFF 00005000
* rsaenh 68000000 6802EFFF 0002f000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 34180000 341C4FFF 00045000
* ole32 77670000 777A3FFF 00134000
* msv1_0 76C90000 76CB6FFF 00027000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 343F0000 34447FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* schannel 76750000 76776FFF 00027000
* COMRES 77010000 770D5FFF 000c6000
* XOLEHLP 344B0000 344B5FFF 00006000
* MSDTCPRX 48070000 480E7FFF 00078000
* msvcp60 780C0000 78120FFF 00061000
* MTXCLU 480F0000 48108FFF 00019000
* VERSION 77B90000 77B97FFF 00008000
* WSOCK32 71BB0000 71BB8FFF 00009000
* OLEAUT32 77D00000 77D8BFFF 0008c000
* CLUSAPI 48110000 48121FFF 00012000
* RESUTILS 48130000 48142FFF 00013000
* DNSAPI 76ED0000 76EFEFFF 0002f000
* winrnr 76F70000 76F76FFF 00007000
* WLDAP32 76F10000 76F3DFFF 0002e000
* rasadhlp 76F80000 76F87FFF 00008000
* security 48570000 48573FFF 00004000
* msfte 49910000 49B67FFF 00258000
* dbghelp 48DD0000 48EE7FFF 00118000
* WINTRUST 76BB0000 76BDAFFF 0002b000
* imagehlp 76C10000 76C38FFF 00029000
* dssenh 68100000 68123FFF 00024000
* hnetcfg 49330000 49388FFF 00059000
* wshtcpip 71AE0000 71AE7FFF 00008000
* NTMARTA 77E00000 77E21FFF 00022000
* SAMLIB 493D0000 493DEFFF 0000f000
* ntdsapi 766F0000 76704FFF 00015000
* xpsp2res 493E0000 496A4FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* sqlncli 496B0000 498CDFFF 0021e000
* COMCTL32 77530000 775C6FFF 00097000
* comdlg32 762B0000 762F9FFF 0004a000
* SQLNCLIR 007A0000 007D2FFF 00033000
* msftepxy 498D0000 498E4FFF 00015000
* xpstar90 62080000 620C4FFF 00045000
* SQLSCM90 620E0000 620E8FFF 00009000
* ODBC32 62100000 6213CFFF 0003d000
* BatchParser90 62140000 6215DFFF 0001e000
* SQLSVC90 62170000 62189FFF 0001a000
* SqlResourceLoader 621A0000 621A5FFF 00006000
* ATL80 7C630000 7C64AFFF 0001b000
* odbcint 62380000 62396FFF 00017000
* SQLSVC90 623A0000 623A2FFF 00003000
* xpstar90 623B0000 623D5FFF 00026000
* xpsqlbot 62400000 62405FFF 00006000
* xplog70 62520000 6252BFFF 0000c000
* xplog70 62540000 62542FFF 00003000
* oledb32 62840000 628B8FFF 00079000
* MSDART 486E0000 486F9FFF 0001a000
* OLEDB32R 488F0000 48900FFF 00011000
* msdasql 62D80000 62DCCFFF 0004d000
* MSDATL3 62DD0000 62DE4FFF 00015000
* MSDASQLR 48700000 48703FFF 00004000
* comsvcs 62F00000 63038FFF 00139000
* cwbodbc 66F30000 66F9CFFF 0006d000
* cwbcore 676C0000 6774BFFF 0008c000
* cwbunpls 64B90000 64B99FFF 0000a000
* MFC42 63040000 63160FFF 00121000
* WININET 77210000 772B7FFF 000a8000
* cwbrw 67590000 675B9FFF 0002a000
* MSVCIRT 62E70000 62E7FFFF 00010000
* SHFOLDER 766D0000 766D8FFF 00009000
* cwbad1 677A0000 677A6FFF 00007000
* CWBUNPLA 64BA0000 64BDAFFF 0003b000
* cwbsof 64E00000 64E2EFFF 0002f000
* cwbnl 67630000 67634FFF 00005000
* cwbsv 67580000 67585FFF 00006000
* cwbco 67750000 67754FFF 00005000
* cwbsy 67570000 67574FFF 00005000
* cwbrc 675C0000 675D0FFF 00011000
* cwbunssl 64B80000 64B8DFFF 0000e000
* cwbad 677B0000 677B3FFF 00004000
* cwbbsspi 67760000 6776FFFF 00010000
* cwbbspc 67770000 67781FFF 00012000
* CWBSOMRI 63200000 6320DFFF 0000e000
* cwbodmsg 63210000 63214FFF 00005000
* odbccp32 63230000 63249FFF 0001a000
* cwbcomsg 63250000 6325DFFF 0000e000
* dbghelp 63540000 63657FFF 00118000
*
* Edi: 61C1EABF: 00000020 C8017800 0001AD48 C8017800 0D092848 82F9DD00
* Esi: 637B7FC1:
* Eax: 637B7FC0:
* Ebx: 0000000A:
* Ecx: 637B7FC0:
* Edx: 00000000:
* Eip: 77387EAC: 8440108A 2BF975D2 33F633C6 D85539D2 5BFF8D0F 45290002
* Ebp: 61C1E848: 61C1E85C 7738A8E8 61C1EAAC 66F88B3C 61C1E86C 61C1EB14
* SegCs: 0000001B:
* EFlags: 00010206: 00450042 005F0052 0046004F 0050005F 004F0052 00450043
* Esp: 61C1E800: 016C5E3D 00000000 61C1F4B8 00000000 FFFFFFFF 00000000
* SegSs: 00000023:
* *******************************************************************************
* -
* Short Stack Dump
77387EAC Module(USER32+00007EAC)
7738A8E8 Module(USER32+0000A8E8)
66F56AC1 Module(cwbodbc+00026AC1)
66F7EA51 Module(cwbodbc+0004EA51)
66F56DC9 Module(cwbodbc+00026DC9)
66F56D44 Module(cwbodbc+00026D44)
66F32EB2 Module(cwbodbc+00002EB2)
66F32BE6 Module(cwbodbc+00002BE6)
62104125 Module(ODBC32+00004125)
621041F3 Module(ODBC32+000041F3)
62D858D8 Module(msdasql+000058D8)
62D8B72F Module(msdasql+0000B72F)
62D8B68F Module(msdasql+0000B68F)
62D8B186 Module(msdasql+0000B186)
62D89A96 Module(msdasql+00009A96)
016C5E3D Module(sqlservr+006C5E3D)
016ABD5A Module(sqlservr+006ABD5A)
01698376 Module(sqlservr+00698376)
01656E53 Module(sqlservr+00656E53)
01E1FE2A Module(sqlservr+00E1FE2A)
010473A7 Module(sqlservr+000473A7)
0103D32C Module(sqlservr+0003D32C)
0103D23D Module(sqlservr+0003D23D)
0103D0C6 Module(sqlservr+0003D0C6)
0102DB52 Module(sqlservr+0002DB52)
0102E0D0 Module(sqlservr+0002E0D0)
0102C5F8 Module(sqlservr+0002C5F8)
010438E5 Module(sqlservr+000438E5)
01041C35 Module(sqlservr+00041C35)
0100889F Module(sqlservr+0000889F)
010089C5 Module(sqlservr+000089C5)
010086E7 Module(sqlservr+000086E7)
010D764A Module(sqlservr+000D764A)
010D7B71 Module(sqlservr+000D7B71)
010D746E Module(sqlservr+000D746E)

You will need to raise this with Microsoft support

http://support.microsoft.com/select/default.aspx?target=assistance&c1=508&

You also say this is SQL 2000 and SQL 2005 which is it?

|||Can you log on to the AS/400 on the machine that you are trying to run the query on?|||No, i just have read access to it|||I guess I should have asked, Can you connect to the AS/400 from the machine where you are trying to run the procedure/task. Do you have the AS/400 client installed, and if so, can you open "client access" and connect?|||

Interesting this thread popped up.

I have run into the exact same problem with my development system that this user is reporting. I came in Monday and I attempted to debug a stored procedure and I got this error.

At first, I thought my code was the culprit. After stripping everything out of my code and just creating a test procedure called 'Hello SQL'

create procedure sTest

AS

print('hello sql')

This failed. I knew something was wrong with my system. I did find one entry in my logs indiciating a problem with the log file for the database last week; however, that entry was a full 3 days prior to this problem appearing.

I found a few MS articles on the error on Technet and have applied those fixes and they didn't fix the problem.

This is really bizarre. I've ran across enough people posting issues on this problem to think that it is not an uncommon occurence.

|||

Hi,

The key to the AV exception is the callstack provided - unfortunately, there haven't been proper symbols available to shed more light on the faulty call. Still - the exception seems to be due to an operation which the ODBC driver has initiated. In our case, this appears to be the IBM's DB2 ODBC driver (CWBODBC.DLL). It is not clear what it called, but from a speculative review of my own user32.dll, it seems its this:

user32!wvsprintfA

(I assume you are familiar with printf, sprintf, wsprintf, etc.) - this would match Bergen's findings very nicely. I would say that the driver is trying to output something - this may be incompatible when running within the SQL Server process to begin with. :-) And is most likely a bug in the driver itself.

What I would do is to search for the latest update for the CWBODBC.DLL driver and install it. If the problems persist, you could contact IBM's support and provide them with the callstack and the version of the CWBODBC.DLL module - they should be able to find the actual issue in no time.

If you have any additional questions, please post.

HTH,

Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||The problem was fixed by installing the latest service pack for the client access ODBC driver

Thanks

Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION reading address 637B7FC0 at 0x77387EAC

Hi i am connecting to a DB2 database on a AS400 machine from SQL server 2005.
I have setup a linked server to connect to the DB2 database.

Most of the time the query ( select * from OPENQUERY(lnkd_svrname,'select abc from svr_name.lib_name.tablename') ) works fine but at times it comes up with the following error.

I am running SQL server 2000 Std. Edition on a WIN 2000 machine.

Any help would be appreciated .

*****ERROR*****

From the Exception.Log file


11/30/06 09:38:59 spid 69 Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION reading address 637B7FC0 at 0x77387EAC

STACK DUMP -

=====================================================================
BugCheck Dump
=====================================================================

This file is generated by Microsoft SQL Server
version 9.00.1399.06
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.


***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0024.txt
SqlDumpExceptionHandler: Process 69 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 11/30/06 09:38:59 spid 69
*
*
* Exception Address = 77387EAC Module(USER32+00007EAC)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 637B7FC0
* Input Buffer 182 bytes -
* select * from OPENQUERY(lnkd_svrname,'select abc from svr_name.lib_name.tablename')

*
*
MODULE BASE END SIZE
* sqlservr 01000000 02BA7FFF 01ba8000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C47FFF 00048000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* Secur32 76F50000 76F62FFF 00013000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* USERENV 76920000 769E3FFF 000c4000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 49DE0000 49E37FFF 00058000
* SHELL32 7C8D0000 7D0D3FFF 00804000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* comctl32 77420000 77522FFF 00103000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* sqlevn70 4F610000 4F7A0FFF 00191000
* SQLOS 344D0000 344D4FFF 00005000
* rsaenh 68000000 6802EFFF 0002f000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 34180000 341C4FFF 00045000
* ole32 77670000 777A3FFF 00134000
* msv1_0 76C90000 76CB6FFF 00027000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 343F0000 34447FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* schannel 76750000 76776FFF 00027000
* COMRES 77010000 770D5FFF 000c6000
* XOLEHLP 344B0000 344B5FFF 00006000
* MSDTCPRX 48070000 480E7FFF 00078000
* msvcp60 780C0000 78120FFF 00061000
* MTXCLU 480F0000 48108FFF 00019000
* VERSION 77B90000 77B97FFF 00008000
* WSOCK32 71BB0000 71BB8FFF 00009000
* OLEAUT32 77D00000 77D8BFFF 0008c000
* CLUSAPI 48110000 48121FFF 00012000
* RESUTILS 48130000 48142FFF 00013000
* DNSAPI 76ED0000 76EFEFFF 0002f000
* winrnr 76F70000 76F76FFF 00007000
* WLDAP32 76F10000 76F3DFFF 0002e000
* rasadhlp 76F80000 76F87FFF 00008000
* security 48570000 48573FFF 00004000
* msfte 49910000 49B67FFF 00258000
* dbghelp 48DD0000 48EE7FFF 00118000
* WINTRUST 76BB0000 76BDAFFF 0002b000
* imagehlp 76C10000 76C38FFF 00029000
* dssenh 68100000 68123FFF 00024000
* hnetcfg 49330000 49388FFF 00059000
* wshtcpip 71AE0000 71AE7FFF 00008000
* NTMARTA 77E00000 77E21FFF 00022000
* SAMLIB 493D0000 493DEFFF 0000f000
* ntdsapi 766F0000 76704FFF 00015000
* xpsp2res 493E0000 496A4FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* sqlncli 496B0000 498CDFFF 0021e000
* COMCTL32 77530000 775C6FFF 00097000
* comdlg32 762B0000 762F9FFF 0004a000
* SQLNCLIR 007A0000 007D2FFF 00033000
* msftepxy 498D0000 498E4FFF 00015000
* xpstar90 62080000 620C4FFF 00045000
* SQLSCM90 620E0000 620E8FFF 00009000
* ODBC32 62100000 6213CFFF 0003d000
* BatchParser90 62140000 6215DFFF 0001e000
* SQLSVC90 62170000 62189FFF 0001a000
* SqlResourceLoader 621A0000 621A5FFF 00006000
* ATL80 7C630000 7C64AFFF 0001b000
* odbcint 62380000 62396FFF 00017000
* SQLSVC90 623A0000 623A2FFF 00003000
* xpstar90 623B0000 623D5FFF 00026000
* xpsqlbot 62400000 62405FFF 00006000
* xplog70 62520000 6252BFFF 0000c000
* xplog70 62540000 62542FFF 00003000
* oledb32 62840000 628B8FFF 00079000
* MSDART 486E0000 486F9FFF 0001a000
* OLEDB32R 488F0000 48900FFF 00011000
* msdasql 62D80000 62DCCFFF 0004d000
* MSDATL3 62DD0000 62DE4FFF 00015000
* MSDASQLR 48700000 48703FFF 00004000
* comsvcs 62F00000 63038FFF 00139000
* cwbodbc 66F30000 66F9CFFF 0006d000
* cwbcore 676C0000 6774BFFF 0008c000
* cwbunpls 64B90000 64B99FFF 0000a000
* MFC42 63040000 63160FFF 00121000
* WININET 77210000 772B7FFF 000a8000
* cwbrw 67590000 675B9FFF 0002a000
* MSVCIRT 62E70000 62E7FFFF 00010000
* SHFOLDER 766D0000 766D8FFF 00009000
* cwbad1 677A0000 677A6FFF 00007000
* CWBUNPLA 64BA0000 64BDAFFF 0003b000
* cwbsof 64E00000 64E2EFFF 0002f000
* cwbnl 67630000 67634FFF 00005000
* cwbsv 67580000 67585FFF 00006000
* cwbco 67750000 67754FFF 00005000
* cwbsy 67570000 67574FFF 00005000
* cwbrc 675C0000 675D0FFF 00011000
* cwbunssl 64B80000 64B8DFFF 0000e000
* cwbad 677B0000 677B3FFF 00004000
* cwbbsspi 67760000 6776FFFF 00010000
* cwbbspc 67770000 67781FFF 00012000
* CWBSOMRI 63200000 6320DFFF 0000e000
* cwbodmsg 63210000 63214FFF 00005000
* odbccp32 63230000 63249FFF 0001a000
* cwbcomsg 63250000 6325DFFF 0000e000
* dbghelp 63540000 63657FFF 00118000
*
* Edi: 61C1EABF: 00000020 C8017800 0001AD48 C8017800 0D092848 82F9DD00
* Esi: 637B7FC1:
* Eax: 637B7FC0:
* Ebx: 0000000A:
* Ecx: 637B7FC0:
* Edx: 00000000:
* Eip: 77387EAC: 8440108A 2BF975D2 33F633C6 D85539D2 5BFF8D0F 45290002
* Ebp: 61C1E848: 61C1E85C 7738A8E8 61C1EAAC 66F88B3C 61C1E86C 61C1EB14
* SegCs: 0000001B:
* EFlags: 00010206: 00450042 005F0052 0046004F 0050005F 004F0052 00450043
* Esp: 61C1E800: 016C5E3D 00000000 61C1F4B8 00000000 FFFFFFFF 00000000
* SegSs: 00000023:
* *******************************************************************************
* -
* Short Stack Dump
77387EAC Module(USER32+00007EAC)
7738A8E8 Module(USER32+0000A8E8)
66F56AC1 Module(cwbodbc+00026AC1)
66F7EA51 Module(cwbodbc+0004EA51)
66F56DC9 Module(cwbodbc+00026DC9)
66F56D44 Module(cwbodbc+00026D44)
66F32EB2 Module(cwbodbc+00002EB2)
66F32BE6 Module(cwbodbc+00002BE6)
62104125 Module(ODBC32+00004125)
621041F3 Module(ODBC32+000041F3)
62D858D8 Module(msdasql+000058D8)
62D8B72F Module(msdasql+0000B72F)
62D8B68F Module(msdasql+0000B68F)
62D8B186 Module(msdasql+0000B186)
62D89A96 Module(msdasql+00009A96)
016C5E3D Module(sqlservr+006C5E3D)
016ABD5A Module(sqlservr+006ABD5A)
01698376 Module(sqlservr+00698376)
01656E53 Module(sqlservr+00656E53)
01E1FE2A Module(sqlservr+00E1FE2A)
010473A7 Module(sqlservr+000473A7)
0103D32C Module(sqlservr+0003D32C)
0103D23D Module(sqlservr+0003D23D)
0103D0C6 Module(sqlservr+0003D0C6)
0102DB52 Module(sqlservr+0002DB52)
0102E0D0 Module(sqlservr+0002E0D0)
0102C5F8 Module(sqlservr+0002C5F8)
010438E5 Module(sqlservr+000438E5)
01041C35 Module(sqlservr+00041C35)
0100889F Module(sqlservr+0000889F)
010089C5 Module(sqlservr+000089C5)
010086E7 Module(sqlservr+000086E7)
010D764A Module(sqlservr+000D764A)
010D7B71 Module(sqlservr+000D7B71)
010D746E Module(sqlservr+000D746E)

You will need to raise this with Microsoft support

http://support.microsoft.com/select/default.aspx?target=assistance&c1=508&

You also say this is SQL 2000 and SQL 2005 which is it?

|||Can you log on to the AS/400 on the machine that you are trying to run the query on?|||No, i just have read access to it|||I guess I should have asked, Can you connect to the AS/400 from the machine where you are trying to run the procedure/task. Do you have the AS/400 client installed, and if so, can you open "client access" and connect?|||

Interesting this thread popped up.

I have run into the exact same problem with my development system that this user is reporting. I came in Monday and I attempted to debug a stored procedure and I got this error.

At first, I thought my code was the culprit. After stripping everything out of my code and just creating a test procedure called 'Hello SQL'

create procedure sTest

AS

print('hello sql')

This failed. I knew something was wrong with my system. I did find one entry in my logs indiciating a problem with the log file for the database last week; however, that entry was a full 3 days prior to this problem appearing.

I found a few MS articles on the error on Technet and have applied those fixes and they didn't fix the problem.

This is really bizarre. I've ran across enough people posting issues on this problem to think that it is not an uncommon occurence.

|||

Hi,

The key to the AV exception is the callstack provided - unfortunately, there haven't been proper symbols available to shed more light on the faulty call. Still - the exception seems to be due to an operation which the ODBC driver has initiated. In our case, this appears to be the IBM's DB2 ODBC driver (CWBODBC.DLL). It is not clear what it called, but from a speculative review of my own user32.dll, it seems its this:

user32!wvsprintfA

(I assume you are familiar with printf, sprintf, wsprintf, etc.) - this would match Bergen's findings very nicely. I would say that the driver is trying to output something - this may be incompatible when running within the SQL Server process to begin with. :-) And is most likely a bug in the driver itself.

What I would do is to search for the latest update for the CWBODBC.DLL driver and install it. If the problems persist, you could contact IBM's support and provide them with the callstack and the version of the CWBODBC.DLL module - they should be able to find the actual issue in no time.

If you have any additional questions, please post.

HTH,

Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||The problem was fixed by installing the latest service pack for the client access ODBC driver

Thanks

Wednesday, February 15, 2012

Excel Linked Server Problem

To All

I'm using the following code to create a Linked Excel server.

EXEC sp_addlinkedserver 'ExcelSource',

'Jet 4.0',

'Microsoft.Jet.OLEDB.4.0',

'\\schuette-dc\DriveH\Temp\EDI\CSCNEDI.xls',

NULL,

'Excel 8.0';

GO

--

The server create correctly, but when I try the following

SELECT * FROM ExcelSource...CSCN

I get the following error

-

[OLE/DB provider returned message: Unspecified error]

OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0' IDBInitialize::Initialize returned 0x80004005: ].

Msg 7399, Level 16, State 1, Line 15

OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.

-

I have verified that i have full access to the "Temp" directory. I have even tried creating a "Named Range" in the spreadsheet with no success.

Thanks

David Davis

Tried on XP SP2 machine and it works fine for me. Try using OpenRowset and see if it works

select * from OpenRowset( 'Microsoft.Jet.OLEDB.4.0', 'Excel 8.0;Database=\\schuette-dc\DriveH\Temp\EDI\CSCNEDI.xls', 'select * from CSCN')

OpenRowset documentation: http://msdn2.microsoft.com/en-us/library/ms190312.aspx

OpenQuery documentation: http://msdn2.microsoft.com/en-us/library/ms188427.aspx

Also take a look at this : http://groups.google.com/group/microsoft.public.sqlserver.programming/browse_thread/thread/6fbf566977fe8504/5871e88b33c1445b?lnk=st&q=OLE+DB+error+trace+%5BOLE%2FDB+Provider+%27Microsoft.Jet.OLEDB.4.0%27+IDBInitialize%3A%3AInitialize+returned+0x80004005%3A+%5D.&rnum=8&hl=en#5871e88b33c1445b

Hope this helps

|||

Raj

I tried the statement and get the same error message.

Thanks

David Davis

|||Hi, anyone solved this problem yet?

My error is the same. I have seen many reports of this problem but no answers.

Thanks.