Estimating hardware requirements for a SQL Server 2005 installation

Is there any good online documentation describing rules of thumb for estimating and planning a SQL Server 2005 deployment in support of a Windows rich client/WCF services architecture?

TIA,

Ian
Well you do not want to hear that answer, but it depends.It′s like asking, How much gas will I need when I travel from NYC to Seattle. Well that depends on how much data / luggage will be transported, which transport device you use, how much data will be retrieved, how often you will query the database, how many users will access the database, etc. There are many parameters to consider.

Jens K. Suessmeyer.

http://www.sqlserver2005.de
sql

Estimated cost shows 300% in query plan

Hello all,
On a SQL Server 2000 sp4, on a 4 Xeon cpus (with hyperthreading) machine
(Windows Server 2003), most of the query plans I see are showing, on the
estimated cost of each step of the plan, more than 100% (e.g. 300% for a
seek).
Does anyone have an explanation or has already seen that ?
tia,
Rudi Bruchez
MCDBAIt's a bug in the graphical query plans when dealing with parallel query
plans. I have seen percentage reaching 4 figures even. I don't think it will
be fixed, considering it wasn't fixed in SP4.
--
Jacco Schalkwijk
SQL Server MVP
"Rudi Bruchez" <rudi#no-spam#at.babaluga.com> wrote in message
news:138syoixibdyn$.14zc2fkwrr1j5.dlg@.40tude.net...
> Hello all,
> On a SQL Server 2000 sp4, on a 4 Xeon cpus (with hyperthreading) machine
> (Windows Server 2003), most of the query plans I see are showing, on the
> estimated cost of each step of the plan, more than 100% (e.g. 300% for a
> seek).
> Does anyone have an explanation or has already seen that ?
> tia,
> Rudi Bruchez
> MCDBA|||On Thu, 27 Oct 2005 16:13:39 +0100, Jacco Schalkwijk wrote:
> It's a bug in the graphical query plans when dealing with parallel query
> plans. I have seen percentage reaching 4 figures even. I don't think it will
> be fixed, considering it wasn't fixed in SP4.
Hi,
Thanks for the feedback. My problem is that I've set the maximum degree of
parallelism to 1 at the server level, and there's no mention of parallelism
on the graphical plan. Should this still appear ?
Btw, even with a maxdop to 1, I still see some "degree of parallelism"
event in profiler, with a BinaryData (CPUs involved) at 0X00000000.
Is it explanable ?
thanks again,
Rudi Bruchez|||On Thu, 27 Oct 2005 17:05:35 +0200, Rudi Bruchez
<rudi#no-spam#at.babaluga.com> wrote:
>On a SQL Server 2000 sp4, on a 4 Xeon cpus (with hyperthreading) machine
>(Windows Server 2003), most of the query plans I see are showing, on the
>estimated cost of each step of the plan, more than 100% (e.g. 300% for a
>seek).
>Does anyone have an explanation or has already seen that ?
It happens.
:)
How about the after-query plan?
J.|||Rudi Bruchez wrote:
> On Thu, 27 Oct 2005 16:13:39 +0100, Jacco Schalkwijk wrote:
>> It's a bug in the graphical query plans when dealing with parallel
>> query plans. I have seen percentage reaching 4 figures even. I don't
>> think it will be fixed, considering it wasn't fixed in SP4.
> Hi,
> Thanks for the feedback. My problem is that I've set the maximum
> degree of parallelism to 1 at the server level, and there's no
> mention of parallelism on the graphical plan. Should this still
> appear ?
> Btw, even with a maxdop to 1, I still see some "degree of parallelism"
> event in profiler, with a BinaryData (CPUs involved) at 0X00000000.
> Is it explanable ?
> thanks again,
> Rudi Bruchez
What happens with the actual plan, not the estimated one? Does it
display correctly? What happens if you add a MAXDOP (1) to the query?
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||On Thu, 27 Oct 2005 18:33:59 -0400, David Gugick wrote:
> Rudi Bruchez wrote:
>> On Thu, 27 Oct 2005 16:13:39 +0100, Jacco Schalkwijk wrote:
>> It's a bug in the graphical query plans when dealing with parallel
>> query plans. I have seen percentage reaching 4 figures even. I don't
>> think it will be fixed, considering it wasn't fixed in SP4.
>> Hi,
>> Thanks for the feedback. My problem is that I've set the maximum
>> degree of parallelism to 1 at the server level, and there's no
>> mention of parallelism on the graphical plan. Should this still
>> appear ?
>> Btw, even with a maxdop to 1, I still see some "degree of parallelism"
>> event in profiler, with a BinaryData (CPUs involved) at 0X00000000.
>> Is it explanable ?
>> thanks again,
>> Rudi Bruchez
> What happens with the actual plan, not the estimated one? Does it
> display correctly? What happens if you add a MAXDOP (1) to the query?
Hello,
I was talking about the actual plan, no difference there with the
estimated, on both I see 300% on several seeks. Same if I put the MAXDOP
(1) option on the query.
I'm interested in this also because it is a server hosted by an ISP, and
there are sometimes performances problems I've difficulties to explain form
the SQL server perspective only. I'm tracing peculiarities which could be
signs for problems.

