Showing posts with label deploying. Show all posts
Showing posts with label deploying. Show all posts

Monday, March 26, 2012

Problems deploying website

My ASP.NET application runs fine within the VS2005 IDE; but, when I deploy to my local machine to try to run it under IIS and calling it up in a browser, I'm getting the following exception:

Exception Details: System.Data.SqlClient.SqlException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[SqlException (0x80131904): Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +734979
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1838
System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +33
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +359
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +121
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +137
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +83
System.Web.UI.WebControls.SqlDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments) +1770
System.Web.UI.WebControls.ListControl.OnDataBinding(EventArgs e) +92
System.Web.UI.WebControls.ListControl.PerformSelect() +31
System.Web.UI.WebControls.BaseDataBoundControl.DataBind() +70
System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound() +82
System.Web.UI.WebControls.ListControl.OnPreRender(EventArgs e) +26
System.Web.UI.Control.PreRenderRecursiveInternal() +77
System.Web.UI.Control.PreRenderRecursiveInternal() +161
System.Web.UI.Control.PreRenderRecursiveInternal() +161
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1360

I'm a novice at this and really need some help. What stupid newbie mistake am I making here? Thanks in advance for any guidance/assistance rendered.

When you deplyed the app you left the same SQL trusted connection, and most probably there is no local SQL server running in the same machine. Make sure to change the SQL string to the IP, username and password of the database and will work really well

Al

|||

I remember I got this problem too when I did my first try. It seems that your are using trusted connection, you need assign the domain user in your database with appropriate access right. Or you can create a database user in the database to use standard User/password connection method in your database is in mixed mode..

You can easily find the syntax for the connection string. As to create user in database, you need to create a login account under Security on the Server, in the database, you assign this user for access under database security tab.

Limno

Problems deploying to a remote Report Server(2005)

I developed a simple report using the AdventureWorks sample database on a XP
Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine in
preview mode. When I attempt to deploy it to a remote Report Server (June
2005 CTP) I get the following error:
"A connection could not be made to the report server
http://<servername>/reportserver.
Additional information: The version of the report server web service
definition (WSDL) is either not valid or unrecognized. The server is not a
compatible version (Microsoft.reportingServices.Designer)"
Any help/responses is greatly appreciated.
PS: The same report developed and deployed on the Report Server works fine!!
--
Thank you,
AshokThe version of RS with Beta2 is not the same as the June CTP. My guess is
that this version mismatch is causing the problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
news:B2A96F52-5CD0-4A83-A0B3-FFEB5EBF5D21@.microsoft.com...
>I developed a simple report using the AdventureWorks sample database on a
>XP
> Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine in
> preview mode. When I attempt to deploy it to a remote Report Server (June
> 2005 CTP) I get the following error:
> "A connection could not be made to the report server
> http://<servername>/reportserver.
> Additional information: The version of the report server web service
> definition (WSDL) is either not valid or unrecognized. The server is not
> a
> compatible version (Microsoft.reportingServices.Designer)"
> Any help/responses is greatly appreciated.
> PS: The same report developed and deployed on the Report Server works
> fine!!
> --
> Thank you,
> Ashok|||THanks Bruce. I appreciate your prompt reponse.
I suspected that it would be an incompatibility issue. Would you recommend
that I uninstall the Beta and install the june CTP on the client?
--
Thank you,
Ashok G
"Bruce L-C [MVP]" wrote:
> The version of RS with Beta2 is not the same as the June CTP. My guess is
> that this version mismatch is causing the problem.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
> news:B2A96F52-5CD0-4A83-A0B3-FFEB5EBF5D21@.microsoft.com...
> >I developed a simple report using the AdventureWorks sample database on a
> >XP
> > Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine in
> > preview mode. When I attempt to deploy it to a remote Report Server (June
> > 2005 CTP) I get the following error:
> >
> > "A connection could not be made to the report server
> > http://<servername>/reportserver.
> >
> > Additional information: The version of the report server web service
> > definition (WSDL) is either not valid or unrecognized. The server is not
> > a
> > compatible version (Microsoft.reportingServices.Designer)"
> >
> > Any help/responses is greatly appreciated.
> >
> > PS: The same report developed and deployed on the Report Server works
> > fine!!
> > --
> > Thank you,
> > Ashok
>
>|||Yes. If you have the report available from RS 2000 then I suggest
uninstalling the beta and install the CTP and then bring over the reports
from RS 2000.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
news:72F122A5-2CD7-4EC1-A776-F8536B016EAB@.microsoft.com...
> THanks Bruce. I appreciate your prompt reponse.
> I suspected that it would be an incompatibility issue. Would you
> recommend
> that I uninstall the Beta and install the june CTP on the client?
> --
> Thank you,
> Ashok G
>
> "Bruce L-C [MVP]" wrote:
>> The version of RS with Beta2 is not the same as the June CTP. My guess is
>> that this version mismatch is causing the problem.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
>> news:B2A96F52-5CD0-4A83-A0B3-FFEB5EBF5D21@.microsoft.com...
>> >I developed a simple report using the AdventureWorks sample database on
>> >a
>> >XP
>> > Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine
>> > in
>> > preview mode. When I attempt to deploy it to a remote Report Server
>> > (June
>> > 2005 CTP) I get the following error:
>> >
>> > "A connection could not be made to the report server
>> > http://<servername>/reportserver.
>> >
>> > Additional information: The version of the report server web service
>> > definition (WSDL) is either not valid or unrecognized. The server is
>> > not
>> > a
>> > compatible version (Microsoft.reportingServices.Designer)"
>> >
>> > Any help/responses is greatly appreciated.
>> >
>> > PS: The same report developed and deployed on the Report Server works
>> > fine!!
>> > --
>> > Thank you,
>> > Ashok
>>|||I moved to another RS 2005 server that has CTP June and it worked! I was
able to publish and execute the report.
Thanks once again.
--
Thank you,
Ashok G
"Bruce L-C [MVP]" wrote:
> Yes. If you have the report available from RS 2000 then I suggest
> uninstalling the beta and install the CTP and then bring over the reports
> from RS 2000.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
> news:72F122A5-2CD7-4EC1-A776-F8536B016EAB@.microsoft.com...
> > THanks Bruce. I appreciate your prompt reponse.
> > I suspected that it would be an incompatibility issue. Would you
> > recommend
> > that I uninstall the Beta and install the june CTP on the client?
> >
> > --
> > Thank you,
> > Ashok G
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> The version of RS with Beta2 is not the same as the June CTP. My guess is
> >> that this version mismatch is causing the problem.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
> >> news:B2A96F52-5CD0-4A83-A0B3-FFEB5EBF5D21@.microsoft.com...
> >> >I developed a simple report using the AdventureWorks sample database on
> >> >a
> >> >XP
> >> > Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine
> >> > in
> >> > preview mode. When I attempt to deploy it to a remote Report Server
> >> > (June
> >> > 2005 CTP) I get the following error:
> >> >
> >> > "A connection could not be made to the report server
> >> > http://<servername>/reportserver.
> >> >
> >> > Additional information: The version of the report server web service
> >> > definition (WSDL) is either not valid or unrecognized. The server is
> >> > not
> >> > a
> >> > compatible version (Microsoft.reportingServices.Designer)"
> >> >
> >> > Any help/responses is greatly appreciated.
> >> >
> >> > PS: The same report developed and deployed on the Report Server works
> >> > fine!!
> >> > --
> >> > Thank you,
> >> > Ashok
> >>
> >>
> >>
>
>

