Showing posts with label files. Show all posts
Showing posts with label files. Show all posts

Thursday, March 29, 2012

exectuing a .bat from cmdexec

All,
sql 2000 sp3
I have a .bat file at d:\wip\queries.bat, the step succeeds, but there is no
data in the files that I am creating. Below is the contents of the .bat. I
have 'd:\queries.bat' in the cmdexec step. I have verified the odbc
connection, any other ideas would be a great help.
db2cmd /c /w /i db2 +o -tf ds1_query.sql -r d:\wip\ds1_query.txt
db2cmd /c /w /i db2 +o -tf ds2_wrs_ind_employee_db2_query.sql -r
d:\wip\ds2_wrs_ind_employee_db2.txt
db2cmd /c /w /i db2 +o -tf ds3_wrs_clr_employee_db2_query.sql -r
d:\wip\ds3_wrs_clr_employee_db2.txt
db2cmd /c /w /i db2 +o -tf ds4_wrs_client_db2_query.sql -r
d:\wip\ds4_wrs_client_db2.txt
db2cmd /c /w /i db2 +o -tf ds5_wrs_diary_db2_query.sql -r
d:\wip\ds5_wrs_diary_db2.txt
db2cmd /c /w /i db2 +o -tf ds6_wrs_dry_history_db2_query.sql -r
d:\wip\ds6_wrs_dry_history_db2.txt
db2cmd /c /w /i db2 +o -tf ds7_wrs_folder_control_db2_query.sql -r
d:\wip\ds7_wrs_folder_control_db2.txt
--
Thanks,
SnyperSorry, the step does fail. I see it in the appliction log as a failure. I do
not know how to get the .bat to execute properly. Any ideas?
--
Thanks,
Snyper
"snyper" wrote:
> All,
> sql 2000 sp3
> I have a .bat file at d:\wip\queries.bat, the step succeeds, but there is no
> data in the files that I am creating. Below is the contents of the .bat. I
> have 'd:\queries.bat' in the cmdexec step. I have verified the odbc
> connection, any other ideas would be a great help.
> db2cmd /c /w /i db2 +o -tf ds1_query.sql -r d:\wip\ds1_query.txt
> db2cmd /c /w /i db2 +o -tf ds2_wrs_ind_employee_db2_query.sql -r
> d:\wip\ds2_wrs_ind_employee_db2.txt
> db2cmd /c /w /i db2 +o -tf ds3_wrs_clr_employee_db2_query.sql -r
> d:\wip\ds3_wrs_clr_employee_db2.txt
> db2cmd /c /w /i db2 +o -tf ds4_wrs_client_db2_query.sql -r
> d:\wip\ds4_wrs_client_db2.txt
> db2cmd /c /w /i db2 +o -tf ds5_wrs_diary_db2_query.sql -r
> d:\wip\ds5_wrs_diary_db2.txt
> db2cmd /c /w /i db2 +o -tf ds6_wrs_dry_history_db2_query.sql -r
> d:\wip\ds6_wrs_dry_history_db2.txt
> db2cmd /c /w /i db2 +o -tf ds7_wrs_folder_control_db2_query.sql -r
> d:\wip\ds7_wrs_folder_control_db2.txt
> --
> Thanks,
> Snyper|||Snyper
Although i know nothing of the detail of what you are trying to do here ...
If running the indiviual commands are being created but not populted then
perhaps it might be worth looking at it being a permissions error in creating
the information or permisiions on population the file.
when you run one of these commands what permissions context is it running
under
under, your id, under the os id or under the applicaion you are running the
commands from.
Are the drive letters in the contect of the user and location you are
running them from ie if runnind this on a remote serverits D: will not be the
same as you d:
perhap you need to qualify the files such \\<severname>\<sharename>
Can you break these commands down
a simpler command to say display a directory listing work via this method ie
the cmdexec works but not he commnd you are running...
"snyper" wrote:
> Sorry, the step does fail. I see it in the appliction log as a failure. I do
> not know how to get the .bat to execute properly. Any ideas?
> --
> Thanks,
> Snyper
>
> "snyper" wrote:
> > All,
> >
> > sql 2000 sp3
> >
> > I have a .bat file at d:\wip\queries.bat, the step succeeds, but there is no
> > data in the files that I am creating. Below is the contents of the .bat. I
> > have 'd:\queries.bat' in the cmdexec step. I have verified the odbc
> > connection, any other ideas would be a great help.
> >
> > db2cmd /c /w /i db2 +o -tf ds1_query.sql -r d:\wip\ds1_query.txt
> > db2cmd /c /w /i db2 +o -tf ds2_wrs_ind_employee_db2_query.sql -r
> > d:\wip\ds2_wrs_ind_employee_db2.txt
> > db2cmd /c /w /i db2 +o -tf ds3_wrs_clr_employee_db2_query.sql -r
> > d:\wip\ds3_wrs_clr_employee_db2.txt
> > db2cmd /c /w /i db2 +o -tf ds4_wrs_client_db2_query.sql -r
> > d:\wip\ds4_wrs_client_db2.txt
> > db2cmd /c /w /i db2 +o -tf ds5_wrs_diary_db2_query.sql -r
> > d:\wip\ds5_wrs_diary_db2.txt
> > db2cmd /c /w /i db2 +o -tf ds6_wrs_dry_history_db2_query.sql -r
> > d:\wip\ds6_wrs_dry_history_db2.txt
> > db2cmd /c /w /i db2 +o -tf ds7_wrs_folder_control_db2_query.sql -r
> > d:\wip\ds7_wrs_folder_control_db2.txt
> > --
> >
> > Thanks,
> >
> > Snyper

exectuing a .bat from cmdexec

All,
sql 2000 sp3
I have a .bat file at d:\wip\queries.bat, the step succeeds, but there is no
data in the files that I am creating. Below is the contents of the .bat. I
have 'd:\queries.bat' in the cmdexec step. I have verified the odbc
connection, any other ideas would be a great help.
db2cmd /c /w /i DB2 +o -tf ds1_query.sql -r d:\wip\ds1_query.txt
db2cmd /c /w /i DB2 +o -tf ds2_wrs_ind_employee_db2_query.sql -r
d:\wip\ds2_wrs_ind_employee_db2.txt
db2cmd /c /w /i DB2 +o -tf ds3_wrs_clr_employee_db2_query.sql -r
d:\wip\ds3_wrs_clr_employee_db2.txt
db2cmd /c /w /i DB2 +o -tf ds4_wrs_client_db2_query.sql -r
d:\wip\ds4_wrs_client_db2.txt
db2cmd /c /w /i DB2 +o -tf ds5_wrs_diary_db2_query.sql -r
d:\wip\ds5_wrs_diary_db2.txt
db2cmd /c /w /i DB2 +o -tf ds6_wrs_dry_history_db2_query.sql -r
d:\wip\ds6_wrs_dry_history_db2.txt
db2cmd /c /w /i DB2 +o -tf ds7_wrs_folder_control_db2_query.sql -r
d:\wip\ds7_wrs_folder_control_db2.txt
--
Thanks,
SnyperSorry, the step does fail. I see it in the appliction log as a failure. I do
not know how to get the .bat to execute properly. Any ideas?
--
Thanks,
Snyper
"snyper" wrote:

> All,
> sql 2000 sp3
> I have a .bat file at d:\wip\queries.bat, the step succeeds, but there is
no
> data in the files that I am creating. Below is the contents of the .bat. I
> have 'd:\queries.bat' in the cmdexec step. I have verified the odbc
> connection, any other ideas would be a great help.
> db2cmd /c /w /i DB2 +o -tf ds1_query.sql -r d:\wip\ds1_query.txt
> db2cmd /c /w /i DB2 +o -tf ds2_wrs_ind_employee_db2_query.sql -r
> d:\wip\ds2_wrs_ind_employee_db2.txt
> db2cmd /c /w /i DB2 +o -tf ds3_wrs_clr_employee_db2_query.sql -r
> d:\wip\ds3_wrs_clr_employee_db2.txt
> db2cmd /c /w /i DB2 +o -tf ds4_wrs_client_db2_query.sql -r
> d:\wip\ds4_wrs_client_db2.txt
> db2cmd /c /w /i DB2 +o -tf ds5_wrs_diary_db2_query.sql -r
> d:\wip\ds5_wrs_diary_db2.txt
> db2cmd /c /w /i DB2 +o -tf ds6_wrs_dry_history_db2_query.sql -r
> d:\wip\ds6_wrs_dry_history_db2.txt
> db2cmd /c /w /i DB2 +o -tf ds7_wrs_folder_control_db2_query.sql -r
> d:\wip\ds7_wrs_folder_control_db2.txt
> --
> Thanks,
> Snyper|||Snyper
Although i know nothing of the detail of what you are trying to do here ...
If running the indiviual commands are being created but not populted then
perhaps it might be worth looking at it being a permissions error in creatin
g
the information or permisiions on population the file.
when you run one of these commands what permissions context is it running
under
under, your id, under the os id or under the applicaion you are running the
commands from.
Are the drive letters in the contect of the user and location you are
running them from ie if runnind this on a remote serverits D: will not be th
e
same as you d:
perhap you need to qualify the files such \\<severname>\<sharename>
Can you break these commands down
a simpler command to say display a directory listing work via this method ie
the cmdexec works but not he commnd you are running...
"snyper" wrote:
[vbcol=seagreen]
> Sorry, the step does fail. I see it in the appliction log as a failure. I
do
> not know how to get the .bat to execute properly. Any ideas?
> --
> Thanks,
> Snyper
>
> "snyper" wrote:
>

Friday, March 9, 2012

Excess Log file sizes

Hello, we've had some issues with our backups and some of our log files have
grown to 15 GB. We since corrected the problem and backups are running
again but the log files remain the same size.
In one particular case, I have a database that, via Taskpad, I can see is
45GB with 26GB of free space and the log is 15GB with 14.8 GB of free space.
I notice on the properties page for this database that AutoShrink is not
checked. Is this the problem? Is there any downside to enabling
autoshrink?
I've read all different articles that give instructions on compacting this
and wanted to know what you folks thought would be the preferred way to A)
reducing the log file size issues I not face and B) best practices for
keeping them from reoccurring once I get these files down to where they
should be.
Any help would be appreciated!
Jim
If you've seen this article, then the rest will probably tell you the
same...
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Ekrem nsoy
"Jim" <jj@.nospam.com> wrote in message
news:%23Lz1vbwnIHA.2396@.TK2MSFTNGP02.phx.gbl...
> Hello, we've had some issues with our backups and some of our log files
> have grown to 15 GB. We since corrected the problem and backups are
> running again but the log files remain the same size.
> In one particular case, I have a database that, via Taskpad, I can see is
> 45GB with 26GB of free space and the log is 15GB with 14.8 GB of free
> space.
> I notice on the properties page for this database that AutoShrink is not
> checked. Is this the problem? Is there any downside to enabling
> autoshrink?
> I've read all different articles that give instructions on compacting this
> and wanted to know what you folks thought would be the preferred way to A)
> reducing the log file size issues I not face and B) best practices for
> keeping them from reoccurring once I get these files down to where they
> should be.
> Any help would be appreciated!
> Jim
>

Excess Log file sizes