Estimated cost shows 300% in query plan

Hello all,
On a SQL Server 2000 sp4, on a 4 Xeon cpus (with hyperthreading) machine
(Windows Server 2003), most of the query plans I see are showing, on the
estimated cost of each step of the plan, more than 100% (e.g. 300% for a
seek).
Does anyone have an explanation or has already seen that ?
tia,
Rudi Bruchez
MCDBA
It's a bug in the graphical query plans when dealing with parallel query
plans. I have seen percentage reaching 4 figures even. I don't think it will
be fixed, considering it wasn't fixed in SP4.
Jacco Schalkwijk
SQL Server MVP
"Rudi Bruchez" <rudi#no-spam#at.babaluga.com> wrote in message
news:138syoixibdyn$.14zc2fkwrr1j5.dlg@.40tude.net.. .
> Hello all,
> On a SQL Server 2000 sp4, on a 4 Xeon cpus (with hyperthreading) machine
> (Windows Server 2003), most of the query plans I see are showing, on the
> estimated cost of each step of the plan, more than 100% (e.g. 300% for a
> seek).
> Does anyone have an explanation or has already seen that ?
> tia,
> Rudi Bruchez
> MCDBA
|||On Thu, 27 Oct 2005 16:13:39 +0100, Jacco Schalkwijk wrote:

> It's a bug in the graphical query plans when dealing with parallel query
> plans. I have seen percentage reaching 4 figures even. I don't think it will
> be fixed, considering it wasn't fixed in SP4.
Hi,
Thanks for the feedback. My problem is that I've set the maximum degree of
parallelism to 1 at the server level, and there's no mention of parallelism
on the graphical plan. Should this still appear ?
Btw, even with a maxdop to 1, I still see some "degree of parallelism"
event in profiler, with a BinaryData (CPUs involved) at 0X00000000.
Is it explanable ?
thanks again,
Rudi Bruchez
|||On Thu, 27 Oct 2005 17:05:35 +0200, Rudi Bruchez
<rudi#no-spam#at.babaluga.com> wrote:
>On a SQL Server 2000 sp4, on a 4 Xeon cpus (with hyperthreading) machine
>(Windows Server 2003), most of the query plans I see are showing, on the
>estimated cost of each step of the plan, more than 100% (e.g. 300% for a
>seek).
>Does anyone have an explanation or has already seen that ?
It happens.

How about the after-query plan?
J.
|||Rudi Bruchez wrote:
> On Thu, 27 Oct 2005 16:13:39 +0100, Jacco Schalkwijk wrote:
>
> Hi,
> Thanks for the feedback. My problem is that I've set the maximum
> degree of parallelism to 1 at the server level, and there's no
> mention of parallelism on the graphical plan. Should this still
> appear ?
> Btw, even with a maxdop to 1, I still see some "degree of parallelism"
> event in profiler, with a BinaryData (CPUs involved) at 0X00000000.
> Is it explanable ?
> thanks again,
> Rudi Bruchez
What happens with the actual plan, not the estimated one? Does it
display correctly? What happens if you add a MAXDOP (1) to the query?
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||On Thu, 27 Oct 2005 18:33:59 -0400, David Gugick wrote:

> Rudi Bruchez wrote:
> What happens with the actual plan, not the estimated one? Does it
> display correctly? What happens if you add a MAXDOP (1) to the query?
Hello,
I was talking about the actual plan, no difference there with the
estimated, on both I see 300% on several seeks. Same if I put the MAXDOP
(1) option on the query.
I'm interested in this also because it is a server hosted by an ISP, and
there are sometimes performances problems I've difficulties to explain form
the SQL server perspective only. I'm tracing peculiarities which could be
signs for problems.

Estimated cost shows 300% in query plan

Hello all,
On a SQL Server 2000 sp4, on a 4 Xeon cpus (with hyperthreading) machine
(Windows Server 2003), most of the query plans I see are showing, on the
estimated cost of each step of the plan, more than 100% (e.g. 300% for a
seek).
Does anyone have an explanation or has already seen that ?
tia,
Rudi Bruchez
MCDBAIt's a bug in the graphical query plans when dealing with parallel query
plans. I have seen percentage reaching 4 figures even. I don't think it will
be fixed, considering it wasn't fixed in SP4.
Jacco Schalkwijk
SQL Server MVP
"Rudi Bruchez" <rudi#no-spam#at.babaluga.com> wrote in message
news:138syoixibdyn$.14zc2fkwrr1j5.dlg@.40tude.net...
> Hello all,
> On a SQL Server 2000 sp4, on a 4 Xeon cpus (with hyperthreading) machine
> (Windows Server 2003), most of the query plans I see are showing, on the
> estimated cost of each step of the plan, more than 100% (e.g. 300% for a
> seek).
> Does anyone have an explanation or has already seen that ?
> tia,
> Rudi Bruchez
> MCDBA|||On Thu, 27 Oct 2005 16:13:39 +0100, Jacco Schalkwijk wrote:

> It's a bug in the graphical query plans when dealing with parallel query
> plans. I have seen percentage reaching 4 figures even. I don't think it wi
ll
> be fixed, considering it wasn't fixed in SP4.
Hi,
Thanks for the feedback. My problem is that I've set the maximum degree of
parallelism to 1 at the server level, and there's no mention of parallelism
on the graphical plan. Should this still appear ?
Btw, even with a maxdop to 1, I still see some "degree of parallelism"
event in profiler, with a BinaryData (CPUs involved) at 0X00000000.
Is it explanable ?
thanks again,
Rudi Bruchez|||On Thu, 27 Oct 2005 17:05:35 +0200, Rudi Bruchez
<rudi#no-spam#at.babaluga.com> wrote:
>On a SQL Server 2000 sp4, on a 4 Xeon cpus (with hyperthreading) machine
>(Windows Server 2003), most of the query plans I see are showing, on the
>estimated cost of each step of the plan, more than 100% (e.g. 300% for a
>seek).
>Does anyone have an explanation or has already seen that ?
It happens.

How about the after-query plan?
J.|||Rudi Bruchez wrote:
> On Thu, 27 Oct 2005 16:13:39 +0100, Jacco Schalkwijk wrote:
>
> Hi,
> Thanks for the feedback. My problem is that I've set the maximum
> degree of parallelism to 1 at the server level, and there's no
> mention of parallelism on the graphical plan. Should this still
> appear ?
> Btw, even with a maxdop to 1, I still see some "degree of parallelism"
> event in profiler, with a BinaryData (CPUs involved) at 0X00000000.
> Is it explanable ?
> thanks again,
> Rudi Bruchez
What happens with the actual plan, not the estimated one? Does it
display correctly? What happens if you add a MAXDOP (1) to the query?
David Gugick
Quest Software
www.imceda.com
www.quest.com|||On Thu, 27 Oct 2005 18:33:59 -0400, David Gugick wrote:

> Rudi Bruchez wrote:
> What happens with the actual plan, not the estimated one? Does it
> display correctly? What happens if you add a MAXDOP (1) to the query?
Hello,
I was talking about the actual plan, no difference there with the
estimated, on both I see 300% on several seeks. Same if I put the MAXDOP
(1) option on the query.
I'm interested in this also because it is a server hosted by an ISP, and
there are sometimes performances problems I've difficulties to explain form
the SQL server perspective only. I'm tracing peculiarities which could be
signs for problems.sql

Error-Unable to get report parameters:Unable to access Web Service

Hi - In our RS + SP1 installation on Windows Server 2003, we recently began
to get the following error:
"Unable to get report parameters: Unable to access Web Service: The request
failed with HTTP status 403: Forbidden."
We are calling Render() in code using an account which has admin rights to
the RS box, is not locked out, etc. Event logs show no failures and the RS
logs are as useless as ever. I see no access denieds from Windows auditing
either.
Thoughts?
thanks muchHi,
Thanks for your posting!
From your descriptions, I understood that you are not able to access Web
Service with the error message "Unable to get report parameters: Unable to
access Web Service: The request failed with HTTP status 403: Forbidden."
Have I understood you? Correct me if I was wrong.
Based on my knowledge, it seems that "anonymous" for Reportserver virual
folder is enabled. Please try the following steps and let me know whether
it works
1. Right click ReportServer in IIS->Properties->Directory Security
2. Make sure "Intergrated Windows authentication" is checked and "enable
anonymouse access" is unchecked.
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael, I looked at my anonymous setting but it was set properly.
By chance, I tried to execute http://server/reportserver/reportservice.asmx
and it said that there were no permissions to execute scripts in this virtual
root. Sure enough, I looked at the ReportServer virtual root config and the
Execute permissions were improperly set. Not sure how changed, but once I
put it back to "Scripts and Executables" I was good.
Thanks much
"Michael Cheng [MSFT]" wrote:
> Hi,
> Thanks for your posting!
> From your descriptions, I understood that you are not able to access Web
> Service with the error message "Unable to get report parameters: Unable to
> access Web Service: The request failed with HTTP status 403: Forbidden."
> Have I understood you? Correct me if I was wrong.
> Based on my knowledge, it seems that "anonymous" for Reportserver virual
> folder is enabled. Please try the following steps and let me know whether
> it works
> 1. Right click ReportServer in IIS->Properties->Directory Security
> 2. Make sure "Intergrated Windows authentication" is checked and "enable
> anonymouse access" is unchecked.
> Thank you for your patience and corporation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>|||Hi,
Thanks for your prompt updates!
It's great to hear that it did turn out to be an authority issue and you
yourself have resolved it.
Thank you for your patience and corporation. If you have any questions or
concerns on SQL Server, don't hesitate to let me know. We are always here
to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.sql

Errors after upgrade

