Rdl files on SourceSafe

I can't get my rdl files off source safe into my solution. Error "The host
name in the certificate is invalid or does not match."Hi Cadel,
Happy New Year!
Based on my experience, error message "The host name in the certificate is
invalid or does not match" usually suggests some redirection logic in your
application for incoming requests. For example, the request to
http://localhost would redirect to another machine using https://. The URL
being redirected to did not match the URL in the SSL Certificate resulting
in the message. The problem is that once you add the redirection logic,
you will not be able to open the project to disable it.
You should disable the redirection or add logic to not redirect if the
request is from http://localhost or from any of the above pages. You could
also add an <appSettings> section to the web.config. Then in your code
check the app setting and perform the redirection based on this value.
This will allow you to enable/disable the redirection by changing the
web.config. Here is a link to the <appSettings> information:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/ht
ml/gngrfappsettingselement.asp
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.|||I only have a Solution file. I created a new solution in VB 2003 and I'm
trying to Add project from Source Control.
It seems my reporting service reports are stuck in source safe.
I'm able to add other projects in, but when I try to add my reports folder
it errors, "The source control server folder you selected contains no Visual
Studio .NET solution or project file. Please select a different server
folder."
So, then I select my Solution file and that's when I get the error, "The
host name in the certificate is invalid or does not match."
How do I add my rdl files from Source safe to my new solution file?
"Michael Cheng [MSFT]" wrote:
> Hi Cadel,
> Happy New Year!
> Based on my experience, error message "The host name in the certificate is
> invalid or does not match" usually suggests some redirection logic in your
> application for incoming requests. For example, the request to
> http://localhost would redirect to another machine using https://. The URL
> being redirected to did not match the URL in the SSL Certificate resulting
> in the message. The problem is that once you add the redirection logic,
> you will not be able to open the project to disable it.
> You should disable the redirection or add logic to not redirect if the
> request is from http://localhost or from any of the above pages. You could
> also add an <appSettings> section to the web.config. Then in your code
> check the app setting and perform the redirection based on this value.
> This will allow you to enable/disable the redirection by changing the
> web.config. Here is a link to the <appSettings> information:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/ht
> ml/gngrfappsettingselement.asp
>
> 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.
>|||Can you access Source Safe through its own UI instead of through Visual
Studio? If so, do a Get Latest on the Source Safe folder that contains
your *.rdl files. Then check if that folder contains a *.rptproj file.
Sounds like it probably doesn't. However, you should be able to
create a new one by right clicking your solution in Visual Studio's
Solution Explorer and choosing Add | New Project. After adding the
project, you should be able to right-click it add choose Add | Existing
Item to add each *.rdl to the project. Then right-click again on the
project and choose Add Project to Source Control.
Hope this helps.
PS - Judging from his answer, I don't think Mr.Cheng understood your
question.|||Thanks that worked for the rdl files, but my rds files come up with an error
when I try "Add existing item", the error is "Deserialization failed: There
is an error in XML document (4,4)."
"Lee" wrote:
> Can you access Source Safe through its own UI instead of through Visual
> Studio? If so, do a Get Latest on the Source Safe folder that contains
> your *.rdl files. Then check if that folder contains a *.rptproj file.
> Sounds like it probably doesn't. However, you should be able to
> create a new one by right clicking your solution in Visual Studio's
> Solution Explorer and choosing Add | New Project. After adding the
> project, you should be able to right-click it add choose Add | Existing
> Item to add each *.rdl to the project. Then right-click again on the
> project and choose Add Project to Source Control.
> Hope this helps.
> PS - Judging from his answer, I don't think Mr.Cheng understood your
> question.
>|||There are other threads on this forum for "deserialization failed" and
some of the responses (some from MSFT folks) seem to suggest that the
report designer sometimes creates invalid XML (which is what the RDS
files contain). Can you post the contents of one of the RDS files that
produces the error? Preferably the one that gave you the message you
posted earlier...I would guess that (4,4) is a line number and position
reference and that may help us find the problem.|||<?xml version="1.0" encoding="utf-8"?>
<RptDataSource xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="">http://www.w3.org/2001/XMLSchema-instance">
<Name>Claims</Name>
<DataSourceID>a4687848-e640-49e1-b479-
É¥962314bea</DataSourceID>
<ConnectionProperties>
<Extension>SQL</Extension>
<ConnectString>data source=db;initial catalog=Claims</ConnectString>
</ConnectionProperties>
</RptDataSource>
"Lee" wrote:
> There are other threads on this forum for "deserialization failed" and
> some of the responses (some from MSFT folks) seem to suggest that the
> report designer sometimes creates invalid XML (which is what the RDS
> files contain). Can you post the contents of one of the RDS files that
> produces the error? Preferably the one that gave you the message you
> posted earlier...I would guess that (4,4) is a line number and position
> reference and that may help us find the problem.
>|||Looks like you've got a corrupted GUID between your <DataSourceID> and
</DataSourceID> tags. The portion to the right of the 4th hyphen
should be a string of 12 characters made up of any combination of 0
through 9 and/or a through e (case-insensitive). Instead, it looks
like some non-printing characters got in there somehow (as evidenced by
the little square immediately after the 4th hyphen). This GUID was
probably produced by Visual Studio when you defined the data source
(i.e., the .rds). It's anybody's guess as to how it got corrupted.
Anyway, all you care about is fixing it...you could try to replace the
entire GUID (i.e., everything between the <DataSourceID> and
</DataSourceID> tags) with a new GUID you generate yourself (choose
Tools | Create GUID in Visual Studio), but the safer approach may be to
delete the data source (i.e., the .rds) and recreate it (with the same
name, etc., so your reports will still work).|||Hello Cadel,
I just wanted to check back with you on the status of this issue. Please
don't hesitate to contact us if you have any further questions or concerns.
Thanks very much, and have a great weekend!
Hope this helps!
Sincerely,
Dana Brash
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/common/international.aspx.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Rdl files on SourceSafe
>thread-index: AcYVLugG5aBk+6DmRSKkEhRPzSx0NQ==>X-WBNR-Posting-Host: 204.87.106.66
>From: =?Utf-8?B?TWlrZSBM?= <Cadel@.nospam.nospam>
>References: <9369838B-3C59-4BAD-AB21-90F42C375AC7@.microsoft.com>
<szZS6QaEGHA.2660@.TK2MSFTNGXA02.phx.gbl>
<B592D9E9-8504-4634-B688-230942D12718@.microsoft.com>
<1136487927.680465.74720@.z14g2000cwz.googlegroups.com>
<F018555D-9444-4F85-9E35-4E29573C51ED@.microsoft.com>
<1136584470.444321.281380@.f14g2000cwb.googlegroups.com>
>Subject: Re: Rdl files on SourceSafe
>Date: Mon, 9 Jan 2006 07:11:03 -0800
>Lines: 23
>Message-ID: <F36CF917-EFCE-4E0D-8D79-22CCDBEDF5D6@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>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: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:66418
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
><?xml version="1.0" encoding="utf-8"?>
><RptDataSource xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>xmlns:xsi="">http://www.w3.org/2001/XMLSchema-instance">
> <Name>Claims</Name>
> <DataSourceID>a4687848-e640-49e1-b479-
>É¥962314bea</DataSourceID>
> <ConnectionProperties>
> <Extension>SQL</Extension>
> <ConnectString>data source=db;initial catalog=Claims</ConnectString>
> </ConnectionProperties>
></RptDataSource>
>"Lee" wrote:
>> There are other threads on this forum for "deserialization failed" and
>> some of the responses (some from MSFT folks) seem to suggest that the
>> report designer sometimes creates invalid XML (which is what the RDS
>> files contain). Can you post the contents of one of the RDS files that
>> produces the error? Preferably the one that gave you the message you
>> posted earlier...I would guess that (4,4) is a line number and position
>> reference and that may help us find the problem.
>>
>|||Hope what helps?|||Hi Cadel,
You can try to add it manually to VSS.
1. Open VSS Explorer, navigate to the project folder.
2. Click the add file button on the Toolbar and add it.
Kevin Yu
======="This posting is provided "AS IS" with no warranties, and confers no
rights."|||That worked.
Thank you.
"Lee" wrote:
> Looks like you've got a corrupted GUID between your <DataSourceID> and
> </DataSourceID> tags. The portion to the right of the 4th hyphen
> should be a string of 12 characters made up of any combination of 0
> through 9 and/or a through e (case-insensitive). Instead, it looks
> like some non-printing characters got in there somehow (as evidenced by
> the little square immediately after the 4th hyphen). This GUID was
> probably produced by Visual Studio when you defined the data source
> (i.e., the .rds). It's anybody's guess as to how it got corrupted.
> Anyway, all you care about is fixing it...you could try to replace the
> entire GUID (i.e., everything between the <DataSourceID> and
> </DataSourceID> tags) with a new GUID you generate yourself (choose
> Tools | Create GUID in Visual Studio), but the safer approach may be to
> delete the data source (i.e., the .rds) and recreate it (with the same
> name, etc., so your reports will still work).
>