Showing posts with label explain. Show all posts
Showing posts with label explain. Show all posts

Monday, March 19, 2012

Access violation with DBCC UNPINTABLE

Customer's server, so I can't explain or change the jobs...
At 3:00 am every day, a job runs that calls DBCC PINTABLE on three tables
At 5:00 PM, another job runs that calls DBCC UNPINTABLE on those same three
tables
Both report to complete successfully, but the UNPINTABLE job causes an
access violation and creates a mini-dump file.
SQL Server 2000, sp4 plus the AWE hotfix (.2040), Windows 2K3, sp1,
single-instance 2 node cluster
Nothing on MS Site about UNPINTABLE causing AVs...
All input appreciated
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
Contact Product Support...
Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
http://blogs.msdn.com/sqlserverstorageengine/default.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:e7tDJ6iEHHA.4404@.TK2MSFTNGP06.phx.gbl...
> Customer's server, so I can't explain or change the jobs...
> At 3:00 am every day, a job runs that calls DBCC PINTABLE on three tables
> At 5:00 PM, another job runs that calls DBCC UNPINTABLE on those same
> three tables
> Both report to complete successfully, but the UNPINTABLE job causes an
> access violation and creates a mini-dump file.
> SQL Server 2000, sp4 plus the AWE hotfix (.2040), Windows 2K3, sp1,
> single-instance 2 node cluster
> Nothing on MS Site about UNPINTABLE causing AVs...
> All input appreciated
>
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
>
|||Hi Paul,
I have asked my customer if he wants to pay for that call. Unless you can
hit //bugcheck for me and see if this a known but "not going to fix"
bug...
I've also asked him why on earth he is still using PINTABLE and UNPINTABLE.
I thought that went out of style with 6.5
Thanks for the response!
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:OKsXrnnEHHA.3836@.TK2MSFTNGP02.phx.gbl...
> Contact Product Support...
> --
> Paul Randal
> Lead Program Manager, Microsoft SQL Server Storage Engine
> http://blogs.msdn.com/sqlserverstorageengine/default.aspx
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:e7tDJ6iEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>

Access violation with DBCC UNPINTABLE

Customer's server, so I can't explain or change the jobs...
At 3:00 am every day, a job runs that calls DBCC PINTABLE on three tables
At 5:00 PM, another job runs that calls DBCC UNPINTABLE on those same three
tables
Both report to complete successfully, but the UNPINTABLE job causes an
access violation and creates a mini-dump file.
SQL Server 2000, sp4 plus the AWE hotfix (.2040), Windows 2K3, sp1,
single-instance 2 node cluster
Nothing on MS Site about UNPINTABLE causing AVs...
All input appreciated
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.comContact Product Support...
Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
http://blogs.msdn.com/sqlserverstor...ne/default.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:e7tDJ6iEHHA.4404@.TK2MSFTNGP06.phx.gbl...
> Customer's server, so I can't explain or change the jobs...
> At 3:00 am every day, a job runs that calls DBCC PINTABLE on three tables
> At 5:00 PM, another job runs that calls DBCC UNPINTABLE on those same
> three tables
> Both report to complete successfully, but the UNPINTABLE job causes an
> access violation and creates a mini-dump file.
> SQL Server 2000, sp4 plus the AWE hotfix (.2040), Windows 2K3, sp1,
> single-instance 2 node cluster
> Nothing on MS Site about UNPINTABLE causing AVs...
> All input appreciated
>
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
>|||Hi Paul,
I have asked my customer if he wants to pay for that call. Unless you can
hit //bugcheck for me and see if this a known but "not going to fix"
bug...
I've also asked him why on earth he is still using PINTABLE and UNPINTABLE.
I thought that went out of style with 6.5
Thanks for the response!
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:OKsXrnnEHHA.3836@.TK2MSFTNGP02.phx.gbl...
> Contact Product Support...
> --
> Paul Randal
> Lead Program Manager, Microsoft SQL Server Storage Engine
> http://blogs.msdn.com/sqlserverstor...ne/default.aspx
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:e7tDJ6iEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>