After upgrading the server to Windows 2003 Server, I
receive the following error when trying to view all table
rows - Unknown Error 8007007F. I tried reinstalling
SP3a, but that resulted in the same error. Also, the
ODBC connections from desktops to the database receive
an "ODBC failed" error.
Anyone know what may be causing these errors?Mike,
Try applying MDAC 2.8. If that fails, there is a fix for the oledb32.dll
file which you can obtain from Microsoft.
Symptoms:
After upgrading from Windows 2000 to Windows 2003 attempting to access a
database or data component will result in a '8007007f' or "The specified
procedure could not be found" error.
Status:
This is a known issue with some installations of Windows 2003
Workaround:
Extract oledb32.dll from the zip file into these two directories. It's
important that it be done in this order:
1) C:\WINNT\system32\dllCache
2) C:\Program Files\Common Files\System\OLE DB
3) Reboot the server
Cause:
This issue is caused when the Windows 2003 installer did not update the
oledb32.dll file.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mike wrote:
> After upgrading the server to Windows 2003 Server, I
> receive the following error when trying to view all table
> rows - Unknown Error 8007007F. I tried reinstalling
> SP3a, but that resulted in the same error. Also, the
> ODBC connections from desktops to the database receive
> an "ODBC failed" error.
> Anyone know what may be causing these errors?|||Mark,
I tried the MDAC 2.8 install, but the same errors
occurred. Is the oledb32.dll file I need on the MS site
(I checked the Knowledge Base, but didn't find anything)
or on the Win 2003 CD?
Thanks for your help.
>--Original Message--
>Mike,
>Try applying MDAC 2.8. If that fails, there is a fix for
the oledb32.dll
>file which you can obtain from Microsoft.
>Symptoms:
>After upgrading from Windows 2000 to Windows 2003
attempting to access a
>database or data component will result in a '8007007f'
or "The specified
>procedure could not be found" error.
>Status:
>This is a known issue with some installations of Windows
2003
>Workaround:
>Extract oledb32.dll from the zip file into these two
directories. It's
>important that it be done in this order:
>1) C:\WINNT\system32\dllCache
>2) C:\Program Files\Common Files\System\OLE DB
>3) Reboot the server
>Cause:
>This issue is caused when the Windows 2003 installer did
not update the
>oledb32.dll file.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mike wrote:
>> After upgrading the server to Windows 2003 Server, I
>> receive the following error when trying to view all
table
>> rows - Unknown Error 8007007F. I tried reinstalling
>> SP3a, but that resulted in the same error. Also, the
>> ODBC connections from desktops to the database receive
>> an "ODBC failed" error.
>> Anyone know what may be causing these errors?
>.
>|||Mike,
http://www.promiseweb.com/oledb32.zip
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mike wrote:
> Mark,
> I tried the MDAC 2.8 install, but the same errors
> occurred. Is the oledb32.dll file I need on the MS site
> (I checked the Knowledge Base, but didn't find anything)
> or on the Win 2003 CD?
> Thanks for your help.
>|||Hi David,
I ran into this error, too. The link is broken.
So I just downloaded MDAC 2.8 from the Microsoft homepage and used the oledb32.dll from within this package. Replaced the file in the dllcache and program files folders, rebootet the server and everything's ok !
Hope this helps,
Torsten
"David Wilson" wrote:
> Mark,
> I have encountered the same problem, but your link to the URL is no longer valid.
> Any thoughts or help would be most appreciated.
> David
> "Mark Allison" wrote:
> > Mike,
> >
> > http://www.promiseweb.com/oledb32.zip
> >
> > --
> > Mark Allison, SQL Server MVP
> > http://www.markallison.co.uk
> >
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> >
> > Mike wrote:
> > > Mark,
> > > I tried the MDAC 2.8 install, but the same errors
> > > occurred. Is the oledb32.dll file I need on the MS site
> > > (I checked the Knowledge Base, but didn't find anything)
> > > or on the Win 2003 CD?
> > > Thanks for your help.
> > >
> > >
> >

Errors after upgrade

After upgrading the server to Windows 2003 Server, I
receive the following error when trying to view all table
rows - Unknown Error 8007007F. I tried reinstalling
SP3a, but that resulted in the same error. Also, the
ODBC connections from desktops to the database receive
an "ODBC failed" error.
Anyone know what may be causing these errors?Mike,
Try applying MDAC 2.8. If that fails, there is a fix for the oledb32.dll
file which you can obtain from Microsoft.
Symptoms:
After upgrading from Windows 2000 to Windows 2003 attempting to access a
database or data component will result in a '8007007f' or "The specified
procedure could not be found" error.
Status:
This is a known issue with some installations of Windows 2003
Workaround:
Extract oledb32.dll from the zip file into these two directories. It's
important that it be done in this order:
1) C:\WINNT\system32\dllCache
2) C:\Program Files\Common Files\System\OLE DB
3) Reboot the server
Cause:
This issue is caused when the Windows 2003 installer did not update the
oledb32.dll file.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mike wrote:
> After upgrading the server to Windows 2003 Server, I
> receive the following error when trying to view all table
> rows - Unknown Error 8007007F. I tried reinstalling
> SP3a, but that resulted in the same error. Also, the
> ODBC connections from desktops to the database receive
> an "ODBC failed" error.
> Anyone know what may be causing these errors?|||Mark,
I tried the MDAC 2.8 install, but the same errors
occurred. Is the oledb32.dll file I need on the MS site
(I checked the Knowledge Base, but didn't find anything)
or on the Win 2003 CD?
Thanks for your help.

>--Original Message--
>Mike,
>Try applying MDAC 2.8. If that fails, there is a fix for
the oledb32.dll
>file which you can obtain from Microsoft.
>Symptoms:
>After upgrading from Windows 2000 to Windows 2003
attempting to access a
>database or data component will result in a '8007007f'
or "The specified
>procedure could not be found" error.
>Status:
>This is a known issue with some installations of Windows
2003
>Workaround:
>Extract oledb32.dll from the zip file into these two
directories. It's
>important that it be done in this order:
>1) C:\WINNT\system32\dllCache
>2) C:\Program Files\Common Files\System\OLE DB
>3) Reboot the server
>Cause:
>This issue is caused when the Windows 2003 installer did
not update the
>oledb32.dll file.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mike wrote:
table[vbcol=seagreen]
>.
>|||Mike,
http://www.promiseweb.com/oledb32.zip
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mike wrote:
> Mark,
> I tried the MDAC 2.8 install, but the same errors
> occurred. Is the oledb32.dll file I need on the MS site
> (I checked the Knowledge Base, but didn't find anything)
> or on the Win 2003 CD?
> Thanks for your help.
>|||Mark,
I have encountered the same problem, but your link to the URL is no longer v
alid.
Any thoughts or help would be most appreciated.
David
"Mark Allison" wrote:

> Mike,
> http://www.promiseweb.com/oledb32.zip
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Mike wrote:
>|||Hi David,
I ran into this error, too. The link is broken.
So I just downloaded MDAC 2.8 from the Microsoft homepage and used the oledb
32.dll from within this package. Replaced the file in the dllcache and progr
am files folders, rebootet the server and everything's ok !
Hope this helps,
Torsten
"David Wilson" wrote:
[vbcol=seagreen]
> Mark,
> I have encountered the same problem, but your link to the URL is no longer
valid.
> Any thoughts or help would be most appreciated.
> David
> "Mark Allison" wrote:
>

Errors after upgrade

After upgrading the server to Windows 2003 Server, I
receive the following error when trying to view all table
rows - Unknown Error 8007007F. I tried reinstalling
SP3a, but that resulted in the same error. Also, the
ODBC connections from desktops to the database receive
an "ODBC failed" error.
Anyone know what may be causing these errors?
Mike,
Try applying MDAC 2.8. If that fails, there is a fix for the oledb32.dll
file which you can obtain from Microsoft.
Symptoms:
After upgrading from Windows 2000 to Windows 2003 attempting to access a
database or data component will result in a '8007007f' or "The specified
procedure could not be found" error.
Status:
This is a known issue with some installations of Windows 2003
Workaround:
Extract oledb32.dll from the zip file into these two directories. It's
important that it be done in this order:
1) C:\WINNT\system32\dllCache
2) C:\Program Files\Common Files\System\OLE DB
3) Reboot the server
Cause:
This issue is caused when the Windows 2003 installer did not update the
oledb32.dll file.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mike wrote:
> After upgrading the server to Windows 2003 Server, I
> receive the following error when trying to view all table
> rows - Unknown Error 8007007F. I tried reinstalling
> SP3a, but that resulted in the same error. Also, the
> ODBC connections from desktops to the database receive
> an "ODBC failed" error.
> Anyone know what may be causing these errors?
|||Mark,
I tried the MDAC 2.8 install, but the same errors
occurred. Is the oledb32.dll file I need on the MS site
(I checked the Knowledge Base, but didn't find anything)
or on the Win 2003 CD?
Thanks for your help.

>--Original Message--
>Mike,
>Try applying MDAC 2.8. If that fails, there is a fix for
the oledb32.dll
>file which you can obtain from Microsoft.
>Symptoms:
>After upgrading from Windows 2000 to Windows 2003
attempting to access a
>database or data component will result in a '8007007f'
or "The specified
>procedure could not be found" error.
>Status:
>This is a known issue with some installations of Windows
2003
>Workaround:
>Extract oledb32.dll from the zip file into these two
directories. It's
>important that it be done in this order:
>1) C:\WINNT\system32\dllCache
>2) C:\Program Files\Common Files\System\OLE DB
>3) Reboot the server
>Cause:
>This issue is caused when the Windows 2003 installer did
not update the[vbcol=seagreen]
>oledb32.dll file.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mike wrote:
table
>.
>
|||Mike,
http://www.promiseweb.com/oledb32.zip
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mike wrote:
> Mark,
> I tried the MDAC 2.8 install, but the same errors
> occurred. Is the oledb32.dll file I need on the MS site
> (I checked the Knowledge Base, but didn't find anything)
> or on the Win 2003 CD?
> Thanks for your help.
>
|||Mark,
I have encountered the same problem, but your link to the URL is no longer valid.
Any thoughts or help would be most appreciated.
David
"Mark Allison" wrote:

> Mike,
> http://www.promiseweb.com/oledb32.zip
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Mike wrote:
>
|||Hi David,
I ran into this error, too. The link is broken.
So I just downloaded MDAC 2.8 from the Microsoft homepage and used the oledb32.dll from within this package. Replaced the file in the dllcache and program files folders, rebootet the server and everything's ok !
Hope this helps,
Torsten
"David Wilson" wrote:
[vbcol=seagreen]
> Mark,
> I have encountered the same problem, but your link to the URL is no longer valid.
> Any thoughts or help would be most appreciated.
> David
> "Mark Allison" wrote:

Errorlogs

Hello All,
I have a SQL server 2000 with sp 3 running on Windows 2000. In the
enterprise manager, when I go to look at errorlogs, it only displays the
most current errorlog and then log # 6. It is not showing any of the
other errorlog files between the current and the number 6. Also, when I
run the command sp_cycle_errorlog, it is not cycling it. My current
errorlog has grown to 321 MB and I want to cycle it.
Have any ideas.
Thanks,
Raziq.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!I am not sure how to address the missing errorlogs or the sp_cycle_errorlog
problem but if you truly want to recycle the SQL Server errorlog, plan a
time to stop and then restart SQL Server. This should recycle the log.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Errorlog File The system cannot find the path specified

I have a cluster SQL Server 2000 database with Windows 2003 server operating
system. Periodically I receive the error listed below. The database is
functioning properly when I received this error message.
Please help me determine why this error occurs periodically.
Thanks,
initerrlog: Could not open error log file 'F=:\LOG\ERRORLOG'. Operating
system error = 3(The system cannot find the path specified.).
Hi,
just go that path and see is there any error log file or not
if not then create a error logfile.
U did not mentioned from where does this error occurs.
thanx
from
killer

Errorlog File The system cannot find the path specified

I have a cluster SQL Server 2000 database with Windows 2003 server operating
system. Periodically I receive the error listed below. The database is
functioning properly when I received this error message.
Please help me determine why this error occurs periodically.
Thanks,
initerrlog: Could not open error log file 'F=:\LOG\ERRORLOG'. Operating
system error = 3(The system cannot find the path specified.).Hi,
just go that path and see is there any error log file or not
if not then create a error logfile.
U did not mentioned from where does this error occurs.
thanx
from
killer

Errorlog File The system cannot find the path specified

I have a cluster SQL Server 2000 database with Windows 2003 server operating
system. Periodically I receive the error listed below. The database is
functioning properly when I received this error message.
Please help me determine why this error occurs periodically.
Thanks,
initerrlog: Could not open error log file 'F=:\LOG\ERRORLOG'. Operating
system error = 3(The system cannot find the path specified.).Hi,
just go that path and see is there any error log file or not
if not then create a error logfile.
U did not mentioned from where does this error occurs.
thanx
from
killer

error:26 Error Locating Server/Instance Specified

I am having trouble connecting to Sql Server 2005 Express from asp.net
2.0 app on Windows Server 2003. I am using Sql Server Authentication,
and I tried the below article's suggestions a number of times. When I
login to to the machine, and login, I am able to get authenticated.
However, when I debug my application, I get the error below. Do I have
to give the sql server authenticaed account I created certain
permissions? Whould I set a port, and use the ipaddress rather than
the server name? Any suggestions would be greatly appreciated.
http://support.microsoft.com/kb/914277
My Error:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified)
My Connection String:
<add key="ConnectionString"
value="server=MyServerName;uid=MyUserName;pwd=MyPasswd;database=MyDB"/>On Feb 1, 5:20=A0pm, carlos <carlosubu...@.gmail.com> wrote:
> I am having trouble connecting to Sql Server 2005 Express from asp.net
> 2.0 app on Windows Server 2003. I am using Sql Server Authentication,
> and I tried the below article's suggestions a number of times. When I
> login to to the machine, and login, I am able to get authenticated.
> However, when I debug my application, I get the error below. Do I have
> to give the sql server authenticaed account I created certain
> permissions? Whould I set a port, and use the ipaddress rather than
> the server name? Any suggestions would be greatly appreciated.
> http://support.microsoft.com/kb/914277
> My Error:
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: SQL Network Interfaces, error: 26 - Error
> Locating Server/Instance Specified)
> My Connection String:
> =A0<add key=3D"ConnectionString"
> value=3D"server=3DMyServerName;uid=3DMyUserName;pwd=3DMyPasswd;database=3D=MyDB"/>
Update:
I changed the connection string to use the ipaddress, and a port that
I set in the TCPIP settings, and now i'm getting the below message:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: TCP Provider, error: 0 - No connection could
be made because the target machine actively refused it.)
I'm thinking this may be a permission problem'|||Hi Carlos,
By default, SQL Server 2005 Express, Evaluation, and Developer editions
allow local client connections only. Enterprise, Standard, and Workgroup
editions also listen for remote client connections over TCP/IP.
you ned to enable Remote Connections option using
Surface Area Configuration for Services and Connections (Remote Connections)
- Database Engine
You must restart the Database Engine instance's service to apply changes.
Regards,
Amol R. Lembhe
"carlos" wrote:
> On Feb 1, 5:20 pm, carlos <carlosubu...@.gmail.com> wrote:
> > I am having trouble connecting to Sql Server 2005 Express from asp.net
> > 2.0 app on Windows Server 2003. I am using Sql Server Authentication,
> > and I tried the below article's suggestions a number of times. When I
> > login to to the machine, and login, I am able to get authenticated.
> > However, when I debug my application, I get the error below. Do I have
> > to give the sql server authenticaed account I created certain
> > permissions? Whould I set a port, and use the ipaddress rather than
> > the server name? Any suggestions would be greatly appreciated.
> >
> > http://support.microsoft.com/kb/914277
> >
> > My Error:
> >
> > An error has occurred while establishing a connection to the server.
> > When connecting to SQL Server 2005, this failure may be caused by the
> > fact that under the default settings SQL Server does not allow remote
> > connections. (provider: SQL Network Interfaces, error: 26 - Error
> > Locating Server/Instance Specified)
> >
> > My Connection String:
> > <add key="ConnectionString"
> > value="server=MyServerName;uid=MyUserName;pwd=MyPasswd;database=MyDB"/>
> Update:
> I changed the connection string to use the ipaddress, and a port that
> I set in the TCPIP settings, and now i'm getting the below message:
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: TCP Provider, error: 0 - No connection could
> be made because the target machine actively refused it.)
> I'm thinking this may be a permission problem'
>

