install Reporting service problem on SQL 2005 Express advanced Help please

Hi All,
I try to install reporting services with a french version of SQL 2005
Express Advanced on W2003 std SP1
Install of SQL2005 OK
When setup programm reach reporting service installation, i get an error
message( in french) :
"Le programme d'installation de SQL Server n'a pas pu récupérer le nom du
certificat SSL"
in English from my own translation : "SQL server installation program has
not been able to find SSL certificate"
This stop installation
detail of error give :
Linkid 20476
Nom du produit Microsoft sql Server
Version du Produit 9.00.2047.00
Source du mesage setup.rll
ID du message 29561
evtType
sqlca\sqlrsguica.cpp@.CheckRSSetupRequirements@.CheckRSSetupRequirements@.x7379
I try to install anyway reporting services via RSConfigTool
Install seems ok . Reporting services start ok
but http://mydomain/reports/Pages/folder.aspx give : Red cross Error
and message : "The request failed with HTTP status 400: Bad Request."
That we can find in C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
Services\LogFiles:
----
w3wp!ui!1!17/02/2007-12:02:13:: e ERROR: The request failed with HTTP status
400: Bad Request.
w3wp!ui!1!17/02/2007-12:02:13:: e ERROR: HTTP status code --> 500
--Details--
System.Net.WebException: The request failed with HTTP status 400: Bad
Request.
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at
Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String
methodname)
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
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.Page.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
w3wp!ui!1!17/02/2007-12:02:13:: 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)
-----
Any idea '
MERCI beaucoup
Philippe
C.I.A ITI work around by desintalling IIS et re_install.
In fact i had installed a certificate via selfssl prior install reporting
services, as i have no option to remove this cerificate, the only way i
found, was to uninstall IIS
Philippe
"Philippe" <ph.boussaroque@.Espace-NTIC.com> a écrit dans le message de news:
ecmCyToUHHA.1364@.TK2MSFTNGP06.phx.gbl...
> Hi All,
> I try to install reporting services with a french version of SQL 2005
> Express Advanced on W2003 std SP1
> Install of SQL2005 OK
> When setup programm reach reporting service installation, i get an error
> message( in french) :
> "Le programme d'installation de SQL Server n'a pas pu récupérer le nom du
> certificat SSL"
> in English from my own translation : "SQL server installation program has
> not been able to find SSL certificate"
> This stop installation
> detail of error give :
> Linkid 20476
> Nom du produit Microsoft sql Server
> Version du Produit 9.00.2047.00
> Source du mesage setup.rll
> ID du message 29561
> evtType
> sqlca\sqlrsguica.cpp@.CheckRSSetupRequirements@.CheckRSSetupRequirements@.x7379
> I try to install anyway reporting services via RSConfigTool
> Install seems ok . Reporting services start ok
> but http://mydomain/reports/Pages/folder.aspx give : Red cross Error
> and message : "The request failed with HTTP status 400: Bad Request."
> That we can find in C:\Program Files\Microsoft SQL
> Server\MSSQL.2\Reporting Services\LogFiles:
> ----
> w3wp!ui!1!17/02/2007-12:02:13:: e ERROR: The request failed with HTTP
> status 400: Bad Request.
> w3wp!ui!1!17/02/2007-12:02:13:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The request failed with HTTP status 400: Bad
> Request.
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
> at
> Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String
> methodname)
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
> 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.Page.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
> w3wp!ui!1!17/02/2007-12:02:13:: 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)
> -----
> Any idea '
> MERCI beaucoup
> Philippe
> C.I.A IT
>
>

Install question