Hello, we've had some issues with our backups and some of our log files have
grown to 15 GB. We since corrected the problem and backups are running
again but the log files remain the same size.
In one particular case, I have a database that, via Taskpad, I can see is
45GB with 26GB of free space and the log is 15GB with 14.8 GB of free space.
I notice on the properties page for this database that AutoShrink is not
checked. Is this the problem? Is there any downside to enabling
autoshrink?
I've read all different articles that give instructions on compacting this
and wanted to know what you folks thought would be the preferred way to A)
reducing the log file size issues I not face and B) best practices for
keeping them from reoccurring once I get these files down to where they
should be.
Any help would be appreciated!
JimIf you've seen this article, then the rest will probably tell you the
same...
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
--
Ekrem Önsoy
"Jim" <jj@.nospam.com> wrote in message
news:%23Lz1vbwnIHA.2396@.TK2MSFTNGP02.phx.gbl...
> Hello, we've had some issues with our backups and some of our log files
> have grown to 15 GB. We since corrected the problem and backups are
> running again but the log files remain the same size.
> In one particular case, I have a database that, via Taskpad, I can see is
> 45GB with 26GB of free space and the log is 15GB with 14.8 GB of free
> space.
> I notice on the properties page for this database that AutoShrink is not
> checked. Is this the problem? Is there any downside to enabling
> autoshrink?
> I've read all different articles that give instructions on compacting this
> and wanted to know what you folks thought would be the preferred way to A)
> reducing the log file size issues I not face and B) best practices for
> keeping them from reoccurring once I get these files down to where they
> should be.
> Any help would be appreciated!
> Jim
>

EXCEPTION_ACCESS_VIOLATION when installing June CTP

Hi - I'm trying to install June CTP on Win2k3 SP1.
Setup failed when trying to start services for configuration.
In log files I found the following
Computer type is AT/AT COMPATIBLE.
Bios Version is INSYDE - 1
Insyde Software MobilePRO BIOS Version 4.00.01
Current time is 11:26:54 08/30/05.
1 Intel x86 level 15, 3 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.

Memory
MemoryLoad = 57%
Total Physical = 959 MB
Available Physical = 408 MB
Total Page File = 2329 MB
Available Page File = 1812 MB
Total Virtual = 2047 MB
Available Virtual = 1014 MB
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\log\SQLDump0001.txt
SqlDumpExceptionHandler: Process 5180 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server i
s terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 08/30/05 11:26:54 spid 0
*
*
* Exception Address = 77BD8944 (strncmp + 00000014)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00330072
*
* MODULE BASE END SIZE
* sqlservr 00400000 01DDEFFF 019df000
* Invalid Address 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* msvcrt 77BA0000 77BF9FFF 0005a000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C47FFF 00048000
* MSVCP80 7C420000 7C4A4FFF 00085000
* MSVCR80 7C370000 7C408FFF 00099000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* NETAPI32 71C40000 71C97FFF 00058000
* opends60 41060000 41065FFF 00006000
* Secur32 76F50000 76F62FFF 00013000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* USERENV 76920000 769E3FFF 000c4000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 02310000 02318FFF 00009000
* sqlevn70 41070000 411ECFFF 0017d000
* SQLOS 02350000 02354FFF 00005000
* rsaenh 68000000 6802EFFF 0002f000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 78800000 7883FFFF 00040000
* ole32 77670000 777A3FFF 00134000
* msv1_0 76C90000 76CB6FFF 00027000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 71CA0000 71CF7FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* schannel 76750000 76776FFF 00027000
* security 71F60000 71F63FFF 00004000
* VERSION 77B90000 77B97FFF 00008000
* dssenh 68100000 68123FFF 00024000
* hnetcfg 5F270000 5F2C8FFF 00059000
* wshtcpip 71AE0000 71AE7FFF 00008000
* DNSAPI 76ED0000 76EF8FFF 00029000
* winrnr 76F70000 76F76FFF 00007000
* WLDAP32 76F10000 76F3DFFF 0002e000
* rasadhlp 76F80000 76F84FFF 00005000
* ntdsapi 766F0000 76704FFF 00015000
* dbghelp 3FA40000 3FB49FFF 0010a000
*
* Edi: 00330072:
* Esi: 00330072:
* Eax: 00000000:
* Ebx: 00000008:
* Ecx: 00000008:
* Edx: 01020001: EC83EC8B 78816608 53008002 820F5756 000000A3 8510508D
* Eip: 77BD8944: D9F7AEF2 FE8BCB03 F30C758B FF468AA6 473AC933 740577FF
* Ebp: 3F6EF3A8: 3F6EF3E4 766F4FF6 00330072 766F4F84 00000008 0194A7FC
* SegCs: 0000001B:
* EFlags: 00010246: 00730075 00650074 005C0072 006C0063 00730075 00650074
* Esp: 3F6EF39C: 3F6EF410 77BD8930 766F4F84 3F6EF3E4 766F4FF6 00330072
* SegSs: 00000023:
* *******************************************************************************
* -
* Short Stack Dump
Any help will be appreciated.The AV is happening in the SQL Server engine. I've moved your post to the SQL DB Engine forum. Maybe someone here can help you.

Dan|||Alexandr,

Are you still getting this error? Can you start the service manually?

From the fragment of the output you have provided there is no way to tell what is wrong.

We either need a full dump file (C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\log\SQLDump0001.txt) or paste Short Stack Dump.

Regards,
Boris.|||Thanks for reply Boris.
I have reinstalled SQL Server on a brand new OS and it works fine now.

With the previous installation - i cannot start service manually - it gives the same error. I've tried to install SQL Express - and it gives the same error again.
I tried to start SQL Server even not as a service but as a console app - and it gives that error.
That may be happend because I already has installed SQL 2000 and MSDE on my PC.

Regards,
Alexandr.|||Alexandr,

An instance of SQL Server 2005 should coexist just fine with SQL Server 2000. I don't think that is the reason for the AV you were getting, although this is just a guess.

Since you have reinstalled the OS, I wonder if you have kept the dump file(s) that were created when the server generated the AV.

If yes, could you paste short stack dump here and we can take a further look.

Thank you,
Boris.|||Boris,

SQLServer 2005 works fine with SQL 2000 installed on the same box.
I haven't kept the stack dump or log files.

Thanks,
Alexandr.

EXCEPTION_ACCESS_VIOLATION