Error:20533.Unable to Open Database

In my project I have used VB 6 and CR 8. In my machine the application is working fine. When it was loaded in the customer machine with windows 98 OS, when the report is clicked, it shows the error 'Error:20533 Unable to Open Database'. The Back end used is MS Access. Anybody pl. guide me to install my project? What to do and how to do?

Pl. post your reply due to urgency.Case 1)If u r running ur exe at client side u must place ur Database at the location u have given to ur DSN
Case 2)If u have installed ur setup at client side and just want to replace exe then check whethere u r replacing ur exe in the folder that has been installed on m/c|||Tried. But getting the same error.|||Open the Report and Do verify Database and map the columns if any|||Verify database. In my machine it works. I haven't installed the CR in the client machine. HOw to set right this problem. Is it necessary to load the CR in the client side? Pl. help
Meenakshi.R|||Did you use DSN to connect to CR?|||I haven't used any DSN for CR inthe client side. How to create that DSN for CR? pl. explain.|||How do you connect CR to database? Did you use OLE DB?
Create a DSN pointing to that DB and design reports. In the Client system create the same DSN and point it to that DB.

Otherwise refer this
http://www.businessobjects.com/support/default.asp

Error: Server doesnot exist or Access denied

We are host with windows 2003 server and SQL 2000 DB server. Our clients are
trying to connect to their individual databases using SQL webadmin or
Enterprise manager tool and they get the following message:
"SQL server doesnot exist or access denied.
ConnectionOpen(Connect())"
This is the message from SQL enterprise manager. The workstation is XP SP1.
Any suggestions>> Any suggestions
Oh the usual:
1. Check to make sure that they are using the right username/password
combination.
2. Make sure the client is not behind a firewall that prevents comm
over the SQL Server port.
3. Make sure the same applies for the server.
4. Make sure that they are using the right authentication type (sql or
win).
5. Make sure that the server is configured to use the right auth mode.
6. Make sure that the server's host name appears in the list of
available server to connect to (see 2 & 3).
HTH
AM|||Actually we found out that the SQL is not listening on any TCP/IP port but
only listening to named pipes. Any idea of how to make SQL Server listen to
any tcp/ip ports?
"AM" wrote:

> Oh the usual:
> 1. Check to make sure that they are using the right username/password
> combination.
> 2. Make sure the client is not behind a firewall that prevents comm
> over the SQL Server port.
> 3. Make sure the same applies for the server.
> 4. Make sure that they are using the right authentication type (sql or
> win).
> 5. Make sure that the server is configured to use the right auth mode.
> 6. Make sure that the server's host name appears in the list of
> available server to connect to (see 2 & 3).
> HTH
> AM
>|||In Enterprise Manager, right click on the DB, select properties. In
ther dialog box, int he General tab, on the bottom click on Network
configuration. In the dialog box that pops up, in the general tab,
check to see if TCP/IP is listed on the box on the right. If not select
it from the box on the left and click on enable. YOu can edit the
properties to set up the port to listen on.
HTH
AM|||You can use Server Network Utility to set the tcp port for the sql instance.
-oj
"Snehal Rana" <SnehalRana@.discussions.microsoft.com> wrote in message
news:E263310C-BB72-483D-BE16-DA854F38CB40@.microsoft.com...[vbcol=seagreen]
> Actually we found out that the SQL is not listening on any TCP/IP port but
> only listening to named pipes. Any idea of how to make SQL Server listen
> to
> any tcp/ip ports?
>
> "AM" wrote:
>