I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
seemed to install fine. However, I wasn't prompted for licensing info (per
processor or per
seat) as SQL2000 does. Did I miss an option somewhere? The licensetype is
now disabled and numlicenses is now null.
Also unlike the SQL2000 install, I didn't see where you have the option to
put the database files (for master, msdb) should you not want them under
C:\program files.
Thanks for any help.
Ron
>I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
> seemed to install fine. However, I wasn't prompted for licensing info
> (per
> processor or per
> seat) as SQL2000 does. Did I miss an option somewhere? The licensetype
> is
> now disabled and numlicenses is now null.
Sounds like you installed an MSDN version, in which case, licensing is
disabled. MSDN versions are for testing and development, and processor/CAL
licensing becomes irrelevant. You should not be running the MSDN version of
SQL Server on a machine where licensing is a concern.

> Also unlike the SQL2000 install, I didn't see where you have the option to
> put the database files (for master, msdb) should you not want them under
> C:\program files.
That option is there, it's just not front and center... it's in one of the
options tabs where you breakdown all of the installable features.
A
|||I really don't see any indication that it's an MSDN version. The CDs show:
On left hand size -
English
Microsoft SQL Server 2005
Standard Edition
(32 Bit)
(Disc 1 of 2)
On right hand size-
December 2005
Servers
Servers
Application
It also reads Microsoft Licensing in several places. No mention of MSDN.
"Aaron Bertrand [SQL Server MVP]" wrote:

> Sounds like you installed an MSDN version, in which case, licensing is
> disabled. MSDN versions are for testing and development, and processor/CAL
> licensing becomes irrelevant. You should not be running the MSDN version of
> SQL Server on a machine where licensing is a concern.
>
> That option is there, it's just not front and center... it's in one of the
> options tabs where you breakdown all of the installable features.
> A
>
>
|||>I really don't see any indication that it's an MSDN version. The CDs show:
> On left hand size -
> English
> Microsoft SQL Server 2005
> Standard Edition
> (32 Bit)
> (Disc 1 of 2)
> On right hand size-
> December 2005
> Servers
> Servers
> Application
> It also reads Microsoft Licensing in several places. No mention of MSDN.
Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
Distribution" anywhere on the disc?
There are a few obscure cases where licensing becomes disabled, but 99% of
the time it's because it's an intentionall crippled edition.
A
|||Yes, it does show "Not for OEM or retail distribution" in the smaller print.
Should I be using another version?
"Aaron Bertrand [SQL Server MVP]" wrote:

> Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
> Distribution" anywhere on the disc?
> There are a few obscure cases where licensing becomes disabled, but 99% of
> the time it's because it's an intentionall crippled edition.
> A
>
>
|||> Yes, it does show "Not for OEM or retail distribution" in the smaller
> print.
> Should I be using another version?
I am not sure what you are using it for, if you require licensing, what your
compliance status is, whether it's personal or company, etc. If you are
using this for production then yes you should have official licenses I am
sure.
|||I'm told we have Volume Licensing and the CDs were not MSDN. I uninstalled
sql2005 and downloaded the SQL2005 standard edition via the MVLS website. I
installed that version and still no prompt for licensing (asking for per
processor or per seat).
The licensetype is disabled and numlicenses is null.
As this will eventually be a production server so I'm concerned that all
will be well. Since I'm convinced we are properly licensed, should I be
concerned as to the values in the server property setting?
Thanks again.
Ron
"Aaron Bertrand [SQL Server MVP]" wrote:

> I am not sure what you are using it for, if you require licensing, what your
> compliance status is, whether it's personal or company, etc. If you are
> using this for production then yes you should have official licenses I am
> sure.
>
>
|||SQL Server 2005 no longer tracks license information. The thinking at the
time this decision was made was that since license restrictions never were
enforced, eliminating the license information would reduce the number of
support calls generated when someone entered the wrong data or wanted to
switch license types. The license information columns weren't removed from
the system tables to keep from breaking applications that depend on them -
that's the normal deprecation policy - so they are still there but contain
no useful information. Now SQL works like most other MS server products -
the license is only a paper document that you need to have if you get
audited.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:734EF6A3-B060-452B-B505-6DBE4C601BA6@.microsoft.com...[vbcol=seagreen]
> I'm told we have Volume Licensing and the CDs were not MSDN. I
> uninstalled
> sql2005 and downloaded the SQL2005 standard edition via the MVLS website.
> I
> installed that version and still no prompt for licensing (asking for per
> processor or per seat).
> The licensetype is disabled and numlicenses is null.
> As this will eventually be a production server so I'm concerned that all
> will be well. Since I'm convinced we are properly licensed, should I be
> concerned as to the values in the server property setting?
> Thanks again.
> Ron
> "Aaron Bertrand [SQL Server MVP]" wrote:

Install question

I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
seemed to install fine. However, I wasn't prompted for licensing info (per
processor or per
seat) as SQL2000 does. Did I miss an option somewhere? The licensetype is
now disabled and numlicenses is now null.
Also unlike the SQL2000 install, I didn't see where you have the option to
put the database files (for master, msdb) should you not want them under
C:\program files.
Thanks for any help.
Ron>I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
> seemed to install fine. However, I wasn't prompted for licensing info
> (per
> processor or per
> seat) as SQL2000 does. Did I miss an option somewhere? The licensetype
> is
> now disabled and numlicenses is now null.
Sounds like you installed an MSDN version, in which case, licensing is
disabled. MSDN versions are for testing and development, and processor/CAL
licensing becomes irrelevant. You should not be running the MSDN version of
SQL Server on a machine where licensing is a concern.

> Also unlike the SQL2000 install, I didn't see where you have the option to
> put the database files (for master, msdb) should you not want them under
> C:\program files.
That option is there, it's just not front and center... it's in one of the
options tabs where you breakdown all of the installable features.
A|||I really don't see any indication that it's an MSDN version. The CDs show:
On left hand size -
English
Microsoft SQL Server 2005
Standard Edition
(32 Bit)
(Disc 1 of 2)
On right hand size-
December 2005
Servers
Servers
Application
It also reads Microsoft Licensing in several places. No mention of MSDN.
"Aaron Bertrand [SQL Server MVP]" wrote:

> Sounds like you installed an MSDN version, in which case, licensing is
> disabled. MSDN versions are for testing and development, and processor/CA
L
> licensing becomes irrelevant. You should not be running the MSDN version
of
> SQL Server on a machine where licensing is a concern.
>
> That option is there, it's just not front and center... it's in one of the
> options tabs where you breakdown all of the installable features.
> A
>
>|||>I really don't see any indication that it's an MSDN version. The CDs show:
> On left hand size -
> English
> Microsoft SQL Server 2005
> Standard Edition
> (32 Bit)
> (Disc 1 of 2)
> On right hand size-
> December 2005
> Servers
> Servers
> Application
> It also reads Microsoft Licensing in several places. No mention of MSDN.
Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
Distribution" anywhere on the disc?
There are a few obscure cases where licensing becomes disabled, but 99% of
the time it's because it's an intentionall crippled edition.
A|||Yes, it does show "Not for OEM or retail distribution" in the smaller print.
Should I be using another version?
"Aaron Bertrand [SQL Server MVP]" wrote:

> Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
> Distribution" anywhere on the disc?
> There are a few obscure cases where licensing becomes disabled, but 99% of
> the time it's because it's an intentionall crippled edition.
> A
>
>|||> Yes, it does show "Not for OEM or retail distribution" in the smaller
> print.
> Should I be using another version?
I am not sure what you are using it for, if you require licensing, what your
compliance status is, whether it's personal or company, etc. If you are
using this for production then yes you should have official licenses I am
sure.|||I'm told we have Volume Licensing and the CDs were not MSDN. I uninstalled
sql2005 and downloaded the SQL2005 standard edition via the MVLS website. I
installed that version and still no prompt for licensing (asking for per
processor or per seat).
The licensetype is disabled and numlicenses is null.
As this will eventually be a production server so I'm concerned that all
will be well. Since I'm convinced we are properly licensed, should I be
concerned as to the values in the server property setting?
Thanks again.
Ron
"Aaron Bertrand [SQL Server MVP]" wrote:

> I am not sure what you are using it for, if you require licensing, what yo
ur
> compliance status is, whether it's personal or company, etc. If you are
> using this for production then yes you should have official licenses I am
> sure.
>
>|||SQL Server 2005 no longer tracks license information. The thinking at the
time this decision was made was that since license restrictions never were
enforced, eliminating the license information would reduce the number of
support calls generated when someone entered the wrong data or wanted to
switch license types. The license information columns weren't removed from
the system tables to keep from breaking applications that depend on them -
that's the normal deprecation policy - so they are still there but contain
no useful information. Now SQL works like most other MS server products -
the license is only a paper document that you need to have if you get
audited.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:734EF6A3-B060-452B-B505-6DBE4C601BA6@.microsoft.com...[vbcol=seagreen]
> I'm told we have Volume Licensing and the CDs were not MSDN. I
> uninstalled
> sql2005 and downloaded the SQL2005 standard edition via the MVLS website.
> I
> installed that version and still no prompt for licensing (asking for per
> processor or per seat).
> The licensetype is disabled and numlicenses is null.
> As this will eventually be a production server so I'm concerned that all
> will be well. Since I'm convinced we are properly licensed, should I be
> concerned as to the values in the server property setting?
> Thanks again.
> Ron
> "Aaron Bertrand [SQL Server MVP]" wrote:
>

Install Client Management Tool in WinXP Professional with SQL2005 CTP

SQL server 2005 was installed successfully with SQL2005 CTP CD(Enterprise edition). However, I tried to install Client Management Tool in my WinXP Professional desktop, it stated that incompatibility of OS. Does it mean that I can only install client management tool in WinXP profession with CTP for other editions except enterprise one? Thanks in advance.

Yep, you hit a bug. We've fixed this. The work around is to pull down one of the other Editions.

Dan

Inserting Records via Stored Procedure

I am trying to insert a record in a SQL2005 Express database. I can use the sp fine and it works inside of the database, but when I try to launch it via ASP.NET it fails...

here is the code. I realize it is not complete, but the only required field is defined via hard code. The error I am getting states it cannot find "sp_InserOrder"

===

ProtectedSub Button1_Click(ByVal senderAsObject,ByVal eAs System.EventArgs)Handles Button1.Click

Dim connAs SqlConnection =Nothing

Dim transAs SqlTransaction =Nothing

Dim cmdAs SqlCommand

conn =New SqlConnection(ConfigurationManager.ConnectionStrings("PartsConnectionString").ConnectionString)

conn.Open()

trans = conn.BeginTransaction

cmd =New SqlCommand()

cmd.Connection = conn

cmd.Transaction = trans

cmd.CommandText ="usp_InserOrder"

cmd.CommandType = Data.CommandType.StoredProcedure

cmd.Parameters.Add("@.MaterialID", Data.SqlDbType.Int)

cmd.Parameters.Add("@.OpenItem", Data.SqlDbType.Bit)

cmd.Parameters("@.MaterialID").Value = 3

cmd.ExecuteNonQuery()

trans.Commit()

=====

I get an error stating cannot find stored procedure. I added the Network Service account full access to the Web Site Directory, which is currently running locally on Windows XP Pro SP2.

Please help, I am a newb and lost...as you can tell from my code...

Are you absolutely sure that your stored procedure is called usp_InserOrder. It would make more sense if it was called usp_InsertOrder.|||It is called that. That is what I was thinking at firs, but I checked the database and that is what I named it.|||

I ran it inside of SQL 2005 here is the output...

(0 row(s) returned)

@.RETURN_VALUE = 0

Finished running [dbo].[InserOrder].

|||You code should read -cmd.CommandText ="InserOrder" as that is what it is called in the report you posted above.