Access violation with DBCC UNPINTABLE

Customer's server, so I can't explain or change the jobs...
At 3:00 am every day, a job runs that calls DBCC PINTABLE on three tables
At 5:00 PM, another job runs that calls DBCC UNPINTABLE on those same three
tables
Both report to complete successfully, but the UNPINTABLE job causes an
access violation and creates a mini-dump file.
SQL Server 2000, sp4 plus the AWE hotfix (.2040), Windows 2K3, sp1,
single-instance 2 node cluster
Nothing on MS Site about UNPINTABLE causing AVs...
All input appreciated :)
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.comContact Product Support...
--
Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
http://blogs.msdn.com/sqlserverstorageengine/default.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:e7tDJ6iEHHA.4404@.TK2MSFTNGP06.phx.gbl...
> Customer's server, so I can't explain or change the jobs...
> At 3:00 am every day, a job runs that calls DBCC PINTABLE on three tables
> At 5:00 PM, another job runs that calls DBCC UNPINTABLE on those same
> three tables
> Both report to complete successfully, but the UNPINTABLE job causes an
> access violation and creates a mini-dump file.
> SQL Server 2000, sp4 plus the AWE hotfix (.2040), Windows 2K3, sp1,
> single-instance 2 node cluster
> Nothing on MS Site about UNPINTABLE causing AVs...
> All input appreciated :)
>
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
>|||Hi Paul,
I have asked my customer if he wants to pay for that call. Unless you can
hit //bugcheck for me and see if this a known but "not going to fix"
bug...:)
I've also asked him why on earth he is still using PINTABLE and UNPINTABLE.
I thought that went out of style with 6.5
Thanks for the response!
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:OKsXrnnEHHA.3836@.TK2MSFTNGP02.phx.gbl...
> Contact Product Support...
> --
> Paul Randal
> Lead Program Manager, Microsoft SQL Server Storage Engine
> http://blogs.msdn.com/sqlserverstorageengine/default.aspx
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:e7tDJ6iEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>> Customer's server, so I can't explain or change the jobs...
>> At 3:00 am every day, a job runs that calls DBCC PINTABLE on three tables
>> At 5:00 PM, another job runs that calls DBCC UNPINTABLE on those same
>> three tables
>> Both report to complete successfully, but the UNPINTABLE job causes an
>> access violation and creates a mini-dump file.
>> SQL Server 2000, sp4 plus the AWE hotfix (.2040), Windows 2K3, sp1,
>> single-instance 2 node cluster
>> Nothing on MS Site about UNPINTABLE causing AVs...
>> All input appreciated :)
>>
>> --
>> Kevin Hill
>> 3NF Consulting
>> http://www.3nf-inc.com/NewsGroups.htm
>> Real-world stuff I run across with SQL Server:
>> http://kevin3nf.blogspot.com
>>
>

Friday, February 24, 2012

Access report with SQL server BE hangs on one p/c but not others