Error: Server doesnot exist or Access denied

We are host with windows 2003 server and SQL 2000 DB server. Our clients are
trying to connect to their individual databases using SQL webadmin or
Enterprise manager tool and they get the following message:
"SQL server doesnot exist or access denied.
ConnectionOpen(Connect())"
This is the message from SQL enterprise manager. The workstation is XP SP1.
Any suggestions>> Any suggestions
Oh the usual:
1. Check to make sure that they are using the right username/password
combination.
2. Make sure the client is not behind a firewall that prevents comm
over the SQL Server port.
3. Make sure the same applies for the server.
4. Make sure that they are using the right authentication type (sql or
win).
5. Make sure that the server is configured to use the right auth mode.
6. Make sure that the server's host name appears in the list of
available server to connect to (see 2 & 3).
HTH
AM|||Actually we found out that the SQL is not listening on any TCP/IP port but
only listening to named pipes. Any idea of how to make SQL Server listen to
any tcp/ip ports?
"AM" wrote:
> >> Any suggestions
> Oh the usual:
> 1. Check to make sure that they are using the right username/password
> combination.
> 2. Make sure the client is not behind a firewall that prevents comm
> over the SQL Server port.
> 3. Make sure the same applies for the server.
> 4. Make sure that they are using the right authentication type (sql or
> win).
> 5. Make sure that the server is configured to use the right auth mode.
> 6. Make sure that the server's host name appears in the list of
> available server to connect to (see 2 & 3).
> HTH
> AM
>|||In Enterprise Manager, right click on the DB, select properties. In
ther dialog box, int he General tab, on the bottom click on Network
configuration. In the dialog box that pops up, in the general tab,
check to see if TCP/IP is listed on the box on the right. If not select
it from the box on the left and click on enable. YOu can edit the
properties to set up the port to listen on.
HTH
AM|||You can use Server Network Utility to set the tcp port for the sql instance.
--
-oj
"Snehal Rana" <SnehalRana@.discussions.microsoft.com> wrote in message
news:E263310C-BB72-483D-BE16-DA854F38CB40@.microsoft.com...
> Actually we found out that the SQL is not listening on any TCP/IP port but
> only listening to named pipes. Any idea of how to make SQL Server listen
> to
> any tcp/ip ports?
>
> "AM" wrote:
>> >> Any suggestions
>> Oh the usual:
>> 1. Check to make sure that they are using the right username/password
>> combination.
>> 2. Make sure the client is not behind a firewall that prevents comm
>> over the SQL Server port.
>> 3. Make sure the same applies for the server.
>> 4. Make sure that they are using the right authentication type (sql or
>> win).
>> 5. Make sure that the server is configured to use the right auth mode.
>> 6. Make sure that the server's host name appears in the list of
>> available server to connect to (see 2 & 3).
>> HTH
>> AM
>>

