Tuesday, March 27, 2012
Error encountered when creating a new datasource
I am new with the Reporting services.
When I tried creating a data source with the following connection string
with the following options:
Conenction Type: SQLServer or OLE DB
Connect using: credentials supplied by the user running the report)
Connection String:
Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Initial
Catalog=Northwind;Data Source=venkat-wxp2;Use Procedure for Prepare=1;Auto
Translate=True;Packet Size=4096;Workstation ID=VENKAT-WXP2;Use Encryption for
Data=False;Tag with column collation when possible=False
I get the following error:
The underlying connection was closed: Could not establish trust relationship
with remote server.
I am on a standalone Windows 2003 Server named venkat-wxp2.
Any help will be appreciated. Thanks in advance.
VenkiTry a simple connection string first and see if it works.
Initial Catalog=Northwind;Data Source=venkat-wxp2;
--
| Thread-Topic: Error encountered when creating a new datasource
| thread-index: AcVrkf5jtPegPMTmTqyEkHE51Kcf9A==| X-WBNR-Posting-Host: 24.56.142.17
| From: "=?Utf-8?B?dnZlbms=?=" <vvenk@.discussions.microsoft.com>
| Subject: Error encountered when creating a new datasource
| Date: Tue, 7 Jun 2005 11:52:03 -0700
| Lines: 28
| Message-ID: <577C1F19-4A5B-4E75-B15D-C81CFDD9BD9D@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:45474
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Hello:
|
| I am new with the Reporting services.
|
| When I tried creating a data source with the following connection string
| with the following options:
| Conenction Type: SQLServer or OLE DB
| Connect using: credentials supplied by the user running the report)
| Connection String:
|
| Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Initial
| Catalog=Northwind;Data Source=venkat-wxp2;Use Procedure for
Prepare=1;Auto
| Translate=True;Packet Size=4096;Workstation ID=VENKAT-WXP2;Use Encryption
for
| Data=False;Tag with column collation when possible=False
|
| I get the following error:
|
| The underlying connection was closed: Could not establish trust
relationship
| with remote server.
|
| I am on a standalone Windows 2003 Server named venkat-wxp2.
|
| Any help will be appreciated. Thanks in advance.
|
| Venki
|
|
|
||||Brad:
Yes, I did try the simpler connection string. I encounter the same issue.
Thanks.
venki
""Brad Syputa - MS"" wrote:
> Try a simple connection string first and see if it works.
> Initial Catalog=Northwind;Data Source=venkat-wxp2;
> --
> | Thread-Topic: Error encountered when creating a new datasource
> | thread-index: AcVrkf5jtPegPMTmTqyEkHE51Kcf9A==> | X-WBNR-Posting-Host: 24.56.142.17
> | From: "=?Utf-8?B?dnZlbms=?=" <vvenk@.discussions.microsoft.com>
> | Subject: Error encountered when creating a new datasource
> | Date: Tue, 7 Jun 2005 11:52:03 -0700
> | Lines: 28
> | Message-ID: <577C1F19-4A5B-4E75-B15D-C81CFDD9BD9D@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:45474
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | Hello:
> |
> | I am new with the Reporting services.
> |
> | When I tried creating a data source with the following connection string
> | with the following options:
> | Conenction Type: SQLServer or OLE DB
> | Connect using: credentials supplied by the user running the report)
> | Connection String:
> |
> | Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Initial
> | Catalog=Northwind;Data Source=venkat-wxp2;Use Procedure for
> Prepare=1;Auto
> | Translate=True;Packet Size=4096;Workstation ID=VENKAT-WXP2;Use Encryption
> for
> | Data=False;Tag with column collation when possible=False
> |
> | I get the following error:
> |
> | The underlying connection was closed: Could not establish trust
> relationship
> | with remote server.
> |
> | I am on a standalone Windows 2003 Server named venkat-wxp2.
> |
> | Any help will be appreciated. Thanks in advance.
> |
> | Venki
> |
> |
> |
> |
>|||While I do not know the cause of your error, a good article to read is at :
http://www.awprofessional.com/articles/article.asp?p=357694&rl=1
--
| Thread-Topic: Error encountered when creating a new datasource
| thread-index: AcVrvSNw13tsTe+nTPeEUMl0Hpblcw==| X-WBNR-Posting-Host: 24.56.142.17
| From: "=?Utf-8?B?dnZlbms=?=" <vvenk@.discussions.microsoft.com>
| References: <577C1F19-4A5B-4E75-B15D-C81CFDD9BD9D@.microsoft.com>
<btNl$X6aFHA.2476@.TK2MSFTNGXA01.phx.gbl>
| Subject: RE: Error encountered when creating a new datasource
| Date: Tue, 7 Jun 2005 17:00:53 -0700
| Lines: 71
| Message-ID: <12ECD0E6-E614-4932-96D5-1AEF2B80B125@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:45502
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Brad:
|
| Yes, I did try the simpler connection string. I encounter the same issue.
|
| Thanks.
|
| venki
|
| ""Brad Syputa - MS"" wrote:
|
| > Try a simple connection string first and see if it works.
| >
| > Initial Catalog=Northwind;Data Source=venkat-wxp2;
| > --
| > | Thread-Topic: Error encountered when creating a new datasource
| > | thread-index: AcVrkf5jtPegPMTmTqyEkHE51Kcf9A==| > | X-WBNR-Posting-Host: 24.56.142.17
| > | From: "=?Utf-8?B?dnZlbms=?=" <vvenk@.discussions.microsoft.com>
| > | Subject: Error encountered when creating a new datasource
| > | Date: Tue, 7 Jun 2005 11:52:03 -0700
| > | Lines: 28
| > | Message-ID: <577C1F19-4A5B-4E75-B15D-C81CFDD9BD9D@.microsoft.com>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| > | Newsgroups: microsoft.public.sqlserver.reportingsvcs
| > | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| > | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| > | Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.sqlserver.reportingsvcs:45474
| > | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
| > |
| > | Hello:
| > |
| > | I am new with the Reporting services.
| > |
| > | When I tried creating a data source with the following connection
string
| > | with the following options:
| > | Conenction Type: SQLServer or OLE DB
| > | Connect using: credentials supplied by the user running the report)
| > | Connection String:
| > |
| > | Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Initial
| > | Catalog=Northwind;Data Source=venkat-wxp2;Use Procedure for
| > Prepare=1;Auto
| > | Translate=True;Packet Size=4096;Workstation ID=VENKAT-WXP2;Use
Encryption
| > for
| > | Data=False;Tag with column collation when possible=False
| > |
| > | I get the following error:
| > |
| > | The underlying connection was closed: Could not establish trust
| > relationship
| > | with remote server.
| > |
| > | I am on a standalone Windows 2003 Server named venkat-wxp2.
| > |
| > | Any help will be appreciated. Thanks in advance.
| > |
| > | Venki
| > |
| > |
| > |
| > |
| >
| >
||||Brad:
I just de-installed SQL Server 2000 and installed SQL Server 2005 instead
and I was able to create a datasource.
Thanks.
""Brad Syputa - MS"" wrote:
> While I do not know the cause of your error, a good article to read is at :
> http://www.awprofessional.com/articles/article.asp?p=357694&rl=1
> --
> | Thread-Topic: Error encountered when creating a new datasource
> | thread-index: AcVrvSNw13tsTe+nTPeEUMl0Hpblcw==> | X-WBNR-Posting-Host: 24.56.142.17
> | From: "=?Utf-8?B?dnZlbms=?=" <vvenk@.discussions.microsoft.com>
> | References: <577C1F19-4A5B-4E75-B15D-C81CFDD9BD9D@.microsoft.com>
> <btNl$X6aFHA.2476@.TK2MSFTNGXA01.phx.gbl>
> | Subject: RE: Error encountered when creating a new datasource
> | Date: Tue, 7 Jun 2005 17:00:53 -0700
> | Lines: 71
> | Message-ID: <12ECD0E6-E614-4932-96D5-1AEF2B80B125@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:45502
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | Brad:
> |
> | Yes, I did try the simpler connection string. I encounter the same issue.
> |
> | Thanks.
> |
> | venki
> |
> | ""Brad Syputa - MS"" wrote:
> |
> | > Try a simple connection string first and see if it works.
> | >
> | > Initial Catalog=Northwind;Data Source=venkat-wxp2;
> | > --
> | > | Thread-Topic: Error encountered when creating a new datasource
> | > | thread-index: AcVrkf5jtPegPMTmTqyEkHE51Kcf9A==> | > | X-WBNR-Posting-Host: 24.56.142.17
> | > | From: "=?Utf-8?B?dnZlbms=?=" <vvenk@.discussions.microsoft.com>
> | > | Subject: Error encountered when creating a new datasource
> | > | Date: Tue, 7 Jun 2005 11:52:03 -0700
> | > | Lines: 28
> | > | Message-ID: <577C1F19-4A5B-4E75-B15D-C81CFDD9BD9D@.microsoft.com>
> | > | MIME-Version: 1.0
> | > | Content-Type: text/plain;
> | > | charset="Utf-8"
> | > | Content-Transfer-Encoding: 7bit
> | > | X-Newsreader: Microsoft CDO for Windows 2000
> | > | Content-Class: urn:content-classes:message
> | > | Importance: normal
> | > | Priority: normal
> | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | > | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | > | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | > | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | > | Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.sqlserver.reportingsvcs:45474
> | > | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> | > |
> | > | Hello:
> | > |
> | > | I am new with the Reporting services.
> | > |
> | > | When I tried creating a data source with the following connection
> string
> | > | with the following options:
> | > | Conenction Type: SQLServer or OLE DB
> | > | Connect using: credentials supplied by the user running the report)
> | > | Connection String:
> | > |
> | > | Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Initial
> | > | Catalog=Northwind;Data Source=venkat-wxp2;Use Procedure for
> | > Prepare=1;Auto
> | > | Translate=True;Packet Size=4096;Workstation ID=VENKAT-WXP2;Use
> Encryption
> | > for
> | > | Data=False;Tag with column collation when possible=False
> | > |
> | > | I get the following error:
> | > |
> | > | The underlying connection was closed: Could not establish trust
> | > relationship
> | > | with remote server.
> | > |
> | > | I am on a standalone Windows 2003 Server named venkat-wxp2.
> | > |
> | > | Any help will be appreciated. Thanks in advance.
> | > |
> | > | Venki
> | > |
> | > |
> | > |
> | > |
> | >
> | >
> |
>
error during SQL Server 2005 Express help...
configured.
After completion, the window displays a red x beside Reporting
Services.
On all the other results, you can click and view a log generated
during installation.
Clicking on the "Reporting Services" (that didn't install) does not
display the log file.
Any help is appreciated.
Thanks,
TrintOn Feb 16, 12:11 pm, "trint" <trinity.sm...@.gmail.com> wrote:
> The "Setup Progress" window displays the selected components to be
> configured.
> After completion, the window displays a red x beside Reporting
> Services.
> On all the other results, you can click and view a log generated
> during installation.
> Clicking on the "Reporting Services" (that didn't install) does not
> display the log file.
> Any help is appreciated.
> Thanks,
> Trint
I had this occur in the past, you can try to see if the reason for the
error appeared in the Event Viewer. I would suggest uninstalling SQL
Server 2005 Express and reinstalling it and of course, make sure that
you have all trial versions uninstalled before reinstalling it (where
applicable). Hope this helps.
Regards,
Enrique Martinez
Sr. SQL Server Developer|||On Feb 18, 7:26 pm, "EMartinez" <emartinez...@.gmail.com> wrote:
> On Feb 16, 12:11 pm, "trint" <trinity.sm...@.gmail.com> wrote:
> > The "Setup Progress" window displays the selected components to be
> > configured.
> > After completion, the window displays a red x beside Reporting
> > Services.
> > On all the other results, you can click and view a log generated
> > during installation.
> > Clicking on the "Reporting Services" (that didn't install) does not
> > display the log file.
> > Any help is appreciated.
> > Thanks,
> >Trint
> I had this occur in the past, you can try to see if the reason for the
> error appeared in the Event Viewer. I would suggest uninstalling SQL
> Server 2005 Express and reinstalling it and of course, make sure that
> you have all trial versions uninstalled before reinstalling it (where
> applicable). Hope this helps.
> Regards,
> Enrique Martinez
> Sr. SQL Server Developer
Enrique,
I did that and also on two different machines (same problem).
Thanks,
Trint
Monday, March 26, 2012
Error during installation of reporting services
I've stuck with an error message and I can't sort it out. I am trying to
install a standard reporting service on a server separated from database
server.
Web server (report services): no domain
Databasebase server: a member of a domain.
I can install RS with domain authentication mode but I can't with SQL
authentication such as sa.
Errror message:
login failed for user '(null)'. reason: not associated with a trusted sql
server connection.
Anyone have an workaround for this error?
ThanksI found that using setup /i command lines and I did without any problem.
"Oliver" <dummy@.hotmail.com> wrote in message
news:eRbesy9EFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I've stuck with an error message and I can't sort it out. I am trying to
> install a standard reporting service on a server separated from database
> server.
> Web server (report services): no domain
> Databasebase server: a member of a domain.
> I can install RS with domain authentication mode but I can't with SQL
> authentication such as sa.
> Errror message:
> login failed for user '(null)'. reason: not associated with a trusted sql
> server connection.
> Anyone have an workaround for this error?
> Thanks
>|||Running setup with the /i command line did not have any impact on this issue
for me.
"Oliver" wrote:
> I found that using setup /i command lines and I did without any problem.
> "Oliver" <dummy@.hotmail.com> wrote in message
> news:eRbesy9EFHA.1936@.TK2MSFTNGP14.phx.gbl...
> > Hi,
> >
> > I've stuck with an error message and I can't sort it out. I am trying to
> > install a standard reporting service on a server separated from database
> > server.
> > Web server (report services): no domain
> > Databasebase server: a member of a domain.
> >
> > I can install RS with domain authentication mode but I can't with SQL
> > authentication such as sa.
> >
> > Errror message:
> > login failed for user '(null)'. reason: not associated with a trusted sql
> > server connection.
> >
> > Anyone have an workaround for this error?
> >
> > Thanks
> >
> >
>
>
Error during Export To Excel - Matrix Report
Hi All,
I have created a Report using Sql Server 2005 Reporting Services. It's a matrix report. When I try to download the report to excel, it gives me the message "
Data Regions within table/matrix cells are ignored.
" in the top left hand side header.
Any pointers on how to resolve it.
Thanks,
S Suresh
This is a limitation of the Excel Renderer. It's not so much an error message as just information about why your data is missing. The Renderer cannot render data regions (list, table, matrix, subreport) nested inside other data regions (subreports inside lists are an exception to this rule). Instead of just displaying a blank cell, it puts the message you have seen in.
You will need to redesign your report if Excel is your desired output format for this report.
|||Geoff,
In your last statement in this thread,
"The Renderer cannot render data regions (list, table, matrix, subreport) nested inside other data regions (subreports inside lists are an exception to this rule)".
I dont understang this statement,currently i am facing with this type of issue only. I have a matrix ,in the data cell of the matrix ,i placed a list and placed a subreport inside it(SubReport has only one small table which acceopts a parameter from value in the column header).
Will it work for me as you said some thing "Execption" or Do i need to search for another alternative?
your suggestions are most valuable
Thank you,
Raj Deep.A
Error during Export To Excel - Matrix Report
Hi All,
I have created a Report using Sql Server 2005 Reporting Services. It's a matrix report. When I try to download the report to excel, it gives me the message "
Data Regions within table/matrix cells are ignored.
" in the top left hand side header.
Any pointers on how to resolve it.
Thanks,
S Suresh
This is a limitation of the Excel Renderer. It's not so much an error message as just information about why your data is missing. The Renderer cannot render data regions (list, table, matrix, subreport) nested inside other data regions (subreports inside lists are an exception to this rule). Instead of just displaying a blank cell, it puts the message you have seen in.
You will need to redesign your report if Excel is your desired output format for this report.
|||Geoff,
In your last statement in this thread,
"The Renderer cannot render data regions (list, table, matrix, subreport) nested inside other data regions (subreports inside lists are an exception to this rule)".
I dont understang this statement,currently i am facing with this type of issue only. I have a matrix ,in the data cell of the matrix ,i placed a list and placed a subreport inside it(SubReport has only one small table which acceopts a parameter from value in the column header).
Will it work for me as you said some thing "Execption" or Do i need to search for another alternative?
your suggestions are most valuable
Thank you,
Raj Deep.A
|||i have a matrix report that has 3 column groupings. Daily Date range across the top(Ex. 11/24,11/25, etc). The column groupings are numbers for WeekToDate, MonthToDate,ProjectToDate. So dates go across the top, then subtotals are grouped based up on the above 3 groups. Problem is when it switches from Nov to Dec 12/1 is missing and looks like it is moved to the end of the report right before the ProjectToDate subtotal. This 'problem' happens when exporting from Report Manager. Export from VS is fine.
Wednesday, March 21, 2012
Error Data bases not compatible, Installation Reporting services
I install Report services (standard, developer, enterprise edition) on sql
server 2000 personal edition, and windows 2003 server enterprise, during the
installation, when creating the data base sends the following message of
error "This version of the data base of the Reporting services is not
compatible with the version of SQL server 2000"
all the scene this in Spanish language.
I do not understand because, help me please.
excuse I do not speak ingles, thanksYou are posting the same problem multiple times. The answer will be the
same. Personal edition will not work. See my other post which has links to
the MS website that documents this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Arturo Alegria Palacios" <Arturo Alegria
Palacios@.discussions.microsoft.com> wrote in message
news:89C41CA4-B525-49B2-980D-BB39CDE4E018@.microsoft.com...
> Hi,
> I install Report services (standard, developer, enterprise edition) on sql
> server 2000 personal edition, and windows 2003 server enterprise, during
> the
> installation, when creating the data base sends the following message of
> error "This version of the data base of the Reporting services is not
> compatible with the version of SQL server 2000"
> all the scene this in Spanish language.
> I do not understand because, help me please.
> excuse I do not speak ingles, thanks|||Thanks bruce, I am going to verify the documentation of website, will verify
the scene where this executing itself now
"Bruce L-C [MVP]" wrote:
> You are posting the same problem multiple times. The answer will be the
> same. Personal edition will not work. See my other post which has links to
> the MS website that documents this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Arturo Alegria Palacios" <Arturo Alegria
> Palacios@.discussions.microsoft.com> wrote in message
> news:89C41CA4-B525-49B2-980D-BB39CDE4E018@.microsoft.com...
> > Hi,
> > I install Report services (standard, developer, enterprise edition) on sql
> > server 2000 personal edition, and windows 2003 server enterprise, during
> > the
> > installation, when creating the data base sends the following message of
> > error "This version of the data base of the Reporting services is not
> > compatible with the version of SQL server 2000"
> >
> > all the scene this in Spanish language.
> >
> > I do not understand because, help me please.
> >
> > excuse I do not speak ingles, thanks
>
>
Friday, March 9, 2012
Error connection to SSRS via SSMS; SQL Server 2005
SQL Server Management Studio, however I get an error; "Cannot connect
to <<Server>>". In addition there is an HTTP status 404 error.
I am running this in a VPC with Windows 2003 Standard and SQL Server
Enterprise.
Within the VPC, I can connect to the Report Manager and view my
reports, I can access the report through web services and Visual
Studio and the ReportServer database exists in the SQL Server; I just
cannot connect to SSRS via SSMS.
Any Thoughts?
PaulWhen you connect to Report Manager via MSIE, what is the server name within
the URL?
http://servername/reports
Are you using that same name when you try to connect to SSRS via SSMS? Did
you try localhost?
--
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Paul" <blackwell_paul@.hotmail.com> wrote in message
news:3fbe13c7-b839-45e7-8785-2657f2081c96@.e25g2000prg.googlegroups.com...
>I am trying to connect to SQL Server Reporting Services through the
> SQL Server Management Studio, however I get an error; "Cannot connect
> to <<Server>>". In addition there is an HTTP status 404 error.
> I am running this in a VPC with Windows 2003 Standard and SQL Server
> Enterprise.
> Within the VPC, I can connect to the Report Manager and view my
> reports, I can access the report through web services and Visual
> Studio and the ReportServer database exists in the SQL Server; I just
> cannot connect to SSRS via SSMS.
> Any Thoughts?
> Paul|||On Nov 19, 9:25 am, "Alain Quesnel" <alainsanss...@.logiquel.com>
wrote:
> When you connect to Report Manager via MSIE, what is the server name within
> the URL?http://servername/reports
> Are you using that same name when you try to connect to SSRS via SSMS? Did
> you try localhost?
> --
> Alain Quesnel
> alainsanss...@.logiquel.com
> www.logiquel.com
> "Paul" <blackwell_p...@.hotmail.com> wrote in message
> news:3fbe13c7-b839-45e7-8785-2657f2081c96@.e25g2000prg.googlegroups.com...
>
> >I am trying to connect to SQL Server Reporting Services through the
> > SQL Server Management Studio, however I get an error; "Cannot connect
> > to <<Server>>". In addition there is an HTTP status 404 error.
> > I am running this in a VPC with Windows 2003 Standard and SQL Server
> > Enterprise.
> > Within the VPC, I can connect to the Report Manager and view my
> > reports, I can access the report through web services and Visual
> > Studio and the ReportServer database exists in the SQL Server; I just
> > cannot connect to SSRS via SSMS.
> > Any Thoughts?
> > Paul- Hide quoted text -
> - Show quoted text -
I am using http://labs:81/reports/... I am using W2K3 Standard and
have a second website (not localhost). It uses portal 81. The server
name is LABS. Even when I use LABS:81 in the Connect to Server dialog
box of the SSMS, I get the same error.|||Can you switch to port 80 (momentarily) and try again?
--
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Paul" <blackwell_paul@.hotmail.com> wrote in message
news:32c86d58-1ff2-4b7f-9b36-635bf7868a69@.d4g2000prg.googlegroups.com...
> On Nov 19, 9:25 am, "Alain Quesnel" <alainsanss...@.logiquel.com>
> wrote:
>> When you connect to Report Manager via MSIE, what is the server name
>> within
>> the URL?http://servername/reports
>> Are you using that same name when you try to connect to SSRS via SSMS?
>> Did
>> you try localhost?
>> --
>> Alain Quesnel
>> alainsanss...@.logiquel.com
>> www.logiquel.com
>> "Paul" <blackwell_p...@.hotmail.com> wrote in message
>> news:3fbe13c7-b839-45e7-8785-2657f2081c96@.e25g2000prg.googlegroups.com...
>>
>> >I am trying to connect to SQL Server Reporting Services through the
>> > SQL Server Management Studio, however I get an error; "Cannot connect
>> > to <<Server>>". In addition there is an HTTP status 404 error.
>> > I am running this in a VPC with Windows 2003 Standard and SQL Server
>> > Enterprise.
>> > Within the VPC, I can connect to the Report Manager and view my
>> > reports, I can access the report through web services and Visual
>> > Studio and the ReportServer database exists in the SQL Server; I just
>> > cannot connect to SSRS via SSMS.
>> > Any Thoughts?
>> > Paul- Hide quoted text -
>> - Show quoted text -
> I am using http://labs:81/reports/... I am using W2K3 Standard and
> have a second website (not localhost). It uses portal 81. The server
> name is LABS. Even when I use LABS:81 in the Connect to Server dialog
> box of the SSMS, I get the same error.
>|||On Nov 19, 1:44 pm, "Alain Quesnel" <alainsanss...@.logiquel.com>
wrote:
> Can you switch to port 80 (momentarily) and try again?
> --
> Alain Quesnel
> alainsanss...@.logiquel.com
> www.logiquel.com
> "Paul" <blackwell_p...@.hotmail.com> wrote in message
> news:32c86d58-1ff2-4b7f-9b36-635bf7868a69@.d4g2000prg.googlegroups.com...
>
> > On Nov 19, 9:25 am, "Alain Quesnel" <alainsanss...@.logiquel.com>
> > wrote:
> >> When you connect to Report Manager via MSIE, what is the server name
> >> within
> >> the URL?http://servername/reports
> >> Are you using that same name when you try to connect to SSRS via SSMS?
> >> Did
> >> you try localhost?
> >> --
> >> Alain Quesnel
> >> alainsanss...@.logiquel.com
> >>www.logiquel.com
> >> "Paul" <blackwell_p...@.hotmail.com> wrote in message
> >>news:3fbe13c7-b839-45e7-8785-2657f2081c96@.e25g2000prg.googlegroups.com...
> >> >I am trying to connect to SQL Server Reporting Services through the
> >> > SQL Server Management Studio, however I get an error; "Cannot connect
> >> > to <<Server>>". In addition there is an HTTP status 404 error.
> >> > I am running this in a VPC with Windows 2003 Standard and SQL Server
> >> > Enterprise.
> >> > Within the VPC, I can connect to the Report Manager and view my
> >> > reports, I can access the report through web services and Visual
> >> > Studio and the ReportServer database exists in the SQL Server; I just
> >> > cannot connect to SSRS via SSMS.
> >> > Any Thoughts?
> >> > Paul- Hide quoted text -
> >> - Show quoted text -
> > I am usinghttp://labs:81/reports/... I am using W2K3 Standard and
> > have a second website (not localhost). It uses portal 81. The server
> > name is LABS. Even when I use LABS:81 in the Connect to Server dialog
> > box of the SSMS, I get the same error.- Hide quoted text -
> - Show quoted text -
Problem solved!
The account that ReportServer was running under did not have the
appropriate access. In addition, the url in the config file was
incorrect; Alain, you nailed it or at least would have if I hand not
already discovered it, thanks for your expertise anyways.
Unfortunately both items I noticed early on, but "didn't think" they
were issues. I just wonder if this is the answer to many blogs that I
have seen regarding this, all resulting with no solution.
Wednesday, March 7, 2012
Error connecting to Reporting server
Reporting Services Error
----
An internal error occurred on the report server. See the error log for more
details. (rsInternalError) Get Online Help
Key not valid for use in specified state.
LOG File entry:
System.Runtime.InteropServices.COMException (0x8009000B): Key not valid for
use in specified state.
Any assistance would be apprectiated.
--
JerryDid you just install the report server?
"Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
> Getting the following error after MS Updates
> Reporting Services Error
> ----
> An internal error occurred on the report server. See the error log for
> more
> details. (rsInternalError) Get Online Help
> Key not valid for use in specified state.
> LOG File entry:
> System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> for
> use in specified state.
> Any assistance would be apprectiated.
> --
> Jerry|||No, this had been running successfully for quite awhile, shortly after the
latest MS secuity updates did this happen.
I've checked all of the services and restarted them. I've ran the rsconfig
utility to update the config files, but still the same message.
--
Jerry
"Ben Watts" wrote:
> Did you just install the report server?
> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
> > Getting the following error after MS Updates
> > Reporting Services Error
> > ----
> >
> > An internal error occurred on the report server. See the error log for
> > more
> > details. (rsInternalError) Get Online Help
> > Key not valid for use in specified state.
> >
> > LOG File entry:
> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> > for
> > use in specified state.
> >
> > Any assistance would be apprectiated.
> > --
> > Jerry
>
>|||I found this when I googled your log file entry.
9/20/2005 4:09:21 AM RE: Setup could not initialize the report
server
Hi AJ,
Welcome to use MSDN Managed Newsgroup and thanks so much for your providing
the sufficient information!
From your descriptions, I understood you encoutner the error message "Setup
could not initialize the report server" when initializing the Reporting
Services. If I have misunderstood your concern, please feel free to point
it out.
We could find the following line in the report error logs
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details. --> System.Runtime.InteropServices.COMException (0x8009000B): Key
not valid for use in specified state.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
errorCode, IntPtr errorInfo)
Based on my knowledge, please perform the steps below and let me know
whether it resolves your issue
1. From Explorer, navigate to x:\Documents and Settings\<service
account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20.
2. Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*".
These files represent the Microsoft SQL Server Reporting Services Key
Container.
3. Delete these files.
4. Reinstall Reporting Services.
Thank you for your patience and cooperation. 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.
"Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
news:E944F1D8-2546-4AEB-9665-4E7ED96C6089@.microsoft.com...
> No, this had been running successfully for quite awhile, shortly after the
> latest MS secuity updates did this happen.
> I've checked all of the services and restarted them. I've ran the rsconfig
> utility to update the config files, but still the same message.
> --
> Jerry
>
> "Ben Watts" wrote:
>> Did you just install the report server?
>> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
>> news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
>> > Getting the following error after MS Updates
>> > Reporting Services Error
>> > ----
>> >
>> > An internal error occurred on the report server. See the error log for
>> > more
>> > details. (rsInternalError) Get Online Help
>> > Key not valid for use in specified state.
>> >
>> > LOG File entry:
>> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
>> > for
>> > use in specified state.
>> >
>> > Any assistance would be apprectiated.
>> > --
>> > Jerry
>>|||I deleted that file and everything seems to be up and running.
Thank you,
--
Jerry
"Ben Watts" wrote:
> I found this when I googled your log file entry.
> 9/20/2005 4:09:21 AM RE: Setup could not initialize the report
> server
> Hi AJ,
> Welcome to use MSDN Managed Newsgroup and thanks so much for your providing
> the sufficient information!
> From your descriptions, I understood you encoutner the error message "Setup
> could not initialize the report server" when initializing the Reporting
> Services. If I have misunderstood your concern, please feel free to point
> it out.
> We could find the following line in the report error logs
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for more
> details. --> System.Runtime.InteropServices.COMException (0x8009000B): Key
> not valid for use in specified state.
> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> errorCode, IntPtr errorInfo)
> Based on my knowledge, please perform the steps below and let me know
> whether it resolves your issue
> 1. From Explorer, navigate to x:\Documents and Settings\<service
> account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20.
> 2. Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*".
> These files represent the Microsoft SQL Server Reporting Services Key
> Container.
> 3. Delete these files.
> 4. Reinstall Reporting Services.
> Thank you for your patience and cooperation. 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.
>
> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> news:E944F1D8-2546-4AEB-9665-4E7ED96C6089@.microsoft.com...
> > No, this had been running successfully for quite awhile, shortly after the
> > latest MS secuity updates did this happen.
> >
> > I've checked all of the services and restarted them. I've ran the rsconfig
> > utility to update the config files, but still the same message.
> >
> > --
> > Jerry
> >
> >
> > "Ben Watts" wrote:
> >
> >> Did you just install the report server?
> >> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> >> news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
> >> > Getting the following error after MS Updates
> >> > Reporting Services Error
> >> > ----
> >> >
> >> > An internal error occurred on the report server. See the error log for
> >> > more
> >> > details. (rsInternalError) Get Online Help
> >> > Key not valid for use in specified state.
> >> >
> >> > LOG File entry:
> >> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> >> > for
> >> > use in specified state.
> >> >
> >> > Any assistance would be apprectiated.
> >> > --
> >> > Jerry
> >>
> >>
> >>
>
>|||You say 'you deleted the file and everything seems to be running'.
Does that mean that you did NOT reinstall RS?
Jerry Hodson wrote:
> I deleted that file and everything seems to be up and running.
> Thank you,
> --
> Jerry
>
> "Ben Watts" wrote:
> > I found this when I googled your log file entry.
> >
> > 9/20/2005 4:09:21 AM RE: Setup could not initialize the report
> > server
> > Hi AJ,
> >
> > Welcome to use MSDN Managed Newsgroup and thanks so much for your providing
> >
> > the sufficient information!
> >
> > From your descriptions, I understood you encoutner the error message "Setup
> >
> > could not initialize the report server" when initializing the Reporting
> >
> > Services. If I have misunderstood your concern, please feel free to point
> >
> > it out.
> >
> > We could find the following line in the report error logs
> >
> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> >
> > An internal error occurred on the report server. See the error log for more
> >
> > details. --> System.Runtime.InteropServices.COMException (0x8009000B): Key
> >
> > not valid for use in specified state.
> >
> > at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> >
> > errorCode, IntPtr errorInfo)
> >
> > Based on my knowledge, please perform the steps below and let me know
> >
> > whether it resolves your issue
> >
> > 1. From Explorer, navigate to x:\Documents and Settings\<service
> >
> > account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20.
> >
> > 2. Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*".
> >
> > These files represent the Microsoft SQL Server Reporting Services Key
> >
> > Container.
> >
> > 3. Delete these files.
> >
> > 4. Reinstall Reporting Services.
> >
> > Thank you for your patience and cooperation. 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.
> >
> >
> >
> > "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> > news:E944F1D8-2546-4AEB-9665-4E7ED96C6089@.microsoft.com...
> > > No, this had been running successfully for quite awhile, shortly after the
> > > latest MS secuity updates did this happen.
> > >
> > > I've checked all of the services and restarted them. I've ran the rsconfig
> > > utility to update the config files, but still the same message.
> > >
> > > --
> > > Jerry
> > >
> > >
> > > "Ben Watts" wrote:
> > >
> > >> Did you just install the report server?
> > >> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> > >> news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
> > >> > Getting the following error after MS Updates
> > >> > Reporting Services Error
> > >> > ----
> > >> >
> > >> > An internal error occurred on the report server. See the error log for
> > >> > more
> > >> > details. (rsInternalError) Get Online Help
> > >> > Key not valid for use in specified state.
> > >> >
> > >> > LOG File entry:
> > >> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> > >> > for
> > >> > use in specified state.
> > >> >
> > >> > Any assistance would be apprectiated.
> > >> > --
> > >> > Jerry
> > >>
> > >>
> > >>
> >
> >
> >|||You say 'you deleted the file and everything seems to be running'.
Does that mean that you did NOT reinstall RS?
Jerry Hodson wrote:
> I deleted that file and everything seems to be up and running.
> Thank you,
> --
> Jerry
>
> "Ben Watts" wrote:
> > I found this when I googled your log file entry.
> >
> > 9/20/2005 4:09:21 AM RE: Setup could not initialize the report
> > server
> > Hi AJ,
> >
> > Welcome to use MSDN Managed Newsgroup and thanks so much for your providing
> >
> > the sufficient information!
> >
> > From your descriptions, I understood you encoutner the error message "Setup
> >
> > could not initialize the report server" when initializing the Reporting
> >
> > Services. If I have misunderstood your concern, please feel free to point
> >
> > it out.
> >
> > We could find the following line in the report error logs
> >
> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> >
> > An internal error occurred on the report server. See the error log for more
> >
> > details. --> System.Runtime.InteropServices.COMException (0x8009000B): Key
> >
> > not valid for use in specified state.
> >
> > at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> >
> > errorCode, IntPtr errorInfo)
> >
> > Based on my knowledge, please perform the steps below and let me know
> >
> > whether it resolves your issue
> >
> > 1. From Explorer, navigate to x:\Documents and Settings\<service
> >
> > account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20.
> >
> > 2. Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*".
> >
> > These files represent the Microsoft SQL Server Reporting Services Key
> >
> > Container.
> >
> > 3. Delete these files.
> >
> > 4. Reinstall Reporting Services.
> >
> > Thank you for your patience and cooperation. 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.
> >
> >
> >
> > "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> > news:E944F1D8-2546-4AEB-9665-4E7ED96C6089@.microsoft.com...
> > > No, this had been running successfully for quite awhile, shortly after the
> > > latest MS secuity updates did this happen.
> > >
> > > I've checked all of the services and restarted them. I've ran the rsconfig
> > > utility to update the config files, but still the same message.
> > >
> > > --
> > > Jerry
> > >
> > >
> > > "Ben Watts" wrote:
> > >
> > >> Did you just install the report server?
> > >> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> > >> news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
> > >> > Getting the following error after MS Updates
> > >> > Reporting Services Error
> > >> > ----
> > >> >
> > >> > An internal error occurred on the report server. See the error log for
> > >> > more
> > >> > details. (rsInternalError) Get Online Help
> > >> > Key not valid for use in specified state.
> > >> >
> > >> > LOG File entry:
> > >> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> > >> > for
> > >> > use in specified state.
> > >> >
> > >> > Any assistance would be apprectiated.
> > >> > --
> > >> > Jerry
> > >>
> > >>
> > >>
> >
> >
> >|||Sorry for taking so long in answering, but that is correct, once I deleted
that file RS started working correctly
--
Jerry
"Steve" wrote:
> You say 'you deleted the file and everything seems to be running'.
> Does that mean that you did NOT reinstall RS?
>
> Jerry Hodson wrote:
> > I deleted that file and everything seems to be up and running.
> >
> > Thank you,
> > --
> > Jerry
> >
> >
> > "Ben Watts" wrote:
> >
> > > I found this when I googled your log file entry.
> > >
> > > 9/20/2005 4:09:21 AM RE: Setup could not initialize the report
> > > server
> > > Hi AJ,
> > >
> > > Welcome to use MSDN Managed Newsgroup and thanks so much for your providing
> > >
> > > the sufficient information!
> > >
> > > From your descriptions, I understood you encoutner the error message "Setup
> > >
> > > could not initialize the report server" when initializing the Reporting
> > >
> > > Services. If I have misunderstood your concern, please feel free to point
> > >
> > > it out.
> > >
> > > We could find the following line in the report error logs
> > >
> > > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > >
> > > An internal error occurred on the report server. See the error log for more
> > >
> > > details. --> System.Runtime.InteropServices.COMException (0x8009000B): Key
> > >
> > > not valid for use in specified state.
> > >
> > > at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> > >
> > > errorCode, IntPtr errorInfo)
> > >
> > > Based on my knowledge, please perform the steps below and let me know
> > >
> > > whether it resolves your issue
> > >
> > > 1. From Explorer, navigate to x:\Documents and Settings\<service
> > >
> > > account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20.
> > >
> > > 2. Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*".
> > >
> > > These files represent the Microsoft SQL Server Reporting Services Key
> > >
> > > Container.
> > >
> > > 3. Delete these files.
> > >
> > > 4. Reinstall Reporting Services.
> > >
> > > Thank you for your patience and cooperation. 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.
> > >
> > >
> > >
> > > "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> > > news:E944F1D8-2546-4AEB-9665-4E7ED96C6089@.microsoft.com...
> > > > No, this had been running successfully for quite awhile, shortly after the
> > > > latest MS secuity updates did this happen.
> > > >
> > > > I've checked all of the services and restarted them. I've ran the rsconfig
> > > > utility to update the config files, but still the same message.
> > > >
> > > > --
> > > > Jerry
> > > >
> > > >
> > > > "Ben Watts" wrote:
> > > >
> > > >> Did you just install the report server?
> > > >> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> > > >> news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
> > > >> > Getting the following error after MS Updates
> > > >> > Reporting Services Error
> > > >> > ----
> > > >> >
> > > >> > An internal error occurred on the report server. See the error log for
> > > >> > more
> > > >> > details. (rsInternalError) Get Online Help
> > > >> > Key not valid for use in specified state.
> > > >> >
> > > >> > LOG File entry:
> > > >> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> > > >> > for
> > > >> > use in specified state.
> > > >> >
> > > >> > Any assistance would be apprectiated.
> > > >> > --
> > > >> > Jerry
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >
>
Error connecting to remote connections...
configuration on a handful of servers using the SQL Reporting Services and
the RDLC which is working great. Except this one server has:
"An error has occurred when establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by teh fact that
under the default settings SQL Server does not allow remote connections.
Named Pipes provider, error: 40 - Could not open a connection to the SQL
Server).
I think the IT admin used SQL permissions when he installed. Could that be
the problem?
Thanks in Advance.
ChrisThis link might help,
http://vadivel.blogspot.com/2007/01/error-has-occurred-while-establishing.html.
daw
"Chris Marsh" wrote:
> That's what appears at my client site. I have virtually the exact same
> configuration on a handful of servers using the SQL Reporting Services and
> the RDLC which is working great. Except this one server has:
> "An error has occurred when establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by teh fact that
> under the default settings SQL Server does not allow remote connections.
> Named Pipes provider, error: 40 - Could not open a connection to the SQL
> Server).
> I think the IT admin used SQL permissions when he installed. Could that be
> the problem?
> Thanks in Advance.
> Chris
>
>|||Sorry, I should have specified this earlier but the SQL DB is SQL 2000 not
2005 which is what is strange. Again, works on multiple other configurations
but not this one.
"daw" <daw@.discussions.microsoft.com> wrote in message
news:D05FF90C-2A0D-43B9-83B4-D348859995E9@.microsoft.com...
> This link might help,
> http://vadivel.blogspot.com/2007/01/error-has-occurred-while-establishing.html.
> daw
> "Chris Marsh" wrote:
>> That's what appears at my client site. I have virtually the exact same
>> configuration on a handful of servers using the SQL Reporting Services
>> and
>> the RDLC which is working great. Except this one server has:
>> "An error has occurred when establishing a connection to the server. When
>> connecting to SQL Server 2005, this failure may be caused by teh fact
>> that
>> under the default settings SQL Server does not allow remote connections.
>> Named Pipes provider, error: 40 - Could not open a connection to the SQL
>> Server).
>> I think the IT admin used SQL permissions when he installed. Could that
>> be
>> the problem?
>> Thanks in Advance.
>> Chris
>>
Wednesday, February 15, 2012
Error after install with Remote SQL Server Instance
I've been having a lot of problems with installing Reporting Services on our
webserver. We want the Report Server to be available externally so I've
installed the Report Server and Report Manager on our webserver and the
ReportServer database is located on a separate database server. The install
goes OK and a first test of http://xxx/ReportServer looked fine but when I
try to open Report Manager I get the below error. I've tried various
configurations with the install, so with NT AUTHORITY\SYSTEM as the user that
starts the Report Server service and then with various domain users and sql
logins that all should have access to the database server. Also, if the
service is stopped (it starts OK directly after it is installed) then it
cannot be restarted. In the log is says that it cannot connect to the
database, but there are no errors during the install or in any of the log
files the first time the service starts. If I try to restart the service then
it hangs and usually the server has to be rebooted to stop it.
This is a clean install of Reporting Services, we've never had a previous
version of it on the server. Both the webserver and database server are
Win2000 (sp4) with IIS 5.0 on the webserver. And it is the Standard Edition
of Reporting Services.
So far I have tried the following measures to fix this:
Reinstall ASP .NET 1.1 (v1.1.4322) and have registered it with IIS and
registered aspnet_isapi.dll.
Set file permissions on the winnt\temp directory and the Temporary ASP .NET
Files directory and the C:\Documents and Settings\xxx\ASPNET\Local
Settings\Temp directory. (ASPNET account, SYSTEM acount and even tried giving
Everyone full control)
Checked that all file associations in IIS are correct (aspx files are
associated with the correct version of the .NET framework)
Installing and uninstalling numerous times.
Installing service pack 1 (this fails everytime)
I have not been able to find any post on google with exactly the same error
and symptoms so any help would be much appreciated.
Regards,
Daniel Lee
aspnet_wp!ui!fb4!10/11/2004-16:53:32:: e ERROR: Server was unable to process
request. --> File or assembly name noogu73a.dll, or one of its dependencies,
was not found.
aspnet_wp!ui!fb4!10/11/2004-16:53:32:: e ERROR: HTTP status code --> 500
--Details--
System.Web.Services.Protocols.SoapException: Server was unable to process
request. --> File or assembly name noogu73a.dll, or one of its dependencies,
was not found.
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()
aspnet_wp!ui!fb4!10/11/2004-16:53:42:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)In case anyone else ever gets a simliar error, this seems to have been
something to do with corruption of a windows dll due to a hard disk failure.
However, my bad experience with Reporting Services continues on a new server.
Would find it hard to recommend this product (at least just now) to anyone
who wants to use this in a normal production environment (i.e. separate web
server and database servers), especially if trying to connect to an OLAP cube
and using MDX. I have wasted an unbelieveable amount of time just trying to
get reporting services installed properly. All this is a real pity as I
really like what it can (should) do. Maybe next year with SQL 2005?
error accessing the reports manager in browser
I installed the Reporting Services on Win2000 server (SP4). when I try to
access the reports manager through browser I am getting following error.
The XML file
c:\winnt\microsoft.net\framework\v1.1.4322\Config\machine.config could not
be loaded. Attempted to access an unloaded AppDomain.
Thanks,
Nemani.I installed latest visual studio.net 2003
"Nemani" <mnemani@.che.state.nm.us> wrote in message
news:eOHZoeuWEHA.1164@.tk2msftngp13.phx.gbl...
> Hi,
> I installed the Reporting Services on Win2000 server (SP4). when I try to
> access the reports manager through browser I am getting following error.
> The XML file
> c:\winnt\microsoft.net\framework\v1.1.4322\Config\machine.config could not
> be loaded. Attempted to access an unloaded AppDomain.
> Thanks,
> Nemani.
>
Error Accessing SSRS Web Applications - Service Unavailable/Invalid Version
Server 2000 instance. Neither was installed with Reporting Services. We went
back and installed Reporting Services on the 2005 instance only. Went
through the config tool with no problems and the virtual directories look
fine in IIS.
When we try to hit the Reports web page using IE, we get "Service
Unavailable." The service shows as "Started."
Event viewer shows two errors, which occur every 12 hours. The first says
"The report server database is an invalid version" (Event ID 117) and the
second says "Report Server Windows Service (MSSQLSERVER) cannot connect to
the report server dartabase" (Event ID 107).
The server has 2.0 of the framework intalled and the SSRS web applications
are pointing to ASP 2.0.
I googled around on these messages and the only resolutions I found
suggested that the Reporting Services config tool had not been run. It had
been run, and to play it safe I ran it again. But no luck.
Any suggestions? The server is running Windows Server 2003 SP1 and SQL
Server is version 9.0.3054.
Thanks in advance for any help.On Dec 6, 11:20 am, "CapCity" <sgomori at yahoo dot com> wrote:
> We have an instance of SQLServer2005 on aserverthat also has a SQLServer2000 instance. Neither was installed with Reporting Services. We went
> back and installed Reporting Services on the 2005 instance only. Went
> through the config tool with no problems and the virtual directories look
> fine in IIS.
> When we try to hit the Reports web page using IE, we get "Service
> Unavailable." Theserviceshows as "Started."
> Event viewer shows two errors, which occur every 12 hours. The first says
> "Thereportserverdatabase is an invalid version" (Event ID 117) and the
> second says "ReportServerWindowsService(MSSQLSERVER) cannot connect to
> thereportserverdartabase" (Event ID 107).
> Theserverhas 2.0 of the framework intalled and the SSRS web applications
> are pointing to ASP 2.0.
> I googled around on these messages and the only resolutions I found
> suggested that the Reporting Services config tool hadnotbeen run. It had
> been run, and to play it safe I ran it again. But no luck.
> Any suggestions? TheserverisrunningWindowsServer2003 SP1 and SQLServeris version 9.0.3054.
> Thanks in advance for any help.
The *WINDOWS* Service may not be running.
Start >> Administrative Tools >> Services >> SQL Server Reporting
Services (MSSQLSERVER)
Make sure that is started and working properly.|||"BM" <moore.brent@.gmail.com> wrote in message
news:c25281d0-9f47-41ff-844f-e6317ec42e09@.w40g2000hsb.googlegroups.com...
> On Dec 6, 11:20 am, "CapCity" <sgomori at yahoo dot com> wrote:
>> We have an instance of SQLServer2005 on aserverthat also has a
>> SQLServer2000 instance. Neither was installed with Reporting Services. We
>> went
>> back and installed Reporting Services on the 2005 instance only. Went
>> through the config tool with no problems and the virtual directories look
>> fine in IIS.
>> When we try to hit the Reports web page using IE, we get "Service
>> Unavailable." Theserviceshows as "Started."
>> Event viewer shows two errors, which occur every 12 hours. The first says
>> "Thereportserverdatabase is an invalid version" (Event ID 117) and the
>> second says "ReportServerWindowsService(MSSQLSERVER) cannot connect to
>> thereportserverdartabase" (Event ID 107).
>> Theserverhas 2.0 of the framework intalled and the SSRS web applications
>> are pointing to ASP 2.0.
>> I googled around on these messages and the only resolutions I found
>> suggested that the Reporting Services config tool hadnotbeen run. It had
>> been run, and to play it safe I ran it again. But no luck.
>> Any suggestions? TheserverisrunningWindowsServer2003 SP1 and SQLServeris
>> version 9.0.3054.
>> Thanks in advance for any help.
> The *WINDOWS* Service may not be running.
> Start >> Administrative Tools >> Services >> SQL Server Reporting
> Services (MSSQLSERVER)
> Make sure that is started and working properly.
The service is running. I even stopped it and restarted it, but still get
the same error.
error accessing rs web service
I am having problems accessing reporting services using the report viewer web service from a web application. We are getting the following error.
System.Net.WebException: The request failed with HTTP status 401: Access Denied.
Below is the code. The uncommented code works, but we don't want to hard code a user. The DefaultCredentials are coming up blank. Any suggestions on why this may be or what to do to correct would be appreciated.
<code>
Dim rsAsNew reportserver_dev.ReportingService
Dim itemAs reportserver_dev.CatalogItem
' gets users network creditentials for reporting services
'rs.Credentials = System.Net.CredentialCache.DefaultCredentials
' ***** to do: this is temporary to force authentication
Dim cacheAsNew System.Net.CredentialCache
cache.Add(New Uri(rs.Url), "Negotiate",New System.Net.NetworkCredential("user", "pwd", "domain"))
rs.Credentials = cache
</code>Hi,
In your web.config is set <identity impersonate="true" /> ?
Regards
|||Hello creagan,
Is the reporting service on the same machine or on a remote machine? If the
report server is a remote machine, then using impersonation and CredentialCache.DefaultCredentials
doesn't work because of a one-hop limitation in NTLM authentication.
Authentication, Role-based Security, and SQL Reporting Services
Roadmap to Delegation
HTH,|||
Please try these links
http://support.microsoft.com/?id=306158
http://www.c-sharpcorner.com/UploadFile/chauhan_sonu57/ProgrammaticImpersonation02022006080545AM/ProgrammaticImpersonation.aspx?ArticleID=3aa21cd6-b867-4306-96ed-de0ba5930fa1
http://blogs.msdn.com/bimusings/archive/2005/11/18/494436.aspx
Regards,
Jimmy