I have two different Production Servers which are creating SQLDump00*** files.
I suspect the issue is to do with Paralellism. As on one of the servers I
set the MAXDOP to 1 and it has cured the problem.
Someone in my office seems to think the issue has something to do with
language_exec as it appears in all the logs. Can someone please tell me what
this term means.
The error in event view is:
SqlDumpExceptionHandler: Process 81 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
The Dump file generates:
================================================== ===================
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.
Current time is 08:40:42 04/28/05.
8 Intel x86 level 15, 1999 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory
MemoryLoad = 78%
Total Physical = 3775 MB
Available Physical = 794 MB
Total Page File = 5669 MB
Available Page File = 2663 MB
Total Virtual = 3071 MB
Available Virtual = 265 MB
*Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL\log\SQLDu
mp0041.txt
*
************************************************** ***************************
**
*
* BEGIN STACK DUMP:
* 04/28/05 08:40:42 spid 70
*
* Exception Address = 00662572 (udf::udf + 00000127 Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000000
* Input Buffer 4088 bytes -
* SELECT repExposureCust."HostName", repExposureCust."PortfolioClassSort",
* repExposureCust."PortfolioClass", repExposureCust."CustID", repExposure
* Cust."PfolCustCode", repExposureCust."PfolCustName", repExposureCust."Pf
* olProdName", repExposureCust."PfolBranName", repExposureCust."PfolCptyCo
* de", repExposureCust."PfolPGRatCode", repExposureCust."ItemClassID", rep
* ExposureCust."PfolItemClass", repExposureCust."PortfolioID", repExposure
* Cust."MeasureID", repExposureCust."DataMonth", repExposureCust."DaysInEx
* cess", repExposureCust."LimMax01", repExposureCust."LimMin01", repExposu
* reCust."ExpMax01", repExposureCust."ExpMin01", repExposureCust."ExpAvg01
* ", repExposureCust."LimMax02", repExposureCust."LimMin02", repExposureCu
* st."ExpMax02", repExposureCust."ExpMin02", repExposureCust."ExpAvg02", r
* epExposureCust."LimMax03", repExposureCust."LimMin03", repExposureCust."
* ExpMax03", repExposureCust."ExpMin03", repExposureCust."ExpAvg03", repEx
* posureCust."LimMax04", repExposureCust."LimMin04", repExposureCust."ExpM
* ax04", repExposureCust."ExpMin04", repExposureCust."ExpAvg04", repExposu
* reCust."LimMax05", repExposureCust."LimMin05", repExposureCust."ExpMax05
* ", repExposureCust."ExpMin05", repExposureCust."ExpAvg05", repExposureCu
* st."LimMax06", repExposureCust."LimMin06", repExposureCust."ExpMax06", r
* epExposureCust."ExpMin06", repExposureCust."ExpAvg06", repExposureCust."
* LimMax07", repExposureCust."LimMin07", repExposureCust."ExpMax07", repEx
* posureCust."ExpMin07", repExposureCust."ExpAvg07", repExposureCust."LimM
* ax08", repExposureCust."LimMin08", repExposureCust."ExpMax08", repExposu
* reCust."ExpMin08", repExposureCust."ExpAvg08", repExposureCust."LimMax09
* ", repExposureCust."LimMin09", repExposureCust."ExpMax09", repExposureCu
* st."ExpMin09", repExposureCust."ExpAvg09", repExposureCust."LimMax10", r
* epExposureCust."LimMin10", repExposureCust."ExpMax10", repExposureCust."
* ExpMin10", repExposureCust."ExpAvg10", repExposureCust."Measure", repExp
* osureCust."LimitAttribute", repExposureCust."LimCurrSpot", repExposureCu
* st."ChecksClassSymbol", repE
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00B2CFFF 0072d000
* ntdll 77F80000 77FFCFFF 0007d000
* KERNEL32 7C570000 7C627FFF 000b8000
* ADVAPI32 7C2D0000 7C331FFF 00062000
* RPCRT4 77D30000 77D9DFFF 0006e000
* USER32 77E10000 77E74FFF 00065000
* GDI32 77F40000 77F7DFFF 0003e000
* OPENDS60 41060000 41065FFF 00006000
* MSVCRT 78000000 78044FFF 00045000
* UMS 41070000 4107CFFF 0000d000
* SQLSORT 42AE0000 42B6FFFF 00090000
* MSVCIRT 780A0000 780B1FFF 00012000
* tsappcmp 77630000 7763EFFF 0000f000
* sqlevn70 41080000 41086FFF 00007000
* NETAPI32 035B0000 035FEFFF 0004f000
* SECUR32 03600000 0360EFFF 0000f000
* NETRAP 03610000 03615FFF 00006000
* SAMLIB 03620000 0362EFFF 0000f000
* WS2_32 03630000 03643FFF 00014000
* WS2HELP 03650000 03657FFF 00008000
* WLDAP32 03660000 03689FFF 0002a000
* DNSAPI 03690000 036B3FFF 00024000
* WSOCK32 036C0000 036C7FFF 00008000
* ole32 03CB0000 03D9BFFF 000ec000
* XOLEHLP 03DA0000 03DA7FFF 00008000
* MSDTCPRX 03DB0000 03E63FFF 000b4000
* MTXCLU 03E70000 03E7FFFF 00010000
* VERSION 03E80000 03E86FFF 00007000
* LZ32 03E90000 03E95FFF 00006000
* CLUSAPI 03EA0000 03EAFFFF 00010000
* RESUTILS 03EB0000 03EBCFFF 0000d000
* USERENV 03EC0000 03F20FFF 00061000
* rnr20 03F30000 03F3BFFF 0000c000
* iphlpapi 03F80000 03F92FFF 00013000
* ICMP 03FA0000 03FA4FFF 00005000
* MPRAPI 03FB0000 03FC6FFF 00017000
* OLEAUT32 03FD0000 0406AFFF 0009b000
* ACTIVEDS 04070000 0409EFFF 0002f000
* ADSLDPC 040A0000 040C2FFF 00023000
* RTUTILS 040D0000 040DDFFF 0000e000
* SETUPAPI 040E0000 0416DFFF 0008e000
* RASAPI32 04170000 041A2FFF 00033000
* RASMAN 041B0000 041C0FFF 00011000
* TAPI32 041D0000 041F1FFF 00022000
* COMCTL32 04200000 04289FFF 0008a000
* SHLWAPI 04290000 042F3FFF 00064000
* DHCPCSVC 04300000 04318FFF 00019000
* winrnr 047C0000 047C7FFF 00008000
* rasadhlp 047D0000 047D4FFF 00005000
* SSNMPN70 00BF0000 00BF5FFF 00006000
* SSNETLIB 00C00000 00C14FFF 00015000
* security 05280000 05283FFF 00004000
* msafd 05290000 052ADFFF 0001e000
* wshtcpip 052F0000 052F6FFF 00007000
* SSmsLPCn 05300000 05306FFF 00007000
* ntdsapi 05780000 05790FFF 00011000
* mswsock 05420000 05431FFF 00012000
* kerberos 057B0000 057E5FFF 00036000
* CRYPTDLL 057F0000 057FDFFF 0000e000
* MSASN1 05800000 0580FFFF 00010000
* rsabase 00C70000 00C92FFF 00023000
* CRYPT32 05320000 053A6FFF 00087000
* SQLFTQRY 05530000 05561FFF 00032000
* CLBCATQ 05DE0000 05E65FFF 00086000
* sqloledb 05E90000 05F02FFF 00073000
* MSDART 05570000 0558EFFF 0001f000
* comdlg32 05F10000 05F4DFFF 0003e000
* SHELL32 05F50000 06197FFF 00248000
* MSDATL3 061A0000 061B4FFF 00015000
* oledb32 06840000 068A5FFF 00066000
* OLEDB32R 05590000 0559FFFF 00010000
* msv1_0 06950000 06970FFF 00021000
* xpsqlbot 06940000 06945FFF 00006000
* xpstar 069C0000 06A06FFF 00047000
* SQLRESLD 06930000 06936FFF 00007000
* SQLSVC 06A10000 06A26FFF 00017000
* ODBC32 06A30000 06A60FFF 00031000
* odbcbcp 06A70000 06A75FFF 00006000
* W95SCM 06A80000 06A8BFFF 0000c000
* SQLUNIRL 06A90000 06ABCFFF 0002d000
* WINSPOOL 06AC0000 06ADDFFF 0001e000
* MPR 06AE0000 06AEFFFF 00010000
* SHFOLDER 06AF0000 06AF7FFF 00008000
* odbcint 06DC0000 06DD5FFF 00016000
* NDDEAPI 06DE0000 06DE6FFF 00007000
* SQLSVC 06DF0000 06DF5FFF 00006000
* xpstar 06E00000 06E08FFF 00009000
* xplog70 00C50000 00C61FFF 00012000
* xplog70 00CA0000 00CA3FFF 00004000
* xp_crs 07230000 07286FFF 00057000
* borlndmm 053F0000 053FAFFF 0000b000
* olepro32 067F0000 06818FFF 00029000
* comsvcs 09300000 0946AFFF 0016b000
* TxfAux 07830000 07893FFF 00064000
* mtxoci 07330000 07352FFF 00023000
* rsaenh 07510000 07532FFF 00023000
* sqlmap70 06780000 067A9FFF 0002a000
* MAPI32 067B0000 067D0FFF 00021000
* MSMAPI32 080D0000 08197FFF 000c8000
* GAPI32 04A60000 04A77FFF 00018000
* EMSABP32 07540000 07563FFF 00024000
* contab32 07190000 071ADFFF 0001e000
* EMSMDB32 09670000 096FEFFF 0008f000
* adsldp 04A20000 04A41FFF 00022000
* adsmsext 06740000 06751FFF 00012000
* dbghelp 08B70000 08C24FFF 000b5000
*
* Edi: 927AB5F0: 927AA018 927ABFF0 00000000 00000000 00000000
00000
000
* Esi: 00000000:
* Eax: 927AB5F0: 927AA018 927ABFF0 00000000 00000000 00000000
00000
000
* Ebx: 927AB4D0: 00380038 000A0004 00000000 00000000 00000002
00000
000
* Ecx: 00000006:
* Edx: 000009E8:
* Eip: 00662572: 758BA5F3 33A5EBF0 A6DBE9C0 75FFFFDF 0C75FF10
0004E
1E8
* Ebp: 06FBA758: 06FBA7AC 005CE635 20642310 2249A030 06FBA82C
927AB
480
* SegCs: 0000001B:
* EFlags: 00010246: 004F0052 00520047 007E0041 005C0031 00450056
00490
052
* Esp: 06FBA724: 2249A030 927AB4D0 927AB480 00380038 000A0004
00000
000
* SegSs: 00000023:
*
************************************************** ***************************
**
*
* Short Stack Dump
* 00662572 Module(sqlservr+00262572) (udf::udf+00000127)
* 005CE635 Module(sqlservr+001CE635) (CSteUdf::CSteUdf+00000077)
* 0075A864 Module(sqlservr+0035A864) (CScaOp_Udf::PqteConvert+000000BF)
The query at the top of te dump file is always the same or at least the bit
that is not truncated is. The bizarre thing is that if you run the query by
hand it runs just fine.
Does anyone have any suggestions or thoughts.
Thanks in advance for any advice offered
Jamie.
How I hate those errors ;)
Normally its to do with one of the SQL Server resources failing, or at least
SQL Server thinking its failed.
When it happened to us I set the Affinity Mask to 0 and after that it worked.
Good Luck
Peter
"jimmy" wrote:

> I have two different Production Servers which are creating SQLDump00*** files.
> I suspect the issue is to do with Paralellism. As on one of the servers I
> set the MAXDOP to 1 and it has cured the problem.
> Someone in my office seems to think the issue has something to do with
> language_exec as it appears in all the logs. Can someone please tell me what
> this term means.
> The error in event view is:
> SqlDumpExceptionHandler: Process 81 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> The Dump file generates:
> ================================================== ===================
> 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.
> Current time is 08:40:42 04/28/05.
> 8 Intel x86 level 15, 1999 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 4.
>
> Memory
> MemoryLoad = 78%
> Total Physical = 3775 MB
> Available Physical = 794 MB
> Total Page File = 5669 MB
> Available Page File = 2663 MB
> Total Virtual = 3071 MB
> Available Virtual = 265 MB
> *Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL\log\SQLDu
> mp0041.txt
> *
> ************************************************** ***************************
> **
> *
> * BEGIN STACK DUMP:
> * 04/28/05 08:40:42 spid 70
> *
> * Exception Address = 00662572 (udf::udf + 00000127 Line 0+00000000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address 00000000
> * Input Buffer 4088 bytes -
> * SELECT repExposureCust."HostName", repExposureCust."PortfolioClassSort",
> * repExposureCust."PortfolioClass", repExposureCust."CustID", repExposure
> * Cust."PfolCustCode", repExposureCust."PfolCustName", repExposureCust."Pf
> * olProdName", repExposureCust."PfolBranName", repExposureCust."PfolCptyCo
> * de", repExposureCust."PfolPGRatCode", repExposureCust."ItemClassID", rep
> * ExposureCust."PfolItemClass", repExposureCust."PortfolioID", repExposure
> * Cust."MeasureID", repExposureCust."DataMonth", repExposureCust."DaysInEx
> * cess", repExposureCust."LimMax01", repExposureCust."LimMin01", repExposu
> * reCust."ExpMax01", repExposureCust."ExpMin01", repExposureCust."ExpAvg01
> * ", repExposureCust."LimMax02", repExposureCust."LimMin02", repExposureCu
> * st."ExpMax02", repExposureCust."ExpMin02", repExposureCust."ExpAvg02", r
> * epExposureCust."LimMax03", repExposureCust."LimMin03", repExposureCust."
> * ExpMax03", repExposureCust."ExpMin03", repExposureCust."ExpAvg03", repEx
> * posureCust."LimMax04", repExposureCust."LimMin04", repExposureCust."ExpM
> * ax04", repExposureCust."ExpMin04", repExposureCust."ExpAvg04", repExposu
> * reCust."LimMax05", repExposureCust."LimMin05", repExposureCust."ExpMax05
> * ", repExposureCust."ExpMin05", repExposureCust."ExpAvg05", repExposureCu
> * st."LimMax06", repExposureCust."LimMin06", repExposureCust."ExpMax06", r
> * epExposureCust."ExpMin06", repExposureCust."ExpAvg06", repExposureCust."
> * LimMax07", repExposureCust."LimMin07", repExposureCust."ExpMax07", repEx
> * posureCust."ExpMin07", repExposureCust."ExpAvg07", repExposureCust."LimM
> * ax08", repExposureCust."LimMin08", repExposureCust."ExpMax08", repExposu
> * reCust."ExpMin08", repExposureCust."ExpAvg08", repExposureCust."LimMax09
> * ", repExposureCust."LimMin09", repExposureCust."ExpMax09", repExposureCu
> * st."ExpMin09", repExposureCust."ExpAvg09", repExposureCust."LimMax10", r
> * epExposureCust."LimMin10", repExposureCust."ExpMax10", repExposureCust."
> * ExpMin10", repExposureCust."ExpAvg10", repExposureCust."Measure", repExp
> * osureCust."LimitAttribute", repExposureCust."LimCurrSpot", repExposureCu
> * st."ChecksClassSymbol", repE
> *
> *
> * MODULE BASE END SIZE
> * sqlservr 00400000 00B2CFFF 0072d000
> * ntdll 77F80000 77FFCFFF 0007d000
> * KERNEL32 7C570000 7C627FFF 000b8000
> * ADVAPI32 7C2D0000 7C331FFF 00062000
> * RPCRT4 77D30000 77D9DFFF 0006e000
> * USER32 77E10000 77E74FFF 00065000
> * GDI32 77F40000 77F7DFFF 0003e000
> * OPENDS60 41060000 41065FFF 00006000
> * MSVCRT 78000000 78044FFF 00045000
> * UMS 41070000 4107CFFF 0000d000
> * SQLSORT 42AE0000 42B6FFFF 00090000
> * MSVCIRT 780A0000 780B1FFF 00012000
> * tsappcmp 77630000 7763EFFF 0000f000
> * sqlevn70 41080000 41086FFF 00007000
> * NETAPI32 035B0000 035FEFFF 0004f000
> * SECUR32 03600000 0360EFFF 0000f000
> * NETRAP 03610000 03615FFF 00006000
> * SAMLIB 03620000 0362EFFF 0000f000
> * WS2_32 03630000 03643FFF 00014000
> * WS2HELP 03650000 03657FFF 00008000
> * WLDAP32 03660000 03689FFF 0002a000
> * DNSAPI 03690000 036B3FFF 00024000
> * WSOCK32 036C0000 036C7FFF 00008000
> * ole32 03CB0000 03D9BFFF 000ec000
> * XOLEHLP 03DA0000 03DA7FFF 00008000
> * MSDTCPRX 03DB0000 03E63FFF 000b4000
> * MTXCLU 03E70000 03E7FFFF 00010000
> * VERSION 03E80000 03E86FFF 00007000
> * LZ32 03E90000 03E95FFF 00006000
> * CLUSAPI 03EA0000 03EAFFFF 00010000
> * RESUTILS 03EB0000 03EBCFFF 0000d000
> * USERENV 03EC0000 03F20FFF 00061000
> * rnr20 03F30000 03F3BFFF 0000c000
> * iphlpapi 03F80000 03F92FFF 00013000
> * ICMP 03FA0000 03FA4FFF 00005000
> * MPRAPI 03FB0000 03FC6FFF 00017000
> * OLEAUT32 03FD0000 0406AFFF 0009b000
> * ACTIVEDS 04070000 0409EFFF 0002f000
> * ADSLDPC 040A0000 040C2FFF 00023000
> * RTUTILS 040D0000 040DDFFF 0000e000
> * SETUPAPI 040E0000 0416DFFF 0008e000
> * RASAPI32 04170000 041A2FFF 00033000
> * RASMAN 041B0000 041C0FFF 00011000
> * TAPI32 041D0000 041F1FFF 00022000
> * COMCTL32 04200000 04289FFF 0008a000
> * SHLWAPI 04290000 042F3FFF 00064000
> * DHCPCSVC 04300000 04318FFF 00019000
> * winrnr 047C0000 047C7FFF 00008000
> * rasadhlp 047D0000 047D4FFF 00005000
> * SSNMPN70 00BF0000 00BF5FFF 00006000
> * SSNETLIB 00C00000 00C14FFF 00015000
> * security 05280000 05283FFF 00004000
> * msafd 05290000 052ADFFF 0001e000
> * wshtcpip 052F0000 052F6FFF 00007000
> * SSmsLPCn 05300000 05306FFF 00007000
> * ntdsapi 05780000 05790FFF 00011000
> * mswsock 05420000 05431FFF 00012000
> * kerberos 057B0000 057E5FFF 00036000
> * CRYPTDLL 057F0000 057FDFFF 0000e000
> * MSASN1 05800000 0580FFFF 00010000
> * rsabase 00C70000 00C92FFF 00023000
> * CRYPT32 05320000 053A6FFF 00087000
> * SQLFTQRY 05530000 05561FFF 00032000
> * CLBCATQ 05DE0000 05E65FFF 00086000
> * sqloledb 05E90000 05F02FFF 00073000
> * MSDART 05570000 0558EFFF 0001f000
> * comdlg32 05F10000 05F4DFFF 0003e000
> * SHELL32 05F50000 06197FFF 00248000
> * MSDATL3 061A0000 061B4FFF 00015000
> * oledb32 06840000 068A5FFF 00066000
> * OLEDB32R 05590000 0559FFFF 00010000
> * msv1_0 06950000 06970FFF 00021000
> * xpsqlbot 06940000 06945FFF 00006000
> * xpstar 069C0000 06A06FFF 00047000
> * SQLRESLD 06930000 06936FFF 00007000
> * SQLSVC 06A10000 06A26FFF 00017000
> * ODBC32 06A30000 06A60FFF 00031000
> * odbcbcp 06A70000 06A75FFF 00006000
> * W95SCM 06A80000 06A8BFFF 0000c000
> * SQLUNIRL 06A90000 06ABCFFF 0002d000

Wednesday, March 7, 2012

EXCEPTION_ACCESS_VIOLATION

I have two different Production Servers which are creating SQLDump00*** files.
I suspect the issue is to do with Paralellism. As on one of the servers I
set the MAXDOP to 1 and it has cured the problem.
Someone in my office seems to think the issue has something to do with
language_exec as it appears in all the logs. Can someone please tell me what
this term means.
The error in event view is:
SqlDumpExceptionHandler: Process 81 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
The Dump file generates:
=====================================================================
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.
Current time is 08:40:42 04/28/05.
8 Intel x86 level 15, 1999 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory
MemoryLoad = 78%
Total Physical = 3775 MB
Available Physical = 794 MB
Total Page File = 5669 MB
Available Page File = 2663 MB
Total Virtual = 3071 MB
Available Virtual = 265 MB
*Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL\log\SQLDu
mp0041.txt
*
*****************************************************************************
**
*
* BEGIN STACK DUMP:
* 04/28/05 08:40:42 spid 70
*
* Exception Address = 00662572 (udf::udf + 00000127 Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000000
* Input Buffer 4088 bytes -
* SELECT repExposureCust."HostName", repExposureCust."PortfolioClassSort",
* repExposureCust."PortfolioClass", repExposureCust."CustID", repExposure
* Cust."PfolCustCode", repExposureCust."PfolCustName", repExposureCust."Pf
* olProdName", repExposureCust."PfolBranName", repExposureCust."PfolCptyCo
* de", repExposureCust."PfolPGRatCode", repExposureCust."ItemClassID", rep
* ExposureCust."PfolItemClass", repExposureCust."PortfolioID", repExposure
* Cust."MeasureID", repExposureCust."DataMonth", repExposureCust."DaysInEx
* cess", repExposureCust."LimMax01", repExposureCust."LimMin01", repExposu
* reCust."ExpMax01", repExposureCust."ExpMin01", repExposureCust."ExpAvg01
* ", repExposureCust."LimMax02", repExposureCust."LimMin02", repExposureCu
* st."ExpMax02", repExposureCust."ExpMin02", repExposureCust."ExpAvg02", r
* epExposureCust."LimMax03", repExposureCust."LimMin03", repExposureCust."
* ExpMax03", repExposureCust."ExpMin03", repExposureCust."ExpAvg03", repEx
* posureCust."LimMax04", repExposureCust."LimMin04", repExposureCust."ExpM
* ax04", repExposureCust."ExpMin04", repExposureCust."ExpAvg04", repExposu
* reCust."LimMax05", repExposureCust."LimMin05", repExposureCust."ExpMax05
* ", repExposureCust."ExpMin05", repExposureCust."ExpAvg05", repExposureCu
* st."LimMax06", repExposureCust."LimMin06", repExposureCust."ExpMax06", r
* epExposureCust."ExpMin06", repExposureCust."ExpAvg06", repExposureCust."
* LimMax07", repExposureCust."LimMin07", repExposureCust."ExpMax07", repEx
* posureCust."ExpMin07", repExposureCust."ExpAvg07", repExposureCust."LimM
* ax08", repExposureCust."LimMin08", repExposureCust."ExpMax08", repExposu
* reCust."ExpMin08", repExposureCust."ExpAvg08", repExposureCust."LimMax09
* ", repExposureCust."LimMin09", repExposureCust."ExpMax09", repExposureCu
* st."ExpMin09", repExposureCust."ExpAvg09", repExposureCust."LimMax10", r
* epExposureCust."LimMin10", repExposureCust."ExpMax10", repExposureCust."
* ExpMin10", repExposureCust."ExpAvg10", repExposureCust."Measure", repExp
* osureCust."LimitAttribute", repExposureCust."LimCurrSpot", repExposureCu
* st."ChecksClassSymbol", repE
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00B2CFFF 0072d000
* ntdll 77F80000 77FFCFFF 0007d000
* KERNEL32 7C570000 7C627FFF 000b8000
* ADVAPI32 7C2D0000 7C331FFF 00062000
* RPCRT4 77D30000 77D9DFFF 0006e000
* USER32 77E10000 77E74FFF 00065000
* GDI32 77F40000 77F7DFFF 0003e000
* OPENDS60 41060000 41065FFF 00006000
* MSVCRT 78000000 78044FFF 00045000
* UMS 41070000 4107CFFF 0000d000
* SQLSORT 42AE0000 42B6FFFF 00090000
* MSVCIRT 780A0000 780B1FFF 00012000
* tsappcmp 77630000 7763EFFF 0000f000
* sqlevn70 41080000 41086FFF 00007000
* NETAPI32 035B0000 035FEFFF 0004f000
* SECUR32 03600000 0360EFFF 0000f000
* NETRAP 03610000 03615FFF 00006000
* SAMLIB 03620000 0362EFFF 0000f000
* WS2_32 03630000 03643FFF 00014000
* WS2HELP 03650000 03657FFF 00008000
* WLDAP32 03660000 03689FFF 0002a000
* DNSAPI 03690000 036B3FFF 00024000
* WSOCK32 036C0000 036C7FFF 00008000
* ole32 03CB0000 03D9BFFF 000ec000
* XOLEHLP 03DA0000 03DA7FFF 00008000
* MSDTCPRX 03DB0000 03E63FFF 000b4000
* MTXCLU 03E70000 03E7FFFF 00010000
* VERSION 03E80000 03E86FFF 00007000
* LZ32 03E90000 03E95FFF 00006000
* CLUSAPI 03EA0000 03EAFFFF 00010000
* RESUTILS 03EB0000 03EBCFFF 0000d000
* USERENV 03EC0000 03F20FFF 00061000
* rnr20 03F30000 03F3BFFF 0000c000
* iphlpapi 03F80000 03F92FFF 00013000
* ICMP 03FA0000 03FA4FFF 00005000
* MPRAPI 03FB0000 03FC6FFF 00017000
* OLEAUT32 03FD0000 0406AFFF 0009b000
* ACTIVEDS 04070000 0409EFFF 0002f000
* ADSLDPC 040A0000 040C2FFF 00023000
* RTUTILS 040D0000 040DDFFF 0000e000
* SETUPAPI 040E0000 0416DFFF 0008e000
* RASAPI32 04170000 041A2FFF 00033000
* RASMAN 041B0000 041C0FFF 00011000
* TAPI32 041D0000 041F1FFF 00022000
* COMCTL32 04200000 04289FFF 0008a000
* SHLWAPI 04290000 042F3FFF 00064000
* DHCPCSVC 04300000 04318FFF 00019000
* winrnr 047C0000 047C7FFF 00008000
* rasadhlp 047D0000 047D4FFF 00005000
* SSNMPN70 00BF0000 00BF5FFF 00006000
* SSNETLIB 00C00000 00C14FFF 00015000
* security 05280000 05283FFF 00004000
* msafd 05290000 052ADFFF 0001e000
* wshtcpip 052F0000 052F6FFF 00007000
* SSmsLPCn 05300000 05306FFF 00007000
* ntdsapi 05780000 05790FFF 00011000
* mswsock 05420000 05431FFF 00012000
* kerberos 057B0000 057E5FFF 00036000
* CRYPTDLL 057F0000 057FDFFF 0000e000
* MSASN1 05800000 0580FFFF 00010000
* rsabase 00C70000 00C92FFF 00023000
* CRYPT32 05320000 053A6FFF 00087000
* SQLFTQRY 05530000 05561FFF 00032000
* CLBCATQ 05DE0000 05E65FFF 00086000
* sqloledb 05E90000 05F02FFF 00073000
* MSDART 05570000 0558EFFF 0001f000
* comdlg32 05F10000 05F4DFFF 0003e000
* SHELL32 05F50000 06197FFF 00248000
* MSDATL3 061A0000 061B4FFF 00015000
* oledb32 06840000 068A5FFF 00066000
* OLEDB32R 05590000 0559FFFF 00010000
* msv1_0 06950000 06970FFF 00021000
* xpsqlbot 06940000 06945FFF 00006000
* xpstar 069C0000 06A06FFF 00047000
* SQLRESLD 06930000 06936FFF 00007000
* SQLSVC 06A10000 06A26FFF 00017000
* ODBC32 06A30000 06A60FFF 00031000
* odbcbcp 06A70000 06A75FFF 00006000
* W95SCM 06A80000 06A8BFFF 0000c000
* SQLUNIRL 06A90000 06ABCFFF 0002d000
* WINSPOOL 06AC0000 06ADDFFF 0001e000
* MPR 06AE0000 06AEFFFF 00010000
* SHFOLDER 06AF0000 06AF7FFF 00008000
* odbcint 06DC0000 06DD5FFF 00016000
* NDDEAPI 06DE0000 06DE6FFF 00007000
* SQLSVC 06DF0000 06DF5FFF 00006000
* xpstar 06E00000 06E08FFF 00009000
* xplog70 00C50000 00C61FFF 00012000
* xplog70 00CA0000 00CA3FFF 00004000
* xp_crs 07230000 07286FFF 00057000
* borlndmm 053F0000 053FAFFF 0000b000
* olepro32 067F0000 06818FFF 00029000
* comsvcs 09300000 0946AFFF 0016b000
* TxfAux 07830000 07893FFF 00064000
* mtxoci 07330000 07352FFF 00023000
* rsaenh 07510000 07532FFF 00023000
* sqlmap70 06780000 067A9FFF 0002a000
* MAPI32 067B0000 067D0FFF 00021000
* MSMAPI32 080D0000 08197FFF 000c8000
* GAPI32 04A60000 04A77FFF 00018000
* EMSABP32 07540000 07563FFF 00024000
* contab32 07190000 071ADFFF 0001e000
* EMSMDB32 09670000 096FEFFF 0008f000
* adsldp 04A20000 04A41FFF 00022000
* adsmsext 06740000 06751FFF 00012000
* dbghelp 08B70000 08C24FFF 000b5000
*
* Edi: 927AB5F0: 927AA018 927ABFF0 00000000 00000000 00000000
00000
000
* Esi: 00000000:
* Eax: 927AB5F0: 927AA018 927ABFF0 00000000 00000000 00000000
00000
000
* Ebx: 927AB4D0: 00380038 000A0004 00000000 00000000 00000002
00000
000
* Ecx: 00000006:
* Edx: 000009E8:
* Eip: 00662572: 758BA5F3 33A5EBF0 A6DBE9C0 75FFFFDF 0C75FF10
0004E
1E8
* Ebp: 06FBA758: 06FBA7AC 005CE635 20642310 2249A030 06FBA82C
927AB
480
* SegCs: 0000001B:
* EFlags: 00010246: 004F0052 00520047 007E0041 005C0031 00450056
00490
052
* Esp: 06FBA724: 2249A030 927AB4D0 927AB480 00380038 000A0004
00000
000
* SegSs: 00000023:
*
*****************************************************************************
**
*
----
--
* Short Stack Dump
* 00662572 Module(sqlservr+00262572) (udf::udf+00000127)
* 005CE635 Module(sqlservr+001CE635) (CSteUdf::CSteUdf+00000077)
* 0075A864 Module(sqlservr+0035A864) (CScaOp_Udf::PqteConvert+000000BF)
The query at the top of te dump file is always the same or at least the bit
that is not truncated is. The bizarre thing is that if you run the query by
hand it runs just fine.
Does anyone have any suggestions or thoughts.
Thanks in advance for any advice offered
Jamie.How I hate those errors ;)
Normally its to do with one of the SQL Server resources failing, or at least
SQL Server thinking its failed.
When it happened to us I set the Affinity Mask to 0 and after that it worked.
Good Luck
Peter
"jimmy" wrote:
> I have two different Production Servers which are creating SQLDump00*** files.
> I suspect the issue is to do with Paralellism. As on one of the servers I
> set the MAXDOP to 1 and it has cured the problem.
> Someone in my office seems to think the issue has something to do with
> language_exec as it appears in all the logs. Can someone please tell me what
> this term means.
> The error in event view is:
> SqlDumpExceptionHandler: Process 81 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> The Dump file generates:
> =====================================================================> 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.
> Current time is 08:40:42 04/28/05.
> 8 Intel x86 level 15, 1999 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 4.
>
> Memory
> MemoryLoad = 78%
> Total Physical = 3775 MB
> Available Physical = 794 MB
> Total Page File = 5669 MB
> Available Page File = 2663 MB
> Total Virtual = 3071 MB
> Available Virtual = 265 MB
> *Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL\log\SQLDu
> mp0041.txt
> *
> *****************************************************************************
> **
> *
> * BEGIN STACK DUMP:
> * 04/28/05 08:40:42 spid 70
> *
> * Exception Address = 00662572 (udf::udf + 00000127 Line 0+00000000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address 00000000
> * Input Buffer 4088 bytes -
> * SELECT repExposureCust."HostName", repExposureCust."PortfolioClassSort",
> * repExposureCust."PortfolioClass", repExposureCust."CustID", repExposure
> * Cust."PfolCustCode", repExposureCust."PfolCustName", repExposureCust."Pf
> * olProdName", repExposureCust."PfolBranName", repExposureCust."PfolCptyCo
> * de", repExposureCust."PfolPGRatCode", repExposureCust."ItemClassID", rep
> * ExposureCust."PfolItemClass", repExposureCust."PortfolioID", repExposure
> * Cust."MeasureID", repExposureCust."DataMonth", repExposureCust."DaysInEx
> * cess", repExposureCust."LimMax01", repExposureCust."LimMin01", repExposu
> * reCust."ExpMax01", repExposureCust."ExpMin01", repExposureCust."ExpAvg01
> * ", repExposureCust."LimMax02", repExposureCust."LimMin02", repExposureCu
> * st."ExpMax02", repExposureCust."ExpMin02", repExposureCust."ExpAvg02", r
> * epExposureCust."LimMax03", repExposureCust."LimMin03", repExposureCust."
> * ExpMax03", repExposureCust."ExpMin03", repExposureCust."ExpAvg03", repEx
> * posureCust."LimMax04", repExposureCust."LimMin04", repExposureCust."ExpM
> * ax04", repExposureCust."ExpMin04", repExposureCust."ExpAvg04", repExposu
> * reCust."LimMax05", repExposureCust."LimMin05", repExposureCust."ExpMax05
> * ", repExposureCust."ExpMin05", repExposureCust."ExpAvg05", repExposureCu
> * st."LimMax06", repExposureCust."LimMin06", repExposureCust."ExpMax06", r
> * epExposureCust."ExpMin06", repExposureCust."ExpAvg06", repExposureCust."
> * LimMax07", repExposureCust."LimMin07", repExposureCust."ExpMax07", repEx
> * posureCust."ExpMin07", repExposureCust."ExpAvg07", repExposureCust."LimM
> * ax08", repExposureCust."LimMin08", repExposureCust."ExpMax08", repExposu
> * reCust."ExpMin08", repExposureCust."ExpAvg08", repExposureCust."LimMax09
> * ", repExposureCust."LimMin09", repExposureCust."ExpMax09", repExposureCu
> * st."ExpMin09", repExposureCust."ExpAvg09", repExposureCust."LimMax10", r
> * epExposureCust."LimMin10", repExposureCust."ExpMax10", repExposureCust."
> * ExpMin10", repExposureCust."ExpAvg10", repExposureCust."Measure", repExp
> * osureCust."LimitAttribute", repExposureCust."LimCurrSpot", repExposureCu
> * st."ChecksClassSymbol", repE
> *
> *
> * MODULE BASE END SIZE
> * sqlservr 00400000 00B2CFFF 0072d000
> * ntdll 77F80000 77FFCFFF 0007d000
> * KERNEL32 7C570000 7C627FFF 000b8000
> * ADVAPI32 7C2D0000 7C331FFF 00062000
> * RPCRT4 77D30000 77D9DFFF 0006e000
> * USER32 77E10000 77E74FFF 00065000
> * GDI32 77F40000 77F7DFFF 0003e000
> * OPENDS60 41060000 41065FFF 00006000
> * MSVCRT 78000000 78044FFF 00045000
> * UMS 41070000 4107CFFF 0000d000
> * SQLSORT 42AE0000 42B6FFFF 00090000
> * MSVCIRT 780A0000 780B1FFF 00012000
> * tsappcmp 77630000 7763EFFF 0000f000
> * sqlevn70 41080000 41086FFF 00007000
> * NETAPI32 035B0000 035FEFFF 0004f000
> * SECUR32 03600000 0360EFFF 0000f000
> * NETRAP 03610000 03615FFF 00006000
> * SAMLIB 03620000 0362EFFF 0000f000
> * WS2_32 03630000 03643FFF 00014000
> * WS2HELP 03650000 03657FFF 00008000
> * WLDAP32 03660000 03689FFF 0002a000
> * DNSAPI 03690000 036B3FFF 00024000
> * WSOCK32 036C0000 036C7FFF 00008000
> * ole32 03CB0000 03D9BFFF 000ec000
> * XOLEHLP 03DA0000 03DA7FFF 00008000
> * MSDTCPRX 03DB0000 03E63FFF 000b4000
> * MTXCLU 03E70000 03E7FFFF 00010000
> * VERSION 03E80000 03E86FFF 00007000
> * LZ32 03E90000 03E95FFF 00006000
> * CLUSAPI 03EA0000 03EAFFFF 00010000
> * RESUTILS 03EB0000 03EBCFFF 0000d000
> * USERENV 03EC0000 03F20FFF 00061000
> * rnr20 03F30000 03F3BFFF 0000c000
> * iphlpapi 03F80000 03F92FFF 00013000
> * ICMP 03FA0000 03FA4FFF 00005000
> * MPRAPI 03FB0000 03FC6FFF 00017000
> * OLEAUT32 03FD0000 0406AFFF 0009b000
> * ACTIVEDS 04070000 0409EFFF 0002f000
> * ADSLDPC 040A0000 040C2FFF 00023000
> * RTUTILS 040D0000 040DDFFF 0000e000
> * SETUPAPI 040E0000 0416DFFF 0008e000
> * RASAPI32 04170000 041A2FFF 00033000
> * RASMAN 041B0000 041C0FFF 00011000
> * TAPI32 041D0000 041F1FFF 00022000
> * COMCTL32 04200000 04289FFF 0008a000
> * SHLWAPI 04290000 042F3FFF 00064000
> * DHCPCSVC 04300000 04318FFF 00019000
> * winrnr 047C0000 047C7FFF 00008000
> * rasadhlp 047D0000 047D4FFF 00005000
> * SSNMPN70 00BF0000 00BF5FFF 00006000
> * SSNETLIB 00C00000 00C14FFF 00015000
> * security 05280000 05283FFF 00004000
> * msafd 05290000 052ADFFF 0001e000
> * wshtcpip 052F0000 052F6FFF 00007000
> * SSmsLPCn 05300000 05306FFF 00007000
> * ntdsapi 05780000 05790FFF 00011000
> * mswsock 05420000 05431FFF 00012000
> * kerberos 057B0000 057E5FFF 00036000
> * CRYPTDLL 057F0000 057FDFFF 0000e000
> * MSASN1 05800000 0580FFFF 00010000
> * rsabase 00C70000 00C92FFF 00023000
> * CRYPT32 05320000 053A6FFF 00087000
> * SQLFTQRY 05530000 05561FFF 00032000
> * CLBCATQ 05DE0000 05E65FFF 00086000
> * sqloledb 05E90000 05F02FFF 00073000
> * MSDART 05570000 0558EFFF 0001f000
> * comdlg32 05F10000 05F4DFFF 0003e000
> * SHELL32 05F50000 06197FFF 00248000
> * MSDATL3 061A0000 061B4FFF 00015000
> * oledb32 06840000 068A5FFF 00066000
> * OLEDB32R 05590000 0559FFFF 00010000
> * msv1_0 06950000 06970FFF 00021000
> * xpsqlbot 06940000 06945FFF 00006000
> * xpstar 069C0000 06A06FFF 00047000
> * SQLRESLD 06930000 06936FFF 00007000
> * SQLSVC 06A10000 06A26FFF 00017000
> * ODBC32 06A30000 06A60FFF 00031000
> * odbcbcp 06A70000 06A75FFF 00006000
> * W95SCM 06A80000 06A8BFFF 0000c000
> * SQLUNIRL 06A90000 06ABCFFF 0002d000

EXCEPTION_ACCESS_VIOLATION

I have two different Production Servers which are creating SQLDump00*** file
s.
I suspect the issue is to do with Paralellism. As on one of the servers I
set the MAXDOP to 1 and it has cured the problem.
Someone in my office seems to think the issue has something to do with
language_exec as it appears in all the logs. Can someone please tell me wha
t
this term means.
The error in event view is:
SqlDumpExceptionHandler: Process 81 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
The Dump file generates:
========================================
=============================
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.
Current time is 08:40:42 04/28/05.
8 Intel x86 level 15, 1999 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory
MemoryLoad = 78%
Total Physical = 3775 MB
Available Physical = 794 MB
Total Page File = 5669 MB
Available Page File = 2663 MB
Total Virtual = 3071 MB
Available Virtual = 265 MB
*Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL\log\SQLDu
mp0041.txt
*
****************************************
************************************
*
**
*
* BEGIN STACK DUMP:
* 04/28/05 08:40:42 spid 70
*
* Exception Address = 00662572 (udf::udf + 00000127 Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000000
* Input Buffer 4088 bytes -
* SELECT repExposureCust."HostName", repExposureCust."PortfolioClassSort",
* repExposureCust."PortfolioClass", repExposureCust."CustID", repExposure
* Cust."PfolCustCode", repExposureCust."PfolCustName", repExposureCust."Pf
* olProdName", repExposureCust."PfolBranName", repExposureCust."PfolCptyCo
* de", repExposureCust."PfolPGRatCode", repExposureCust."ItemClassID", rep
* ExposureCust."PfolItemClass", repExposureCust."PortfolioID", repExposure
* Cust."MeasureID", repExposureCust."DataMonth", repExposureCust."DaysInEx
* cess", repExposureCust."LimMax01", repExposureCust."LimMin01", repExposu
* reCust."ExpMax01", repExposureCust."ExpMin01", repExposureCust."ExpAvg01
* ", repExposureCust."LimMax02", repExposureCust."LimMin02", repExposureCu
* st."ExpMax02", repExposureCust."ExpMin02", repExposureCust."ExpAvg02", r
* epExposureCust."LimMax03", repExposureCust."LimMin03", repExposureCust."
* ExpMax03", repExposureCust."ExpMin03", repExposureCust."ExpAvg03", repEx
* posureCust."LimMax04", repExposureCust."LimMin04", repExposureCust."ExpM
* ax04", repExposureCust."ExpMin04", repExposureCust."ExpAvg04", repExposu
* reCust."LimMax05", repExposureCust."LimMin05", repExposureCust."ExpMax05
* ", repExposureCust."ExpMin05", repExposureCust."ExpAvg05", repExposureCu
* st."LimMax06", repExposureCust."LimMin06", repExposureCust."ExpMax06", r
* epExposureCust."ExpMin06", repExposureCust."ExpAvg06", repExposureCust."
* LimMax07", repExposureCust."LimMin07", repExposureCust."ExpMax07", repEx
* posureCust."ExpMin07", repExposureCust."ExpAvg07", repExposureCust."LimM
* ax08", repExposureCust."LimMin08", repExposureCust."ExpMax08", repExposu
* reCust."ExpMin08", repExposureCust."ExpAvg08", repExposureCust."LimMax09
* ", repExposureCust."LimMin09", repExposureCust."ExpMax09", repExposureCu
* st."ExpMin09", repExposureCust."ExpAvg09", repExposureCust."LimMax10", r
* epExposureCust."LimMin10", repExposureCust."ExpMax10", repExposureCust."
* ExpMin10", repExposureCust."ExpAvg10", repExposureCust."Measure", repExp
* osureCust."LimitAttribute", repExposureCust."LimCurrSpot", repExposureCu
* st."ChecksClassSymbol", repE
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00B2CFFF 0072d000
* ntdll 77F80000 77FFCFFF 0007d000
* KERNEL32 7C570000 7C627FFF 000b8000
* ADVAPI32 7C2D0000 7C331FFF 00062000
* RPCRT4 77D30000 77D9DFFF 0006e000
* USER32 77E10000 77E74FFF 00065000
* GDI32 77F40000 77F7DFFF 0003e000
* OPENDS60 41060000 41065FFF 00006000
* MSVCRT 78000000 78044FFF 00045000
* UMS 41070000 4107CFFF 0000d000
* SQLSORT 42AE0000 42B6FFFF 00090000
* MSVCIRT 780A0000 780B1FFF 00012000
* tsappcmp 77630000 7763EFFF 0000f000
* sqlevn70 41080000 41086FFF 00007000
* NETAPI32 035B0000 035FEFFF 0004f000
* SECUR32 03600000 0360EFFF 0000f000
* NETRAP 03610000 03615FFF 00006000
* SAMLIB 03620000 0362EFFF 0000f000
* WS2_32 03630000 03643FFF 00014000
* WS2HELP 03650000 03657FFF 00008000
* WLDAP32 03660000 03689FFF 0002a000
* DNSAPI 03690000 036B3FFF 00024000
* WSOCK32 036C0000 036C7FFF 00008000
* ole32 03CB0000 03D9BFFF 000ec000
* XOLEHLP 03DA0000 03DA7FFF 00008000
* MSDTCPRX 03DB0000 03E63FFF 000b4000
* MTXCLU 03E70000 03E7FFFF 00010000
* VERSION 03E80000 03E86FFF 00007000
* LZ32 03E90000 03E95FFF 00006000
* CLUSAPI 03EA0000 03EAFFFF 00010000
* RESUTILS 03EB0000 03EBCFFF 0000d000
* USERENV 03EC0000 03F20FFF 00061000
* rnr20 03F30000 03F3BFFF 0000c000
* iphlpapi 03F80000 03F92FFF 00013000
* ICMP 03FA0000 03FA4FFF 00005000
* MPRAPI 03FB0000 03FC6FFF 00017000
* OLEAUT32 03FD0000 0406AFFF 0009b000
* ACTIVEDS 04070000 0409EFFF 0002f000
* ADSLDPC 040A0000 040C2FFF 00023000
* RTUTILS 040D0000 040DDFFF 0000e000
* SETUPAPI 040E0000 0416DFFF 0008e000
* RASAPI32 04170000 041A2FFF 00033000
* RASMAN 041B0000 041C0FFF 00011000
* TAPI32 041D0000 041F1FFF 00022000
* COMCTL32 04200000 04289FFF 0008a000
* SHLWAPI 04290000 042F3FFF 00064000
* DHCPCSVC 04300000 04318FFF 00019000
* winrnr 047C0000 047C7FFF 00008000
* rasadhlp 047D0000 047D4FFF 00005000
* SSNMPN70 00BF0000 00BF5FFF 00006000
* SSNETLIB 00C00000 00C14FFF 00015000
* security 05280000 05283FFF 00004000
* msafd 05290000 052ADFFF 0001e000
* wshtcpip 052F0000 052F6FFF 00007000
* SSmsLPCn 05300000 05306FFF 00007000
* ntdsapi 05780000 05790FFF 00011000
* mswsock 05420000 05431FFF 00012000
* kerberos 057B0000 057E5FFF 00036000
* CRYPTDLL 057F0000 057FDFFF 0000e000
* MSASN1 05800000 0580FFFF 00010000
* rsabase 00C70000 00C92FFF 00023000
* CRYPT32 05320000 053A6FFF 00087000
* SQLFTQRY 05530000 05561FFF 00032000
* CLBCATQ 05DE0000 05E65FFF 00086000
* sqloledb 05E90000 05F02FFF 00073000
* MSDART 05570000 0558EFFF 0001f000
* comdlg32 05F10000 05F4DFFF 0003e000
* SHELL32 05F50000 06197FFF 00248000
* MSDATL3 061A0000 061B4FFF 00015000
* oledb32 06840000 068A5FFF 00066000
* OLEDB32R 05590000 0559FFFF 00010000
* msv1_0 06950000 06970FFF 00021000
* xpsqlbot 06940000 06945FFF 00006000
* xpstar 069C0000 06A06FFF 00047000
* SQLRESLD 06930000 06936FFF 00007000
* SQLSVC 06A10000 06A26FFF 00017000
* ODBC32 06A30000 06A60FFF 00031000
* odbcbcp 06A70000 06A75FFF 00006000
* W95SCM 06A80000 06A8BFFF 0000c000
* SQLUNIRL 06A90000 06ABCFFF 0002d000
* WINSPOOL 06AC0000 06ADDFFF 0001e000
* MPR 06AE0000 06AEFFFF 00010000
* SHFOLDER 06AF0000 06AF7FFF 00008000
* odbcint 06DC0000 06DD5FFF 00016000
* NDDEAPI 06DE0000 06DE6FFF 00007000
* SQLSVC 06DF0000 06DF5FFF 00006000
* xpstar 06E00000 06E08FFF 00009000
* xplog70 00C50000 00C61FFF 00012000
* xplog70 00CA0000 00CA3FFF 00004000
* xp_crs 07230000 07286FFF 00057000
* borlndmm 053F0000 053FAFFF 0000b000
* olepro32 067F0000 06818FFF 00029000
* comsvcs 09300000 0946AFFF 0016b000
* TxfAux 07830000 07893FFF 00064000
* mtxoci 07330000 07352FFF 00023000
* rsaenh 07510000 07532FFF 00023000
* sqlmap70 06780000 067A9FFF 0002a000
* MAPI32 067B0000 067D0FFF 00021000
* MSMAPI32 080D0000 08197FFF 000c8000
* GAPI32 04A60000 04A77FFF 00018000
* EMSABP32 07540000 07563FFF 00024000
* contab32 07190000 071ADFFF 0001e000
* EMSMDB32 09670000 096FEFFF 0008f000
* adsldp 04A20000 04A41FFF 00022000
* adsmsext 06740000 06751FFF 00012000
* dbghelp 08B70000 08C24FFF 000b5000
*
* Edi: 927AB5F0: 927AA018 927ABFF0 00000000 00000000 00000000
00000
000
* Esi: 00000000:
* Eax: 927AB5F0: 927AA018 927ABFF0 00000000 00000000 00000000
00000
000
* Ebx: 927AB4D0: 00380038 000A0004 00000000 00000000 00000002
00000
000
* Ecx: 00000006:
* Edx: 000009E8:
* Eip: 00662572: 758BA5F3 33A5EBF0 A6DBE9C0 75FFFFDF 0C75FF10
0004E
1E8
* Ebp: 06FBA758: 06FBA7AC 005CE635 20642310 2249A030 06FBA82C
927AB
480
* SegCs: 0000001B:
* EFlags: 00010246: 004F0052 00520047 007E0041 005C0031 00450056
00490
052
* Esp: 06FBA724: 2249A030 927AB4D0 927AB480 00380038 000A0004
00000
000
* SegSs: 00000023:
*
****************************************
************************************
*
**
*
----
-
--
* Short Stack Dump
* 00662572 Module(sqlservr+00262572) (udf::udf+00000127)
* 005CE635 Module(sqlservr+001CE635) (CSteUdf::CSteUdf+00000077)
* 0075A864 Module(sqlservr+0035A864) (CScaOp_Udf::PqteConvert+000000BF)
The query at the top of te dump file is always the same or at least the bit
that is not truncated is. The bizarre thing is that if you run the query by
hand it runs just fine.
Does anyone have any suggestions or thoughts.
Thanks in advance for any advice offered
Jamie.How I hate those errors ;)
Normally its to do with one of the SQL Server resources failing, or at least
SQL Server thinking its failed.
When it happened to us I set the Affinity Mask to 0 and after that it worked
.
Good Luck
Peter
"jimmy" wrote:

> I have two different Production Servers which are creating SQLDump00*** fi
les.
> I suspect the issue is to do with Paralellism. As on one of the servers I
> set the MAXDOP to 1 and it has cured the problem.
> Someone in my office seems to think the issue has something to do with
> language_exec as it appears in all the logs. Can someone please tell me w
hat
> this term means.
> The error in event view is:
> SqlDumpExceptionHandler: Process 81 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> The Dump file generates:
> ========================================
=============================
> 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.
> Current time is 08:40:42 04/28/05.
> 8 Intel x86 level 15, 1999 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 4.
>
> Memory
> MemoryLoad = 78%
> Total Physical = 3775 MB
> Available Physical = 794 MB
> Total Page File = 5669 MB
> Available Page File = 2663 MB
> Total Virtual = 3071 MB
> Available Virtual = 265 MB
> *Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL\log\SQLDu
> mp0041.txt
> *
> ****************************************
**********************************
***
> **
> *
> * BEGIN STACK DUMP:
> * 04/28/05 08:40:42 spid 70
> *
> * Exception Address = 00662572 (udf::udf + 00000127 Line 0+00000000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address 00000000
> * Input Buffer 4088 bytes -
> * SELECT repExposureCust."HostName", repExposureCust."PortfolioClassSort"
,
> * repExposureCust."PortfolioClass", repExposureCust."CustID", repExposur
e
> * Cust."PfolCustCode", repExposureCust."PfolCustName", repExposureCust."P
f
> * olProdName", repExposureCust."PfolBranName", repExposureCust."PfolCptyC
o
> * de", repExposureCust."PfolPGRatCode", repExposureCust."ItemClassID", re
p
> * ExposureCust."PfolItemClass", repExposureCust."PortfolioID", repExposur
e
> * Cust."MeasureID", repExposureCust."DataMonth", repExposureCust."DaysInE
x
> * cess", repExposureCust."LimMax01", repExposureCust."LimMin01", repExpos
u
> * reCust."ExpMax01", repExposureCust."ExpMin01", repExposureCust."ExpAvg0
1
> * ", repExposureCust."LimMax02", repExposureCust."LimMin02", repExposureC
u
> * st."ExpMax02", repExposureCust."ExpMin02", repExposureCust."ExpAvg02",
r
> * epExposureCust."LimMax03", repExposureCust."LimMin03", repExposureCust.
"
> * ExpMax03", repExposureCust."ExpMin03", repExposureCust."ExpAvg03", repE
x
> * posureCust."LimMax04", repExposureCust."LimMin04", repExposureCust."Exp
M
> * ax04", repExposureCust."ExpMin04", repExposureCust."ExpAvg04", repExpos
u
> * reCust."LimMax05", repExposureCust."LimMin05", repExposureCust."ExpMax0
5
> * ", repExposureCust."ExpMin05", repExposureCust."ExpAvg05", repExposureC
u
> * st."LimMax06", repExposureCust."LimMin06", repExposureCust."ExpMax06",
r
> * epExposureCust."ExpMin06", repExposureCust."ExpAvg06", repExposureCust.
"
> * LimMax07", repExposureCust."LimMin07", repExposureCust."ExpMax07", repE
x
> * posureCust."ExpMin07", repExposureCust."ExpAvg07", repExposureCust."Lim
M
> * ax08", repExposureCust."LimMin08", repExposureCust."ExpMax08", repExpos
u
> * reCust."ExpMin08", repExposureCust."ExpAvg08", repExposureCust."LimMax0
9
> * ", repExposureCust."LimMin09", repExposureCust."ExpMax09", repExposureC
u
> * st."ExpMin09", repExposureCust."ExpAvg09", repExposureCust."LimMax10",
r
> * epExposureCust."LimMin10", repExposureCust."ExpMax10", repExposureCust.
"
> * ExpMin10", repExposureCust."ExpAvg10", repExposureCust."Measure", repEx
p
> * osureCust."LimitAttribute", repExposureCust."LimCurrSpot", repExposureC
u
> * st."ChecksClassSymbol", repE
> *
> *
> * MODULE BASE END SIZE
> * sqlservr 00400000 00B2CFFF 0072d000
> * ntdll 77F80000 77FFCFFF 0007d000
> * KERNEL32 7C570000 7C627FFF 000b8000
> * ADVAPI32 7C2D0000 7C331FFF 00062000
> * RPCRT4 77D30000 77D9DFFF 0006e000
> * USER32 77E10000 77E74FFF 00065000
> * GDI32 77F40000 77F7DFFF 0003e000
> * OPENDS60 41060000 41065FFF 00006000
> * MSVCRT 78000000 78044FFF 00045000
> * UMS 41070000 4107CFFF 0000d000
> * SQLSORT 42AE0000 42B6FFFF 00090000
> * MSVCIRT 780A0000 780B1FFF 00012000
> * tsappcmp 77630000 7763EFFF 0000f000
> * sqlevn70 41080000 41086FFF 00007000
> * NETAPI32 035B0000 035FEFFF 0004f000
> * SECUR32 03600000 0360EFFF 0000f000
> * NETRAP 03610000 03615FFF 00006000
> * SAMLIB 03620000 0362EFFF 0000f000
> * WS2_32 03630000 03643FFF 00014000
> * WS2HELP 03650000 03657FFF 00008000
> * WLDAP32 03660000 03689FFF 0002a000
> * DNSAPI 03690000 036B3FFF 00024000
> * WSOCK32 036C0000 036C7FFF 00008000
> * ole32 03CB0000 03D9BFFF 000ec000
> * XOLEHLP 03DA0000 03DA7FFF 00008000
> * MSDTCPRX 03DB0000 03E63FFF 000b4000
> * MTXCLU 03E70000 03E7FFFF 00010000
> * VERSION 03E80000 03E86FFF 00007000
> * LZ32 03E90000 03E95FFF 00006000
> * CLUSAPI 03EA0000 03EAFFFF 00010000
> * RESUTILS 03EB0000 03EBCFFF 0000d000
> * USERENV 03EC0000 03F20FFF 00061000
> * rnr20 03F30000 03F3BFFF 0000c000
> * iphlpapi 03F80000 03F92FFF 00013000
> * ICMP 03FA0000 03FA4FFF 00005000
> * MPRAPI 03FB0000 03FC6FFF 00017000
> * OLEAUT32 03FD0000 0406AFFF 0009b000
> * ACTIVEDS 04070000 0409EFFF 0002f000
> * ADSLDPC 040A0000 040C2FFF 00023000
> * RTUTILS 040D0000 040DDFFF 0000e000
> * SETUPAPI 040E0000 0416DFFF 0008e000
> * RASAPI32 04170000 041A2FFF 00033000
> * RASMAN 041B0000 041C0FFF 00011000
> * TAPI32 041D0000 041F1FFF 00022000
> * COMCTL32 04200000 04289FFF 0008a000
> * SHLWAPI 04290000 042F3FFF 00064000
> * DHCPCSVC 04300000 04318FFF 00019000
> * winrnr 047C0000 047C7FFF 00008000
> * rasadhlp 047D0000 047D4FFF 00005000
> * SSNMPN70 00BF0000 00BF5FFF 00006000
> * SSNETLIB 00C00000 00C14FFF 00015000
> * security 05280000 05283FFF 00004000
> * msafd 05290000 052ADFFF 0001e000
> * wshtcpip 052F0000 052F6FFF 00007000
> * SSmsLPCn 05300000 05306FFF 00007000
> * ntdsapi 05780000 05790FFF 00011000
> * mswsock 05420000 05431FFF 00012000
> * kerberos 057B0000 057E5FFF 00036000
> * CRYPTDLL 057F0000 057FDFFF 0000e000
> * MSASN1 05800000 0580FFFF 00010000
> * rsabase 00C70000 00C92FFF 00023000
> * CRYPT32 05320000 053A6FFF 00087000
> * SQLFTQRY 05530000 05561FFF 00032000
> * CLBCATQ 05DE0000 05E65FFF 00086000
> * sqloledb 05E90000 05F02FFF 00073000
> * MSDART 05570000 0558EFFF 0001f000
> * comdlg32 05F10000 05F4DFFF 0003e000
> * SHELL32 05F50000 06197FFF 00248000
> * MSDATL3 061A0000 061B4FFF 00015000
> * oledb32 06840000 068A5FFF 00066000
> * OLEDB32R 05590000 0559FFFF 00010000
> * msv1_0 06950000 06970FFF 00021000
> * xpsqlbot 06940000 06945FFF 00006000
> * xpstar 069C0000 06A06FFF 00047000
> * SQLRESLD 06930000 06936FFF 00007000
> * SQLSVC 06A10000 06A26FFF 00017000
> * ODBC32 06A30000 06A60FFF 00031000
> * odbcbcp 06A70000 06A75FFF 00006000
> * W95SCM 06A80000 06A8BFFF 0000c000
> * SQLUNIRL 06A90000 06ABCFFF 0002d000

Sunday, February 19, 2012

Excel to MS SQL Server via OLE - Date problem

Background:
I have Excel files that are not in a good 'data' format so I'm planning to
migrate the data out of Excel into MS SQL server. Since the data is spread
all over the place in the current Excel files, I'll need to write code to
grab the right data, build a select statement, and push the data into SQL
Server.
Current status:
I have working code that pushes the stuff I want into SQL server. Woot!
Problem:
The excel files contain date and time fields. The date cells have values of
39000, etc and the time fields are decimals from 0 to 1. All pretty standard.
When I grab a date field using the following OLE code:
TestDate = Cdat(xlSheet2.Range("D8").Value)
And then display it back, I see an actual date.
When I do the same thing with a time field, I just see the decimal number.
Problem is that when they get to SQL server,
Dates are all: 1/1/1900 12:00:00 AM
Times are: 1/1/1900 with what appears to be the right time.
The SQL server fields are Datetime.
I'm stuck - any suggestions?
TIA.
Doug
ps - I've cross posted in the Excel group
Nothing like posting a question to make the answer clear...
My OLE code buids a string that becomes the insert query on the SQL server
side.
The string looks something like:
Insert into tableX(Field1, Field2, Field3) Values ('StringValue',
numericValue)
Two things.
First: I needed to add the date value and time value from Excel into a
single number.
Second: rather than submit the value as a value, I send it as a string ala
Insert into tableX(Field1, Field2) Values ('MyString', '12/31/2008 08:00:00
AM')
poof, works great.
Hope this is of value to others.
Doug
"Doug_F" wrote:

> Background:
> I have Excel files that are not in a good 'data' format so I'm planning to
> migrate the data out of Excel into MS SQL server. Since the data is spread
> all over the place in the current Excel files, I'll need to write code to
> grab the right data, build a select statement, and push the data into SQL
> Server.
> Current status:
> I have working code that pushes the stuff I want into SQL server. Woot!
> Problem:
> The excel files contain date and time fields. The date cells have values of
> 39000, etc and the time fields are decimals from 0 to 1. All pretty standard.
> When I grab a date field using the following OLE code:
> TestDate = Cdat(xlSheet2.Range("D8").Value)
> And then display it back, I see an actual date.
> When I do the same thing with a time field, I just see the decimal number.
> Problem is that when they get to SQL server,
> Dates are all: 1/1/1900 12:00:00 AM
> Times are: 1/1/1900 with what appears to be the right time.
> The SQL server fields are Datetime.
> I'm stuck - any suggestions?
> TIA.
> Doug
> ps - I've cross posted in the Excel group

Excel to MS SQL Server via OLE - Date problem

Background:
I have Excel files that are not in a good 'data' format so I'm planning to
migrate the data out of Excel into MS SQL server. Since the data is spread
all over the place in the current Excel files, I'll need to write code to
grab the right data, build a select statement, and push the data into SQL
Server.
Current status:
I have working code that pushes the stuff I want into SQL server. Woot!
Problem:
The excel files contain date and time fields. The date cells have values of
39000, etc and the time fields are decimals from 0 to 1. All pretty standard.
When I grab a date field using the following OLE code:
TestDate = Cdat(xlSheet2.Range("D8").Value)
And then display it back, I see an actual date.
When I do the same thing with a time field, I just see the decimal number.
Problem is that when they get to SQL server,
Dates are all: 1/1/1900 12:00:00 AM
Times are: 1/1/1900 with what appears to be the right time.
The SQL server fields are Datetime.
I'm stuck - any suggestions?
TIA.
Doug
ps - I've cross posted in the Excel groupNothing like posting a question to make the answer clear...
My OLE code buids a string that becomes the insert query on the SQL server
side.
The string looks something like:
Insert into tableX(Field1, Field2, Field3) Values ('StringValue',
numericValue)
Two things.
First: I needed to add the date value and time value from Excel into a
single number.
Second: rather than submit the value as a value, I send it as a string ala
Insert into tableX(Field1, Field2) Values ('MyString', '12/31/2008 08:00:00
AM')
poof, works great.
Hope this is of value to others.
Doug
"Doug_F" wrote:
> Background:
> I have Excel files that are not in a good 'data' format so I'm planning to
> migrate the data out of Excel into MS SQL server. Since the data is spread
> all over the place in the current Excel files, I'll need to write code to
> grab the right data, build a select statement, and push the data into SQL
> Server.
> Current status:
> I have working code that pushes the stuff I want into SQL server. Woot!
> Problem:
> The excel files contain date and time fields. The date cells have values of
> 39000, etc and the time fields are decimals from 0 to 1. All pretty standard.
> When I grab a date field using the following OLE code:
> TestDate = Cdat(xlSheet2.Range("D8").Value)
> And then display it back, I see an actual date.
> When I do the same thing with a time field, I just see the decimal number.
> Problem is that when they get to SQL server,
> Dates are all: 1/1/1900 12:00:00 AM
> Times are: 1/1/1900 with what appears to be the right time.
> The SQL server fields are Datetime.
> I'm stuck - any suggestions?
> TIA.
> Doug
> ps - I've cross posted in the Excel group

Excel SQL 2000

Is it possible to store excel spreadsheet files in a sql
server database? If so how and what are the implications
of doing so..
Thanks,
AnjelinaIs this easy to do? If the excel file changes and the column is to be used for replication will the changes be replicated?
Anjelina
>--Original Message--
>Try to "dump" it in the database with Textcopy program, or use methods in
>RDO and ADO via GetChunk and AppendChunk commands. (Store it in the column
>type IMAGE)
>Jens S=FC=DFmeyer.
>
>.
>

excel source with optional columns

Hi:

I use a SSIS package to loop thro a folder and load data from multiple excel files to a SQL2005 table. Works fine except when an excel has a missing col.

Col names in xls are always a subset of col names in the table. The missing cols are random, else I would just have made another package:-)

Once a missing column is found, I get runtime and design time errors, and metadata problems. How can a get SSIS to ignore missing columns?

TIA

I recently solved this problem using a dynamically built select statement. Is it always just 1 column that's missing or do you need to load a dynamic number of columns? If it's a truly dynamic then the algorithm is a little more complex...|||

Thanks for your response. Request you tell me more aboout it.

I did the whole thing in BIDS in a SSIS project, using a ForEach container, a Excel Source and an OleDB destination. I was hoping to achieve my objectives with these objects and their settings :-).

|||I used a For Each Loop and then a For Loop to solve this problem.

The first For Each Loop iterates threw the columns names in the spreadsheet. It contains a script component that counts the columns storing the result in a variable. There might be a more efficient way to count columns but I couldn't figure out how.

The second For Loop container uses this counter variable to select and load each column one at a time. It contains 2 components; a script component that builds a select statement and a data flow task that actually moves the data using the select statement.

Here is the script code that dynamically builds each select statement:

Public Sub Main()
Dim SelectCommand As String
Dim WorksheetName As String
Dim ColumnLoopIndex As Integer
WorksheetName = Dts.Variables("WorksheetName").Value.ToString
ColumnLoopIndex = CInt(Dts.Variables("ColumnLoopIndex").Value)
SelectCommand = "Select F" & ColumnLoopIndex.ToString & " AS CurrentColumn from [" & WorksheetName & "]"
Dts.Variables("SelectCommand").Value = SelectCommand
Dts.TaskResult = Dts.Results.Success
End Sub

Please note: Depending on your data and how dynamic you want the

package to be you could skip the second For Loop and build a single select

statement that loads all of the columns. In this case your dynamically built select

statement would contain return fields like "SELECT F1, F2, NULL AS F3, NULL AS F4

FROM [myworksheetname]" to account for missing F3 and F4 columns.

Excel Source dt_ntext problems

Hi:

I import data from multiple excel files into SQL DB. I have trouble with fields that could contain >255 chars.

If I have the col type = DT_Ntext in my Data Flow, the package fails for files that do not have any values >255 chars.

If I have the external coltype=dt_wstr and the output coltype=dt_wstr(4000) the package fails if the file contains any value >255 chars.(Implicit conversion does not occur, as expected).

I worked around by adding a dummy first row with >255 chars.

Is there a way to use a cast function to solve this prob? I tried using Select dt_ntext(fieldname) from Sheet1$, but that does not work.

Is there some clean way to get around this problem?

TIA
Kar

Hi Karfast

For now this have to be done manually. I was able successfully execute getting advise from Bob Bojanic

Follw these instructions carefully:

1) Go to Mapping option at Destination, Point your mouse for each of row having your above problem and its corresponding destination (note the Datatypes types and Lengths)

2) Open Advanced Editor for the Excel Source, Under Amend the Types and Lengths accordingly for all the columns in destination to match your source Columns' type and length

Thanks

Subhash Subramanyam

|||

Metadata of Excel sheets is often hard to deal with. The dummy first row seems as a clever solution to me. It is not elegant but the entire JET provider is far from that.

Select dt_ntext(fieldname) is not going to work as dt_ntext can be recognized only by SSIS and not by the JET provider. The more adequate query would be select LongText(fieldname), but I have no idea if JET can deal with it (don't have a way to try it at the moment).

HTH.

|||

Thanks, Bob.

I tried:

Select LongText(Fieldname) , and also tried out Memo etc. All these give a Undefined Function error.

I cant even find any help on this. There is apparently something called a Jet SQL Reference, but I couldnt find it. Not even in Access 2000 Local Help.

So I guess the dirty workaround is the only way :-(

Kar

Friday, February 17, 2012

Excel reader issues

Hi,

I need to load data from excel files which will be provided by a number (around 100 monthly) of external suppliers, so we don't get 100% control over the files themselves.

What my solution involves is copying the excel file to a common name (e.g. supplierExcel.xls), turning this into a pipe delimited txt and then loading the txt. I had trouble switching files when trying to load directly from excel.

All these files should arrive in the same format of 36 fields and of course in the right order; there will be rejections if they fail.

I've come across a problem extracting the data from excel where I'm getting 'the value could not be converted because of a potential loss of data' on field 1. It only happens on excel files where there is a quote mark as the first character and I have loaded other files quite happily without the quotemark.

Has anyone seen this before? Is this a known issue and how can I get around it, without recourse to manually changing the individual files?

Thanks

nathan

Hi,

It is difficult to answer, you should be more specific on a couple of things.

- Why cannot you load direct from Excel. this could be the only fix you need, You could use the File System task.

- How do you convert the Excel to text

- Do you use table load or SQL Command

- Do you need the quote when it is the initial char? In Excel it means you want to force the cell content to be text.

If you do not need the quote, strip it from the file.

declare @.sometext as varchar(255)

set @.sometext = '''There is an initial '' in this test string'

select substring(@.sometext, patindex('''%',@.sometext)+1,255)

if you need te quote, try to replace it by 3 quotes or make sure the entry is not too long, May be you could do this

declare @.sometext as varchar(255)

set @.sometext = '''There is an initial '' in this test string'

select case left(@.sometext,1) when char(39) then char(39) + char(39) + @.sometext else @.sometext end

.Philippe