Error: Server doesnot exist or Access denied

We are host with windows 2003 server and SQL 2000 DB server. Our clients are
trying to connect to their individual databases using SQL webadmin or
Enterprise manager tool and they get the following message:
"SQL server doesnot exist or access denied.
ConnectionOpen(Connect())"
This is the message from SQL enterprise manager. The workstation is XP SP1.
Any suggestions
>> Any suggestions
Oh the usual:
1. Check to make sure that they are using the right username/password
combination.
2. Make sure the client is not behind a firewall that prevents comm
over the SQL Server port.
3. Make sure the same applies for the server.
4. Make sure that they are using the right authentication type (sql or
win).
5. Make sure that the server is configured to use the right auth mode.
6. Make sure that the server's host name appears in the list of
available server to connect to (see 2 & 3).
HTH
AM
|||Actually we found out that the SQL is not listening on any TCP/IP port but
only listening to named pipes. Any idea of how to make SQL Server listen to
any tcp/ip ports?
"AM" wrote:

> Oh the usual:
> 1. Check to make sure that they are using the right username/password
> combination.
> 2. Make sure the client is not behind a firewall that prevents comm
> over the SQL Server port.
> 3. Make sure the same applies for the server.
> 4. Make sure that they are using the right authentication type (sql or
> win).
> 5. Make sure that the server is configured to use the right auth mode.
> 6. Make sure that the server's host name appears in the list of
> available server to connect to (see 2 & 3).
> HTH
> AM
>
|||In Enterprise Manager, right click on the DB, select properties. In
ther dialog box, int he General tab, on the bottom click on Network
configuration. In the dialog box that pops up, in the general tab,
check to see if TCP/IP is listed on the box on the right. If not select
it from the box on the left and click on enable. YOu can edit the
properties to set up the port to listen on.
HTH
AM
|||You can use Server Network Utility to set the tcp port for the sql instance.
-oj
"Snehal Rana" <SnehalRana@.discussions.microsoft.com> wrote in message
news:E263310C-BB72-483D-BE16-DA854F38CB40@.microsoft.com...[vbcol=seagreen]
> Actually we found out that the SQL is not listening on any TCP/IP port but
> only listening to named pipes. Any idea of how to make SQL Server listen
> to
> any tcp/ip ports?
>
> "AM" wrote: