Showing posts with label moving. Show all posts
Showing posts with label moving. Show all posts

Tuesday, March 6, 2012

64-bit SQL Server 2005 Cluster: slow remote desktop

Hi,
We are moving from SQL Server 2000 to SQL Server 2005. Wondering if you
have the same problem or can share some of your experience to solve some
issue.
We have brand new clustered database servers which have Quad Duo CPUs
and 8GB memory each running SQL Server 2005 64bit Enterprise edition
with SP1 applied and on Win2K3 server x64 Enterprise edition. Only
database engine component are installed for now.
We have some strange behaviors from time to time that :
When we have some query running from some local PC Management Studio,
the remote desktop control is either takes a long time to connect or
very slow to react the requests. When it happened, sometime we can not
connect to the database server from Management Studio with the
connection timeout which was OK couple minutes ago. Interestingly at
those moments, the query is still running , no process blocking found,
very light CPU usage and low disk I/O detected from the monitoring tool
and it looks like the SQL server is not busy at all. No 3rd
party/identifiable process can be found running on the database server
also, the 'system idle process' is the main one with CPU count. And
overall the query just take very long than expected to finish. We could
have very normal days for a while and randomly we will encountered the
symptom above. Each time query we ran is different. Some are light and
some are heavy. The query we recently ran is to create index on many big
partitioned tables.
Thanks in advance.Hi,
Thanks for your post!
From your description, I understand that:
You installed SQL Server 2005 64bit as clustered servers. The Windows
Server 2003 was also 64bit.
When you executed the query in SQL Server Management Studio locally, the
remote desktop need a long time to connect the server and had very slow
responses for requests.
At that time, extra connections to the SQL Server were also slow and even
failed. The CPU use ratio and disk I/O level were low then.
This happened once a while. The latest query was to create index on many
large partitioned tables.
If I have misunderstood, please let me know.
To narrow down this issue, I appreciate you send me the performance report
files of SQL Server Profiler and Performance Monitor when the issue is
happening again.
Also, I appreciate you could tell me more about the query when this issue
happened:
What's kind of the query?
Does a simple query will cause that problem?
When this issue happened, what were recorded in the SQL error logs and
system event logs?
If you have any other concerns, please feel free to let me know. It's my
pleasure to be of assistance.
+++++++++++++++++++++++++++
Charles Wang
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.
=====================================================Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others:
https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||American are in vacation "Independency Day".
Charles|||Hi ,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
+++++++++++++++++++++++++++
Charles Wang
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.

64-bit SQL Server 2005 Cluster: slow remote desktop

Hi,
We are moving from SQL Server 2000 to SQL Server 2005. Wondering if you
have the same problem or can share some of your experience to solve some
issue.
We have brand new clustered database servers which have Quad Duo CPUs
and 8GB memory each running SQL Server 2005 64bit Enterprise edition
with SP1 applied and on Win2K3 server x64 Enterprise edition. Only
database engine component are installed for now.
We have some strange behaviors from time to time that :
When we have some query running from some local PC Management Studio,
the remote desktop control is either takes a long time to connect or
very slow to react the requests. When it happened, sometime we can not
connect to the database server from Management Studio with the
connection timeout which was OK couple minutes ago. Interestingly at
those moments, the query is still running , no process blocking found,
very light CPU usage and low disk I/O detected from the monitoring tool
and it looks like the SQL server is not busy at all. No 3rd
party/identifiable process can be found running on the database server
also, the 'system idle process' is the main one with CPU count. And
overall the query just take very long than expected to finish. We could
have very normal days for a while and randomly we will encountered the
symptom above. Each time query we ran is different. Some are light and
some are heavy. The query we recently ran is to create index on many big
partitioned tables.
Thanks in advance.Hi,
Thanks for your post!
From your description, I understand that:
You installed SQL Server 2005 64bit as clustered servers. The Windows
Server 2003 was also 64bit.
When you executed the query in SQL Server Management Studio locally, the
remote desktop need a long time to connect the server and had very slow
responses for requests.
At that time, extra connections to the SQL Server were also slow and even
failed. The CPU use ratio and disk I/O level were low then.
This happened once a while. The latest query was to create index on many
large partitioned tables.
If I have misunderstood, please let me know.
To narrow down this issue, I appreciate you send me the performance report
files of SQL Server Profiler and Performance Monitor when the issue is
happening again.
Also, I appreciate you could tell me more about the query when this issue
happened:
What's kind of the query?
Does a simple query will cause that problem?
When this issue happened, what were recorded in the SQL error logs and
system event logs?
If you have any other concerns, please feel free to let me know. It's my
pleasure to be of assistance.
+++++++++++++++++++++++++++
Charles Wang
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.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others:
https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/defaul...rnational.aspx.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi,
Thanks for your post!
From your description, I understand that:
You installed SQL Server 2005 64bit as clustered servers. The Windows
Server 2003 was also 64bit.
When you executed the query in SQL Server Management Studio locally, the
remote desktop need a long time to connect the server and had very slow
responses for requests.
At that time, extra connections to the SQL Server were also slow and even
failed. The CPU use ratio and disk I/O level were low then.
This happened once a while. The latest query was to create index on many
large partitioned tables.
If I have misunderstood, please let me know.
To narrow down this issue, I appreciate you send me the performance report
files of SQL Server Profiler and Performance Monitor when the issue is
happening again.
Also, I appreciate you could tell me more about the query when this issue
happened:
What's kind of the query?
Does a simple query will cause that problem?
When this issue happened, what were recorded in the SQL error logs and
system event logs?
If you have any other concerns, please feel free to let me know. It's my
pleasure to be of assistance.
+++++++++++++++++++++++++++
Charles Wang
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.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others:
https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/defaul...rnational.aspx.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||American are in vacation "Independency Day".
Charles|||Hi ,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
+++++++++++++++++++++++++++
Charles Wang
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.

Monday, February 13, 2012

403 Error

I've been tasked with moving several reports from a pre-production
environment to production. Sounded easy enough for me; except they left out
that the production environment has some SSRS issues. I've been working
through these and have resolved most of them. The remaining one is very
perplexing, and I can't seem to pinpoint the root cause of the error message.
The management console works just fine, and I'm also able to deploy existing
reports to the new server, however, SSRS is not able to render any reports.
I constantly receive a 403 Forbidden error. Both systems are using Windows
Server 2003 and SQL Server 2005, although they are different service pack
versions. I have duplicated all security permissions from the pre-production
box to the production one, to no avail. The Event Viewer has finally logged
an error message, but it's all Greek to me. The error is listed below.
If anyone could provide some insight, I would be very gratefull.
TIA,
Chris
Error Message:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 7/10/2007 4:45:29 PM
Event time (UTC): 7/10/2007 11:45:29 PM
Event ID: 9a1bce04b5cb4a40bb2a25d886773a0e
Event sequence: 191
Event occurrence: 4
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/root/Reports-1-128285789610527498
Trust level: RosettaMgr
Application Virtual Path: /Reports
Application Path: C:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportManager\
Machine name: *****
Process information:
Process ID: 4020
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: WebException
Exception message: The remote server returned an error: (403) Forbidden.
Request information:
Request URL:
http://***/Reports/Reserved.ReportViewerWebControl.axd?OpType=StyleSheet&Version=2005.090.3042.00
Request path: /Reports/Reserved.ReportViewerWebControl.axd
User host address:
User:
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: True
Stack trace: at
Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean
isAbortable, String url, Stream outputStream, String& mimeType, String&
fileNameExtension)
at Microsoft.Reporting.WebForms.ServerReport.GetStyleSheet(String
styleSheetName)
at
Microsoft.Reporting.WebForms.ReportServerStyleSheetOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response)
at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext
context)
at
System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)
Custom event details:
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.On Jul 10, 8:14 pm, Christopher Robin
<ChristopherRo...@.discussions.microsoft.com> wrote:
> I've been tasked with moving several reports from a pre-production
> environment to production. Sounded easy enough for me; except they left out
> that the production environment has some SSRS issues. I've been working
> through these and have resolved most of them. The remaining one is very
> perplexing, and I can't seem to pinpoint the root cause of the error message.
> The management console works just fine, and I'm also able to deploy existing
> reports to the new server, however, SSRS is not able to render any reports.
> I constantly receive a 403 Forbidden error. Both systems are using Windows
> Server 2003 and SQL Server 2005, although they are different service pack
> versions. I have duplicated all security permissions from the pre-production
> box to the production one, to no avail. The Event Viewer has finally logged
> an error message, but it's all Greek to me. The error is listed below.
> If anyone could provide some insight, I would be very gratefull.
> TIA,
> Chris
> Error Message:
> Event code: 3005
> Event message: An unhandled exception has occurred.
> Event time: 7/10/2007 4:45:29 PM
> Event time (UTC): 7/10/2007 11:45:29 PM
> Event ID: 9a1bce04b5cb4a40bb2a25d886773a0e
> Event sequence: 191
> Event occurrence: 4
> Event detail code: 0
> Application information:
> Application domain: /LM/W3SVC/1/root/Reports-1-128285789610527498
> Trust level: RosettaMgr
> Application Virtual Path: /Reports
> Application Path: C:\Program Files\Microsoft SQL
> Server\MSSQL.3\Reporting Services\ReportManager\
> Machine name: *****
> Process information:
> Process ID: 4020
> Process name: w3wp.exe
> Account name: NT AUTHORITY\NETWORK SERVICE
> Exception information:
> Exception type: WebException
> Exception message: The remote server returned an error: (403) Forbidden.
> Request information:
> Request URL:
> http://***/Reports/Reserved.ReportViewerWebControl.axd?OpType=StyleSheet&Version=2005.090.3042.00
> Request path: /Reports/Reserved.ReportViewerWebControl.axd
> User host address:
> User:
> Is authenticated: True
> Authentication Type: Negotiate
> Thread account name: NT AUTHORITY\NETWORK SERVICE
> Thread information:
> Thread ID: 1
> Thread account name: NT AUTHORITY\NETWORK SERVICE
> Is impersonating: True
> Stack trace: at
> Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean
> isAbortable, String url, Stream outputStream, String& mimeType, String&
> fileNameExtension)
> at Microsoft.Reporting.WebForms.ServerReport.GetStyleSheet(String
> styleSheetName)
> at
> Microsoft.Reporting.WebForms.ReportServerStyleSheetOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response)
> at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext
> context)
> at
> System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
> at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
> completedSynchronously)
> Custom event details:
> For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.
You may want to recreate the website under a different name/virtual
directory. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||"EMartinez" wrote:
> On Jul 10, 8:14 pm, Christopher Robin
> <ChristopherRo...@.discussions.microsoft.com> wrote:
> > I've been tasked with moving several reports from a pre-production
> > environment to production. Sounded easy enough for me; except they left out
> > that the production environment has some SSRS issues. I've been working
> > through these and have resolved most of them. The remaining one is very
> > perplexing, and I can't seem to pinpoint the root cause of the error message.
> > The management console works just fine, and I'm also able to deploy existing
> > reports to the new server, however, SSRS is not able to render any reports.
> > I constantly receive a 403 Forbidden error. Both systems are using Windows
> > Server 2003 and SQL Server 2005, although they are different service pack
> > versions. I have duplicated all security permissions from the pre-production
> > box to the production one, to no avail. The Event Viewer has finally logged
> > an error message, but it's all Greek to me. The error is listed below.
> >
> > If anyone could provide some insight, I would be very gratefull.
> >
> > TIA,
> > Chris
> >
> > Error Message:
> >
> > Event code: 3005
> > Event message: An unhandled exception has occurred.
> > Event time: 7/10/2007 4:45:29 PM
> > Event time (UTC): 7/10/2007 11:45:29 PM
> > Event ID: 9a1bce04b5cb4a40bb2a25d886773a0e
> > Event sequence: 191
> > Event occurrence: 4
> > Event detail code: 0
> >
> > Application information:
> > Application domain: /LM/W3SVC/1/root/Reports-1-128285789610527498
> > Trust level: RosettaMgr
> > Application Virtual Path: /Reports
> > Application Path: C:\Program Files\Microsoft SQL
> > Server\MSSQL.3\Reporting Services\ReportManager\
> > Machine name: *****
> >
> > Process information:
> > Process ID: 4020
> > Process name: w3wp.exe
> > Account name: NT AUTHORITY\NETWORK SERVICE
> >
> > Exception information:
> > Exception type: WebException
> > Exception message: The remote server returned an error: (403) Forbidden.
> >
> > Request information:
> > Request URL:
> > http://***/Reports/Reserved.ReportViewerWebControl.axd?OpType=StyleSheet&Version=2005.090.3042.00
> > Request path: /Reports/Reserved.ReportViewerWebControl.axd
> > User host address:
> > User:
> > Is authenticated: True
> > Authentication Type: Negotiate
> > Thread account name: NT AUTHORITY\NETWORK SERVICE
> >
> > Thread information:
> > Thread ID: 1
> > Thread account name: NT AUTHORITY\NETWORK SERVICE
> > Is impersonating: True
> > Stack trace: at
> > Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean
> > isAbortable, String url, Stream outputStream, String& mimeType, String&
> > fileNameExtension)
> > at Microsoft.Reporting.WebForms.ServerReport.GetStyleSheet(String
> > styleSheetName)
> > at
> > Microsoft.Reporting.WebForms.ReportServerStyleSheetOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response)
> > at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext
> > context)
> > at
> > System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
> > at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
> > completedSynchronously)
> >
> > Custom event details:
> >
> > For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.
>
> You may want to recreate the website under a different name/virtual
> directory. Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>
Hi Enrique,
I don't fully understand, what happened, but your suggestion worked
beautifully. Reporting Services is now showing the report I deployed, and
I'm not the only one that can access it.
Thanks for the help.
Chris|||On Jul 11, 12:52 pm, Christopher Robin
<ChristopherRo...@.discussions.microsoft.com> wrote:
> "EMartinez" wrote:
> > On Jul 10, 8:14 pm, Christopher Robin
> > <ChristopherRo...@.discussions.microsoft.com> wrote:
> > > I've been tasked with moving several reports from a pre-production
> > > environment to production. Sounded easy enough for me; except they left out
> > > that the production environment has some SSRS issues. I've been working
> > > through these and have resolved most of them. The remaining one is very
> > > perplexing, and I can't seem to pinpoint the root cause of the error message.
> > > The management console works just fine, and I'm also able to deploy existing
> > > reports to the new server, however, SSRS is not able to render any reports.
> > > I constantly receive a 403 Forbidden error. Both systems are using Windows
> > > Server 2003 and SQL Server 2005, although they are different service pack
> > > versions. I have duplicated all security permissions from the pre-production
> > > box to the production one, to no avail. The Event Viewer has finally logged
> > > an error message, but it's all Greek to me. The error is listed below.
> > > If anyone could provide some insight, I would be very gratefull.
> > > TIA,
> > > Chris
> > > Error Message:
> > > Event code: 3005
> > > Event message: An unhandled exception has occurred.
> > > Event time: 7/10/2007 4:45:29 PM
> > > Event time (UTC): 7/10/2007 11:45:29 PM
> > > Event ID: 9a1bce04b5cb4a40bb2a25d886773a0e
> > > Event sequence: 191
> > > Event occurrence: 4
> > > Event detail code: 0
> > > Application information:
> > > Application domain: /LM/W3SVC/1/root/Reports-1-128285789610527498
> > > Trust level: RosettaMgr
> > > Application Virtual Path: /Reports
> > > Application Path: C:\Program Files\Microsoft SQL
> > > Server\MSSQL.3\Reporting Services\ReportManager\
> > > Machine name: *****
> > > Process information:
> > > Process ID: 4020
> > > Process name: w3wp.exe
> > > Account name: NT AUTHORITY\NETWORK SERVICE
> > > Exception information:
> > > Exception type: WebException
> > > Exception message: The remote server returned an error: (403) Forbidden.
> > > Request information:
> > > Request URL:
> > > http://***/Reports/Reserved.ReportViewerWebControl.axd?OpType=StyleSheet&Version=2005.090.3042.00
> > > Request path: /Reports/Reserved.ReportViewerWebControl.axd
> > > User host address:
> > > User:
> > > Is authenticated: True
> > > Authentication Type: Negotiate
> > > Thread account name: NT AUTHORITY\NETWORK SERVICE
> > > Thread information:
> > > Thread ID: 1
> > > Thread account name: NT AUTHORITY\NETWORK SERVICE
> > > Is impersonating: True
> > > Stack trace: at
> > > Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean
> > > isAbortable, String url, Stream outputStream, String& mimeType, String&
> > > fileNameExtension)
> > > at Microsoft.Reporting.WebForms.ServerReport.GetStyleSheet(String
> > > styleSheetName)
> > > at
> > > Microsoft.Reporting.WebForms.ReportServerStyleSheetOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response)
> > > at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext
> > > context)
> > > at
> > > System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
> > > at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
> > > completedSynchronously)
> > > Custom event details:
> > > For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.
> > You may want to recreate the website under a different name/virtual
> > directory. Hope this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
> Hi Enrique,
> I don't fully understand, what happened, but your suggestion worked
> beautifully. Reporting Services is now showing the report I deployed, and
> I'm not the only one that can access it.
> Thanks for the help.
> Chris
You're welcome. Glad I could be of assistance.
Regards,
Enrique Martinez
Sr. Software Consultant