Problems deploying to a different server

I've been playing with Reporting Services on my computer and got it working fine. I can view the reports on my localhost with no problems. However, when I change the TargetServerURL in the report properties to the server that I want the report to go on (yes, the target server has SQL Reporting Services installed on it), I get the following error message:

Server was unable to process request. > Method ReportingService.SetExecutionOptions can not be reflected. > Unknown error - HRESULT 0x80131047

Anyone have any idea of what's going wrong here? Thanks for any help.

Just to add: I do have rights to the server I'm trying to publish to. This is assuming that SQL Reporting Services is distributing the reports under my username. It could well be that it's trying to use the generic ASPNET user that Visual Studio has a habit of using for its web publishing. Anyone know for sure?Problem solved. Silly mistake on my part. I deployed Framework 2.0 beta to that server and by default it set the folders used by Report Services to use ASP.NET 2.0 which my Visual Studio 2003 didn't like, so I set the folders to use ASP.NET 1.1 and all is good.sql

Problems deploying SSRS2005 security extension example

Dear All,
I've been trying to deploy the security extension example from
Microsoft for SSRS2005 and have encountered the following errors when
I access the reports virtual directory (although the pages/
UILogin.aspx page comes up)
- Report Server Web App reports that the report server is not
responding.
- Report Server reports that it cannot access (access denied)
accessing the dll file.
Can anyone help me with this?
Config File Segments:
________________________________________________________________________
rsmreportserver.config (file exists when I do a dir command on the
path in the type attribute)
<Security>
<Extension Name="Forms"
Type="Microsoft.Samples.ReportingServices.CustomSecurity.Authorization,
Microsoft.Samples.ReportingServices.CustomSecurity" >
<Configuration>
<AdminConfiguration>
<UserName>prime</UserName>
</AdminConfiguration>
</Configuration>
</Extension>
</Security>
<Authentication>
<Extension Name="Forms"
Type="Microsoft.Samples.ReportingServices.CustomSecurity.AuthenticationExtension,
Microsoft.Samples.ReportingServices.CustomSecurity" />
</Authentication>
_____________________________________________________________________
rssrvpolicy.config
<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="$CodeGen$/*"
/>
</CodeGroup>
<CodeGroup
class="UnionCodeGroup"
version="1"
Name="SecurityExtensionCodeGroup"
Description="Code group for the sample security extension"
PermissionSetName="FullTrust">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\bin
\Microsoft.Samples.ReportingServices.CustomSecurity.dll"
/>
</CodeGroup>
_____________________________________________________________________
rsswebapplication.config (note xxx=actual hostname)
<UI>
<CustomAuthenticationUI>
<loginUrl>/Pages/UILogon.aspx</loginUrl>
<UseSSL>False</UseSSL>
</CustomAuthenticationUI>
<ReportServerUrl>http://xxx/reportserver</ReportServerUrl>
</UI>
_____________________________________________________________________
_____________________________________________________________________
ReportServer WebApp Log
w3wp!library!1!12/3/2007-18:28:01:: i INFO: Initializing WatsonFlags
to default value of '1064' because it was not specified in
Configuration file.
w3wp!library!1!12/3/2007-18:28:01:: i INFO: Initializing
WatsonDumpOnExceptions to default value of
'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException'
because it was not specified in Configuration file.
w3wp!library!1!12/3/2007-18:28:01:: i INFO: Initializing
WatsonDumpExcludeIfContainsExceptions to default value of
'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException'
because it was not specified in Configuration file.
w3wp!library!1!12/3/2007-18:28:01:: i INFO: Initializing
SecureConnectionLevel to default value of '1' because it was not
specified in Configuration file.
w3wp!library!1!12/3/2007-18:28:01:: i INFO: Initializing
DisplayErrorLink to 'True' as specified in Configuration file.
w3wp!library!1!12/3/2007-18:28:01:: i INFO: Initializing
WebServiceUseFileShareStorage to default value of 'False' because it
was not specified in Configuration file.
w3wp!ui!1!12/3/2007-18:28:05:: e ERROR: The report server is not
responding. Verify that the report server is running and can be
accessed from this computer.
w3wp!ui!1!12/3/2007-18:28:06:: e ERROR: HTTP status code --> 500
--Details--
Microsoft.ReportingServices.UI.Global+RSWebServiceWrapper
+CantCommunicateWithReportServerException: The report server is not
responding. Verify that the report server is running and can be
accessed from this computer.
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!12/3/2007-18:28:07:: 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)
_________________________________________________________________________
ReportServer Log
w3wp!runningjobs!7!12/3/2007-18:28:04:: i INFO: Database Cleanup (Web
Service) timer enabled: Next Event: 600 seconds. Cycle: 600 seconds
w3wp!runningjobs!7!12/3/2007-18:28:04:: i INFO: Running Requests
Scavenger timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
w3wp!runningjobs!7!12/3/2007-18:28:04:: i INFO: Running Requests DB
timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
w3wp!runningjobs!7!12/3/2007-18:28:04:: i INFO: Memory stats update
timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
w3wp!extensionfactory!7!12/03/2007-18:28:04:: e ERROR: Exception
caught instantiating Forms report server extension:
System.IO.FileLoadException: Could not load file or assembly
'Microsoft.Samples.ReportingServices.CustomSecurity' or one of its
dependencies. Access is denied.
File name: 'Microsoft.Samples.ReportingServices.CustomSecurity'
at System.Reflection.Assembly.nLoad(AssemblyName fileName, String
codeBase, Evidence assemblySecurity, Assembly locationHint,
StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean
forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName
assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark,
Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(String assemblyString,
Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean
forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
at
Microsoft.ReportingServices.Diagnostics.ExtensionClassFactory.LoadAssembly(String
name)
at
Microsoft.ReportingServices.Diagnostics.ExtensionClassFactory.CreateExtensionObject(Extension
extConfig)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM
\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind
failure logging.
To turn this feature off, remove the registry value [HKLM\Software
\Microsoft\Fusion!EnableLog].
.
w3wp!library!7!12/03/2007-18:28:04:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. See the
report server log files for more information., Could not load
Authentication extension;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. See the
report server log files for more information.
w3wp!library!7!12/03/2007-18:28:06:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. See the
report server log files for more information., Could not load
Authentication extension;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. See the
report server log files for more information.
w3wp!library!8!12/3/2007-18:29:04:: i INFO: Catalog SQL Server Edition
= Developer
w3wp!library!7!12/3/2007-18:38:04:: i INFO: Cleaned 0 batch records, 0
policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0
running jobs, 0 persisted streams
__________________________________________________________
Thanks, HerbHi
Ive got the same problem, but only on windows server 2003 using ssl. It runs
fine untill i install a ssl certificate, then it gives me a similar error. *.
ReportingServices.CustomSecurity* file not found.
If i reverse the ssl certificate, the problem remains. The same stuff works
fine on win xp with ssl though, and on win server 2003 without ssl. How did
you resolve this?
thanks
Leon
url:http://www.ureader.com/msg/115713209.aspx

Wednesday, March 7, 2012

Problem with XMLNS version(while deploying report)

Our Report has xmlns=http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition.xsd

but the server for deploying our report has different namespace.....http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition.xsd.

Is there any way we can deploy reports with new namespace to the server?

Please guide us what we need to do to fix this problem. ?

ALL Reporting server experts....Kindly...Please look into this issue

You can deploy those reports to the older server version. You will need to remove any of the new 2005 features in the RDL to make it conform to the older definition and change the name space.

Or, you can upgrade to RS 2005.