Hi
I have a MS Access database which uses SQL server 2000 (SBS 2003) as a
back end (using ODBC).
Can anybody explain to me why one p/c should have a problem with one
report? When you click on the button which runs the report, the egg
timer comes on for about 10 minutes and then the following error is
displayed:
Connection failed
SQL State '01000'
SQL Server error 53
[microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
Connection failed
SQL State '08001
SQL Error 17
[microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
exist
or access denied
All other reports in the Access application run fine on this p/c. The
report itself runs fine on all other p/cs that I have tried it on. The
same error occurs whichever user is logged onto the p/c.
Can anybody make any suggestions as to what might be going on?
Thanks
ColinBooby
At first glance it seems that this specific report is connected to SQL
Server with 'wrong' login or to 'wrong' database. Also it could permission
issues
Can you compare everything with 'working' reports?
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1180954455.134604.78650@.w5g2000hsg.googlegroups.com...
> Hi
> I have a MS Access database which uses SQL server 2000 (SBS 2003) as a
> back end (using ODBC).
> Can anybody explain to me why one p/c should have a problem with one
> report? When you click on the button which runs the report, the egg
> timer comes on for about 10 minutes and then the following error is
> displayed:
> Connection failed
> SQL State '01000'
> SQL Server error 53
> [microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
> Connection failed
> SQL State '08001
> SQL Error 17
> [microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does n
ot exist
> or access denied
> All other reports in the Access application run fine on this p/c. The
> report itself runs fine on all other p/cs that I have tried it on. The
> same error occurs whichever user is logged onto the p/c.
> Can anybody make any suggestions as to what might be going on?
> Thanks
> Colin
>

Access report with SQL server BE hangs on one p/c but not others

Hi
I have a MS Access database which uses SQL server 2000 (SBS 2003) as a
back end (using ODBC).
Can anybody explain to me why one p/c should have a problem with one
report? When you click on the button which runs the report, the egg
timer comes on for about 10 minutes and then the following error is
displayed:
Connection failed
SQL State '01000'
SQL Server error 53
[microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
Connection failed
SQL State '08001
SQL Error 17
[microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
or access denied
All other reports in the Access application run fine on this p/c. The
report itself runs fine on all other p/cs that I have tried it on. The
same error occurs whichever user is logged onto the p/c.
Can anybody make any suggestions as to what might be going on?
Thanks
Colin
Booby
At first glance it seems that this specific report is connected to SQL
Server with 'wrong' login or to 'wrong' database. Also it could permission
issues
Can you compare everything with 'working' reports?
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1180954455.134604.78650@.w5g2000hsg.googlegrou ps.com...
> Hi
> I have a MS Access database which uses SQL server 2000 (SBS 2003) as a
> back end (using ODBC).
> Can anybody explain to me why one p/c should have a problem with one
> report? When you click on the button which runs the report, the egg
> timer comes on for about 10 minutes and then the following error is
> displayed:
> Connection failed
> SQL State '01000'
> SQL Server error 53
> [microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
> Connection failed
> SQL State '08001
> SQL Error 17
> [microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
> or access denied
> All other reports in the Access application run fine on this p/c. The
> report itself runs fine on all other p/cs that I have tried it on. The
> same error occurs whichever user is logged onto the p/c.
> Can anybody make any suggestions as to what might be going on?
> Thanks
> Colin
>

Access report with SQL server BE hangs on one p/c but not others

Hi
I have a MS Access database which uses SQL server 2000 (SBS 2003) as a
back end (using ODBC).
Can anybody explain to me why one p/c should have a problem with one
report? When you click on the button which runs the report, the egg
timer comes on for about 10 minutes and then the following error is
displayed:
Connection failed
SQL State '01000'
SQL Server error 53
[microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
Connection failed
SQL State '08001
SQL Error 17
[microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
or access denied
All other reports in the Access application run fine on this p/c. The
report itself runs fine on all other p/cs that I have tried it on. The
same error occurs whichever user is logged onto the p/c.
Can anybody make any suggestions as to what might be going on?
Thanks
ColinBooby
At first glance it seems that this specific report is connected to SQL
Server with 'wrong' login or to 'wrong' database. Also it could permission
issues
Can you compare everything with 'working' reports?
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1180954455.134604.78650@.w5g2000hsg.googlegroups.com...
> Hi
> I have a MS Access database which uses SQL server 2000 (SBS 2003) as a
> back end (using ODBC).
> Can anybody explain to me why one p/c should have a problem with one
> report? When you click on the button which runs the report, the egg
> timer comes on for about 10 minutes and then the following error is
> displayed:
> Connection failed
> SQL State '01000'
> SQL Server error 53
> [microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
> Connection failed
> SQL State '08001
> SQL Error 17
> [microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
> or access denied
> All other reports in the Access application run fine on this p/c. The
> report itself runs fine on all other p/cs that I have tried it on. The
> same error occurs whichever user is logged onto the p/c.
> Can anybody make any suggestions as to what might be going on?
> Thanks
> Colin
>