.sdf deployment problem VS2005

I have .sdf and .xds objects in my project for a PocketPC 2003 device. When I debug all of the CF2.0, SQL, and .SDF files are downloaded to the device. However, when I install via the application.cab file, the .sdf, .xds, and CF files do not show up on the device.

What am I missing here?

First ensure that your SDF has Build Action set to 'Content' and Copy to Output Directory = True in your project. When you then create a Smart Device Setup Project in VS2005 to create the CAB file for deployment, you need to include the project output AND the content files from your project in the setup project.

Darren

|||

After installing the CF, SQL and application cabs the .sdf file is in the correct folder. However, I am unable to open the .sdf via the application or SQLce Query Analyzer. I get the following message:

Error:0x80004005 E_FAIL

Native Error: (25039)

Description : Access to the database file is not allowe, {,,,File name,,]

Interface defining error: IID_IDBInitialize

Param. 0:0

Param. 1:0

Param. 2:0

Param. 3 \Program Files\Myapplication folder\myapplication.sdf

Param. 4:

Param.

I am still missing something. What?

|||I think I found the problem(s). A) On the device I removed SQLClient2.0. B) In VS I rebuilt .sdf and .xsd. Now it works. I think the .sdf that I replace in VS was based on CF1.0|||

cool. thanks for posting your solution.

-Darren

.Net Deployment ....

Hi everybody,

I want install the project in client side .. In installation time i want to access the my server .. How i can make the setup file to access the internet.. please help me.....

Thanks & Regards,

S.Sajan

Not only is that NOT a good idea, many users will have firewalls that may keep your installation from accessing the internet.

See my post to your previous question for information about remote and unattended installations.

.Net App Deployment Scenario: Privileges for Non-Admin Users

My VB.net application manipulates data in a local SQL Express database. When the app is installed, the database does not exist, but it cannot be created at run-time by anyone other than a user with administrator privileges. In addition, the application shares the data stored in SQL with a critical 3rd party component that can only reach the database via named DSN (also not existing prior to installation).

I see my primary SQL security options as being:

(1) Use SQL or Mixed Mode authentication with an admin-level username/password combination, or

(2) Create a db user/group with admin-level privileges and grant membership to all NT authenticated users

Secondary problem: Creating the DSN.

Does it make sense to create a Custom Action (.dll) that is called at the end of the installation process in order to create the database, the user security context and the named DSN?

Am I overlooking some built-in functionality provided by Visual Studio 2005 that will accompish some or all of this for me? I am aware that customizing the 'silent' installation of SQL Express to use a different authentication mode requires manifest tweaking -- I just don't know anything about setting up the appropriate security for this situation. Would you put the db and role creation stuff in a SQL script and execute it post-install?

Thanks in advance for any insight you can provide.

-T

UPDATE

I plan to modify the SQL Express installation to use mixed-mode authentication, then execute code at the tail end of my app install to (a) create the database, (b) create a dbo-level user (and pwd) for the database, and (c) create my DSN (via SQLConfigDataSource API call).

Feel free to respond if you think/know that there is a better solution.

-T

.Net App Deployment Scenario: Privileges for Non-Admin Users

My VB.net application manipulates data in a local SQL Express database. When the app is installed, the database does not exist, but it cannot be created at run-time by anyone other than a user with administrator privileges. In addition, the application shares the data stored in SQL with a critical 3rd party component that can only reach the database via named DSN (also not existing prior to installation).

I see my primary SQL security options as being:

(1) Use SQL or Mixed Mode authentication with an admin-level username/password combination, or

(2) Create a db user/group with admin-level privileges and grant membership to all NT authenticated users

Secondary problem: Creating the DSN.

Does it make sense to create a Custom Action (.dll) that is called at the end of the installation process in order to create the database, the user security context and the named DSN?

Am I overlooking some built-in functionality provided by Visual Studio 2005 that will accompish some or all of this for me? I am aware that customizing the 'silent' installation of SQL Express to use a different authentication mode requires manifest tweaking -- I just don't know anything about setting up the appropriate security for this situation. Would you put the db and role creation stuff in a SQL script and execute it post-install?

Thanks in advance for any insight you can provide.

-T

UPDATE

I plan to modify the SQL Express installation to use mixed-mode authentication, then execute code at the tail end of my app install to (a) create the database, (b) create a dbo-level user (and pwd) for the database, and (c) create my DSN (via SQLConfigDataSource API call).

Feel free to respond if you think/know that there is a better solution.

-T

***** Deployment error: Connection closed ******

c:\Report1.rdl The underlying connection was closed: An unexpected error
occurred on a send.
When i deploy I get this error sometimes. It gets resolved on its own. Its
like a hit and trial thing, sometimes it runs, sometimes it doesnt. Wonder
what am I doing wrong?
ThanksThis could be is an IIS timeout issue. You can change this value in IIS
manager.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"NI" <NI@.discussions.microsoft.com> wrote in message
news:673C1CD2-8511-4585-8193-83A52AF2DB62@.microsoft.com...
> c:\Report1.rdl The underlying connection was closed: An unexpected error
> occurred on a send.
> When i deploy I get this error sometimes. It gets resolved on its own. Its
> like a hit and trial thing, sometimes it runs, sometimes it doesnt. Wonder
> what am I doing wrong?
> Thanks
>

(Report Model Deployment Error) The value of parameter 'DataSources' is not valid

I've got a report model I am trying to move from a development server to a production server. I published it to my development RS, exported the SMDL file, then uploaded it to the production server. At that point, I tried assigning the data source to the model and got the error:

The value of parameter 'DataSources' is not valid in the browser.
Looking in the logs, the following trace is there:

w3wp!library!7!12/12/2005-13:23:00:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!webserver!7!12/12/2005-13:23:00:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: Logon failed. > Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException: Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
w3wp!library!5!12/12/2005-13:23:49:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!1!12/12/2005-13:23:49:: i INFO: Call to GetSystemPermissions
w3wp!library!7!12/12/2005-13:23:50:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!7!12/12/2005-13:23:51:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid.
w3wp!library!7!12/12/2005-13:30:18:: Using folder C:\Program Files\Microsoft SQL Server 2005\MSSQL.3\Reporting Services\RSTempFiles for temporary files.
w3wp!library!7!12/12/2005-13:30:18:: i INFO: Cleaned 0 batch records, 0 policies, 1 sessions, 0 cache entries, 1 snapshots, 1 chunks, 0 running jobs, 0 persisted streams

The problem is that the data source is selected to be Integrated Windows Authentication, so I'm a bit confused as to what's up with the model.

PS I am local admin on the machine as well as System Admin for reporting services.

I have a similar problem. I do not yet have a resolution:

Can't call reports from Report Manager.

I've installed Reporting Services 2005 on a Windows 2003 Server. The server has a successful side by side install of VS2003 and VS2005 and a successful side by side install of SQL Server 2000 and SQL Server 2005. It also is a Domain Controller [I know that this is suboptimal, but I don't have enough machines to avoid this right now]. I am Domain Administrator and did the install as domain admin. Also, the domain admin account is the default dbo for the SQLServer 2005 install. I followed a default install of Reporting Services [under the default web site] and it worked properly. I then had an issue where I needed another site under the default web site to use ASP.NET 1.1, so I moved the Reporting Services website to a separate web site with a distinct assigned IP. I did this by "hand" in the IIS Manager. Since then I've had a rsLogonFailed error when trying to access reports from the Report Server. I reinstalled Reporting Services, but got a cryptic message indicating that the deinstall was not perfectly clean.

Since I really don't want to launch a major rebuilding effort on this computer, I've been trying to find the special sauce to put this back together again. I've adjusted the Reporting Services Configuration, the ASP.NET application pools, and the SQL DB logins and permissions. No success.

The executionlog table in the ReportServer$SQLServer2005 database records the failed logins. It indentifies the UserName and the status "rsLogonFailed", along with the reportID, timestamp, etc.

I have noticed, via Google, other users having similar problems. For instance, someone trying to establish an email subscription has an rsLogonFailed problem at: http://www.sqltalk.org/ftopic7220.html

Here is my trace:

w3wp!chunks!5!12/18/2005-22:19:49:: v VERBOSE: ### CopyImages(d221ebad-7547-4c48-9324-90a21d66a168,715a6af3-dd95-44f7-b3c5-c660f3c3393f)
w3wp!library!5!12/18/2005-22:19:49:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!library!5!12/18/2005-22:19:49:: v VERBOSE: Transaction rollback.
w3wp!dbcleanup!5!12/18/2005-22:25:28:: v VERBOSE: Starting database cleanup.

The error that you are getting is the closest to mine that I've seen on the net. Does anyone have any ideas?

Best,

Mike

|||

Have you received any solution for this problem? I am having the same problem and in desparate need for a fix.

I heard from the below site/comments that there is a problem with SQL Reporting Services 2005 and Windows Server 2003 SP1.

Apparently there are some issues with Windows 2003 when trying to
impersonate a user to a remote resource. We stumbled across a similar issue
when using SQL Reporting Services hosted on Windows 2003. We reinstalled the
entire reporting environment onto a Windows 2000 Server and the problem
immediately disappeared. These issues related to security problems access
resources on remote machines via a web application.

http://groups.google.com/group/microsoft.public.dotnet.framework.webservices/browse_thread/thread/bb9f3db6230a04ed/3d342d8c40e6aede?lnk=st&q=Reporting+Services+referenced+account+locked+out&rnum=1&hl=en#3d342d8c40e6aede

Thanks for any assistance, anyone can give me.

|||Open the datasource properties and make sure that credentials are either "Credentials stored securely in report server" or "Windows integrated security"|||Also make sure that you have a fully qualified user name, i.e. domain\username or machine\username.|||

If the suggestions above don't fix this error, try to update the password for the unattended execution account: rsconfig.exe -e ... - or through the RsConfigTool in RS 2005

Thanks

tudor

|||

I follow this thread and found the source of my problem. I had lost the execution account definition. when I restored that in reporting Services Configuration manager, the login failures stopped.

thank you

Tebby Wafer

|||Just an FYI. I had the very same problem, but in order to correct, I had to remove the execution account credentials. After doing so, my reports worked again. I'll try re-adding the execution account again at a later time if needed.|||I also had this problem on a development machine and it appeared to be because the password had changed on the Execution Account (it had been set as a user account). To resolve the problem I had to change the stored password on the execution account by going into the Reporting Services Configuration Manager (under Configuration Tools in the Start Menu) and clicking on the Execution Account option. You can change the account or reset the password here.|||I am experiencing the same issue with SSRS and Windows 2003 I now have WMI errors and the reinstallation of SSRS is a nightmare which I still haven't solved yet. This is just POOR product service by Microsoft. I am so frustrated I am considering discontinuing all reporting services and switch to another reporting platform.|||I was having a similar error just viewing a report. Reconfiguring the Execution Account solved my problem as well.|||

Hello, I am new to MS CRm and everything. Where can i find this execution account ?

Kumail

(Report Model Deployment Error) The value of parameter 'DataSources' is not valid

I've got a report model I am trying to move from a development server to a production server. I published it to my development RS, exported the SMDL file, then uploaded it to the production server. At that point, I tried assigning the data source to the model and got the error:

The value of parameter 'DataSources' is not valid in the browser.
Looking in the logs, the following trace is there:

w3wp!library!7!12/12/2005-13:23:00:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!webserver!7!12/12/2005-13:23:00:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: Logon failed. > Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException: Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
w3wp!library!5!12/12/2005-13:23:49:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!1!12/12/2005-13:23:49:: i INFO: Call to GetSystemPermissions
w3wp!library!7!12/12/2005-13:23:50:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!7!12/12/2005-13:23:51:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid.
w3wp!library!7!12/12/2005-13:30:18:: Using folder C:\Program Files\Microsoft SQL Server 2005\MSSQL.3\Reporting Services\RSTempFiles for temporary files.
w3wp!library!7!12/12/2005-13:30:18:: i INFO: Cleaned 0 batch records, 0 policies, 1 sessions, 0 cache entries, 1 snapshots, 1 chunks, 0 running jobs, 0 persisted streams

The problem is that the data source is selected to be Integrated Windows Authentication, so I'm a bit confused as to what's up with the model.

PS I am local admin on the machine as well as System Admin for reporting services.

I have a similar problem. I do not yet have a resolution:

Can't call reports from Report Manager.

I've installed Reporting Services 2005 on a Windows 2003 Server. The server has a successful side by side install of VS2003 and VS2005 and a successful side by side install of SQL Server 2000 and SQL Server 2005. It also is a Domain Controller [I know that this is suboptimal, but I don't have enough machines to avoid this right now]. I am Domain Administrator and did the install as domain admin. Also, the domain admin account is the default dbo for the SQLServer 2005 install. I followed a default install of Reporting Services [under the default web site] and it worked properly. I then had an issue where I needed another site under the default web site to use ASP.NET 1.1, so I moved the Reporting Services website to a separate web site with a distinct assigned IP. I did this by "hand" in the IIS Manager. Since then I've had a rsLogonFailed error when trying to access reports from the Report Server. I reinstalled Reporting Services, but got a cryptic message indicating that the deinstall was not perfectly clean.

Since I really don't want to launch a major rebuilding effort on this computer, I've been trying to find the special sauce to put this back together again. I've adjusted the Reporting Services Configuration, the ASP.NET application pools, and the SQL DB logins and permissions. No success.

The executionlog table in the ReportServer$SQLServer2005 database records the failed logins. It indentifies the UserName and the status "rsLogonFailed", along with the reportID, timestamp, etc.

I have noticed, via Google, other users having similar problems. For instance, someone trying to establish an email subscription has an rsLogonFailed problem at: http://www.sqltalk.org/ftopic7220.html

Here is my trace:

w3wp!chunks!5!12/18/2005-22:19:49:: v VERBOSE: ### CopyImages(d221ebad-7547-4c48-9324-90a21d66a168,715a6af3-dd95-44f7-b3c5-c660f3c3393f)
w3wp!library!5!12/18/2005-22:19:49:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!library!5!12/18/2005-22:19:49:: v VERBOSE: Transaction rollback.
w3wp!dbcleanup!5!12/18/2005-22:25:28:: v VERBOSE: Starting database cleanup.

The error that you are getting is the closest to mine that I've seen on the net. Does anyone have any ideas?

Best,

Mike

|||

Have you received any solution for this problem? I am having the same problem and in desparate need for a fix.

I heard from the below site/comments that there is a problem with SQL Reporting Services 2005 and Windows Server 2003 SP1.

Apparently there are some issues with Windows 2003 when trying to
impersonate a user to a remote resource. We stumbled across a similar issue
when using SQL Reporting Services hosted on Windows 2003. We reinstalled the
entire reporting environment onto a Windows 2000 Server and the problem
immediately disappeared. These issues related to security problems access
resources on remote machines via a web application.

http://groups.google.com/group/microsoft.public.dotnet.framework.webservices/browse_thread/thread/bb9f3db6230a04ed/3d342d8c40e6aede?lnk=st&q=Reporting+Services+referenced+account+locked+out&rnum=1&hl=en#3d342d8c40e6aede

Thanks for any assistance, anyone can give me.

|||Open the datasource properties and make sure that credentials are either "Credentials stored securely in report server" or "Windows integrated security"|||Also make sure that you have a fully qualified user name, i.e. domain\username or machine\username.|||

If the suggestions above don't fix this error, try to update the password for the unattended execution account: rsconfig.exe -e ... - or through the RsConfigTool in RS 2005

Thanks

tudor

|||

I follow this thread and found the source of my problem. I had lost the execution account definition. when I restored that in reporting Services Configuration manager, the login failures stopped.

thank you

Tebby Wafer

|||Just an FYI. I had the very same problem, but in order to correct, I had to remove the execution account credentials. After doing so, my reports worked again. I'll try re-adding the execution account again at a later time if needed.|||I also had this problem on a development machine and it appeared to be because the password had changed on the Execution Account (it had been set as a user account). To resolve the problem I had to change the stored password on the execution account by going into the Reporting Services Configuration Manager (under Configuration Tools in the Start Menu) and clicking on the Execution Account option. You can change the account or reset the password here.|||I am experiencing the same issue with SSRS and Windows 2003 I now have WMI errors and the reinstallation of SSRS is a nightmare which I still haven't solved yet. This is just POOR product service by Microsoft. I am so frustrated I am considering discontinuing all reporting services and switch to another reporting platform.|||I was having a similar error just viewing a report. Reconfiguring the Execution Account solved my problem as well.|||

Hello, I am new to MS CRm and everything. Where can i find this execution account ?

Kumail

(Report Model Deployment Error) The value of parameter 'DataSources' is not valid

I've got a report model I am trying to move from a development server to a production server. I published it to my development RS, exported the SMDL file, then uploaded it to the production server. At that point, I tried assigning the data source to the model and got the error:

The value of parameter 'DataSources' is not valid in the browser.
Looking in the logs, the following trace is there:

w3wp!library!7!12/12/2005-13:23:00:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!webserver!7!12/12/2005-13:23:00:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: Logon failed. > Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException: Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
w3wp!library!5!12/12/2005-13:23:49:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!1!12/12/2005-13:23:49:: i INFO: Call to GetSystemPermissions
w3wp!library!7!12/12/2005-13:23:50:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!7!12/12/2005-13:23:51:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid.
w3wp!library!7!12/12/2005-13:30:18:: Using folder C:\Program Files\Microsoft SQL Server 2005\MSSQL.3\Reporting Services\RSTempFiles for temporary files.
w3wp!library!7!12/12/2005-13:30:18:: i INFO: Cleaned 0 batch records, 0 policies, 1 sessions, 0 cache entries, 1 snapshots, 1 chunks, 0 running jobs, 0 persisted streams

The problem is that the data source is selected to be Integrated Windows Authentication, so I'm a bit confused as to what's up with the model.

PS I am local admin on the machine as well as System Admin for reporting services.

I have a similar problem. I do not yet have a resolution:

Can't call reports from Report Manager.

I've installed Reporting Services 2005 on a Windows 2003 Server. The server has a successful side by side install of VS2003 and VS2005 and a successful side by side install of SQL Server 2000 and SQL Server 2005. It also is a Domain Controller [I know that this is suboptimal, but I don't have enough machines to avoid this right now]. I am Domain Administrator and did the install as domain admin. Also, the domain admin account is the default dbo for the SQLServer 2005 install. I followed a default install of Reporting Services [under the default web site] and it worked properly. I then had an issue where I needed another site under the default web site to use ASP.NET 1.1, so I moved the Reporting Services website to a separate web site with a distinct assigned IP. I did this by "hand" in the IIS Manager. Since then I've had a rsLogonFailed error when trying to access reports from the Report Server. I reinstalled Reporting Services, but got a cryptic message indicating that the deinstall was not perfectly clean.

Since I really don't want to launch a major rebuilding effort on this computer, I've been trying to find the special sauce to put this back together again. I've adjusted the Reporting Services Configuration, the ASP.NET application pools, and the SQL DB logins and permissions. No success.

The executionlog table in the ReportServer$SQLServer2005 database records the failed logins. It indentifies the UserName and the status "rsLogonFailed", along with the reportID, timestamp, etc.

I have noticed, via Google, other users having similar problems. For instance, someone trying to establish an email subscription has an rsLogonFailed problem at: http://www.sqltalk.org/ftopic7220.html

Here is my trace:

w3wp!chunks!5!12/18/2005-22:19:49:: v VERBOSE: ### CopyImages(d221ebad-7547-4c48-9324-90a21d66a168,715a6af3-dd95-44f7-b3c5-c660f3c3393f)
w3wp!library!5!12/18/2005-22:19:49:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!library!5!12/18/2005-22:19:49:: v VERBOSE: Transaction rollback.
w3wp!dbcleanup!5!12/18/2005-22:25:28:: v VERBOSE: Starting database cleanup.

The error that you are getting is the closest to mine that I've seen on the net. Does anyone have any ideas?

Best,

Mike

|||

Have you received any solution for this problem? I am having the same problem and in desparate need for a fix.

I heard from the below site/comments that there is a problem with SQL Reporting Services 2005 and Windows Server 2003 SP1.

Apparently there are some issues with Windows 2003 when trying to
impersonate a user to a remote resource. We stumbled across a similar issue
when using SQL Reporting Services hosted on Windows 2003. We reinstalled the
entire reporting environment onto a Windows 2000 Server and the problem
immediately disappeared. These issues related to security problems access
resources on remote machines via a web application.

http://groups.google.com/group/microsoft.public.dotnet.framework.webservices/browse_thread/thread/bb9f3db6230a04ed/3d342d8c40e6aede?lnk=st&q=Reporting+Services+referenced+account+locked+out&rnum=1&hl=en#3d342d8c40e6aede

Thanks for any assistance, anyone can give me.

|||Open the datasource properties and make sure that credentials are either "Credentials stored securely in report server" or "Windows integrated security"|||Also make sure that you have a fully qualified user name, i.e. domain\username or machine\username.|||

If the suggestions above don't fix this error, try to update the password for the unattended execution account: rsconfig.exe -e ... - or through the RsConfigTool in RS 2005

Thanks

tudor

|||

I follow this thread and found the source of my problem. I had lost the execution account definition. when I restored that in reporting Services Configuration manager, the login failures stopped.

thank you

Tebby Wafer

|||Just an FYI. I had the very same problem, but in order to correct, I had to remove the execution account credentials. After doing so, my reports worked again. I'll try re-adding the execution account again at a later time if needed.|||I also had this problem on a development machine and it appeared to be because the password had changed on the Execution Account (it had been set as a user account). To resolve the problem I had to change the stored password on the execution account by going into the Reporting Services Configuration Manager (under Configuration Tools in the Start Menu) and clicking on the Execution Account option. You can change the account or reset the password here.|||I am experiencing the same issue with SSRS and Windows 2003 I now have WMI errors and the reinstallation of SSRS is a nightmare which I still haven't solved yet. This is just POOR product service by Microsoft. I am so frustrated I am considering discontinuing all reporting services and switch to another reporting platform.|||I was having a similar error just viewing a report. Reconfiguring the Execution Account solved my problem as well.|||

Hello, I am new to MS CRm and everything. Where can i find this execution account ?

Kumail

(Report Model Deployment Error) The value of parameter 'DataSources' is not valid

I've got a report model I am trying to move from a development server to a production server. I published it to my development RS, exported the SMDL file, then uploaded it to the production server. At that point, I tried assigning the data source to the model and got the error:

The value of parameter 'DataSources' is not valid in the browser.
Looking in the logs, the following trace is there:

w3wp!library!7!12/12/2005-13:23:00:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!webserver!7!12/12/2005-13:23:00:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: Logon failed. > Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException: Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
w3wp!library!5!12/12/2005-13:23:49:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!1!12/12/2005-13:23:49:: i INFO: Call to GetSystemPermissions
w3wp!library!7!12/12/2005-13:23:50:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!7!12/12/2005-13:23:51:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid.
w3wp!library!7!12/12/2005-13:30:18:: Using folder C:\Program Files\Microsoft SQL Server 2005\MSSQL.3\Reporting Services\RSTempFiles for temporary files.
w3wp!library!7!12/12/2005-13:30:18:: i INFO: Cleaned 0 batch records, 0 policies, 1 sessions, 0 cache entries, 1 snapshots, 1 chunks, 0 running jobs, 0 persisted streams

The problem is that the data source is selected to be Integrated Windows Authentication, so I'm a bit confused as to what's up with the model.

PS I am local admin on the machine as well as System Admin for reporting services.

I have a similar problem. I do not yet have a resolution:

Can't call reports from Report Manager.

I've installed Reporting Services 2005 on a Windows 2003 Server. The server has a successful side by side install of VS2003 and VS2005 and a successful side by side install of SQL Server 2000 and SQL Server 2005. It also is a Domain Controller [I know that this is suboptimal, but I don't have enough machines to avoid this right now]. I am Domain Administrator and did the install as domain admin. Also, the domain admin account is the default dbo for the SQLServer 2005 install. I followed a default install of Reporting Services [under the default web site] and it worked properly. I then had an issue where I needed another site under the default web site to use ASP.NET 1.1, so I moved the Reporting Services website to a separate web site with a distinct assigned IP. I did this by "hand" in the IIS Manager. Since then I've had a rsLogonFailed error when trying to access reports from the Report Server. I reinstalled Reporting Services, but got a cryptic message indicating that the deinstall was not perfectly clean.

Since I really don't want to launch a major rebuilding effort on this computer, I've been trying to find the special sauce to put this back together again. I've adjusted the Reporting Services Configuration, the ASP.NET application pools, and the SQL DB logins and permissions. No success.

The executionlog table in the ReportServer$SQLServer2005 database records the failed logins. It indentifies the UserName and the status "rsLogonFailed", along with the reportID, timestamp, etc.

I have noticed, via Google, other users having similar problems. For instance, someone trying to establish an email subscription has an rsLogonFailed problem at: http://www.sqltalk.org/ftopic7220.html

Here is my trace:

w3wp!chunks!5!12/18/2005-22:19:49:: v VERBOSE: ### CopyImages(d221ebad-7547-4c48-9324-90a21d66a168,715a6af3-dd95-44f7-b3c5-c660f3c3393f)
w3wp!library!5!12/18/2005-22:19:49:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!library!5!12/18/2005-22:19:49:: v VERBOSE: Transaction rollback.
w3wp!dbcleanup!5!12/18/2005-22:25:28:: v VERBOSE: Starting database cleanup.

The error that you are getting is the closest to mine that I've seen on the net. Does anyone have any ideas?

Best,

Mike

|||

Have you received any solution for this problem? I am having the same problem and in desparate need for a fix.

I heard from the below site/comments that there is a problem with SQL Reporting Services 2005 and Windows Server 2003 SP1.

Apparently there are some issues with Windows 2003 when trying to
impersonate a user to a remote resource. We stumbled across a similar issue
when using SQL Reporting Services hosted on Windows 2003. We reinstalled the
entire reporting environment onto a Windows 2000 Server and the problem
immediately disappeared. These issues related to security problems access
resources on remote machines via a web application.

http://groups.google.com/group/microsoft.public.dotnet.framework.webservices/browse_thread/thread/bb9f3db6230a04ed/3d342d8c40e6aede?lnk=st&q=Reporting+Services+referenced+account+locked+out&rnum=1&hl=en#3d342d8c40e6aede

Thanks for any assistance, anyone can give me.

|||Open the datasource properties and make sure that credentials are either "Credentials stored securely in report server" or "Windows integrated security"|||Also make sure that you have a fully qualified user name, i.e. domain\username or machine\username.|||

If the suggestions above don't fix this error, try to update the password for the unattended execution account: rsconfig.exe -e ... - or through the RsConfigTool in RS 2005

Thanks

tudor

|||

I follow this thread and found the source of my problem. I had lost the execution account definition. when I restored that in reporting Services Configuration manager, the login failures stopped.

thank you

Tebby Wafer

|||Just an FYI. I had the very same problem, but in order to correct, I had to remove the execution account credentials. After doing so, my reports worked again. I'll try re-adding the execution account again at a later time if needed.|||I also had this problem on a development machine and it appeared to be because the password had changed on the Execution Account (it had been set as a user account). To resolve the problem I had to change the stored password on the execution account by going into the Reporting Services Configuration Manager (under Configuration Tools in the Start Menu) and clicking on the Execution Account option. You can change the account or reset the password here.|||I am experiencing the same issue with SSRS and Windows 2003 I now have WMI errors and the reinstallation of SSRS is a nightmare which I still haven't solved yet. This is just POOR product service by Microsoft. I am so frustrated I am considering discontinuing all reporting services and switch to another reporting platform.|||I was having a similar error just viewing a report. Reconfiguring the Execution Account solved my problem as well.|||

Hello, I am new to MS CRm and everything. Where can i find this execution account ?

Kumail

(Report Model Deployment Error) The value of parameter 'DataSources' is not valid

I've got a report model I am trying to move from a development server to a production server. I published it to my development RS, exported the SMDL file, then uploaded it to the production server. At that point, I tried assigning the data source to the model and got the error:

The value of parameter 'DataSources' is not valid in the browser.
Looking in the logs, the following trace is there:

w3wp!library!7!12/12/2005-13:23:00:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!webserver!7!12/12/2005-13:23:00:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: Logon failed. > Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException: Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
w3wp!library!5!12/12/2005-13:23:49:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!1!12/12/2005-13:23:49:: i INFO: Call to GetSystemPermissions
w3wp!library!7!12/12/2005-13:23:50:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!7!12/12/2005-13:23:51:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid.
w3wp!library!7!12/12/2005-13:30:18:: Using folder C:\Program Files\Microsoft SQL Server 2005\MSSQL.3\Reporting Services\RSTempFiles for temporary files.
w3wp!library!7!12/12/2005-13:30:18:: i INFO: Cleaned 0 batch records, 0 policies, 1 sessions, 0 cache entries, 1 snapshots, 1 chunks, 0 running jobs, 0 persisted streams

The problem is that the data source is selected to be Integrated Windows Authentication, so I'm a bit confused as to what's up with the model.

PS I am local admin on the machine as well as System Admin for reporting services.

I have a similar problem. I do not yet have a resolution:

Can't call reports from Report Manager.

I've installed Reporting Services 2005 on a Windows 2003 Server. The server has a successful side by side install of VS2003 and VS2005 and a successful side by side install of SQL Server 2000 and SQL Server 2005. It also is a Domain Controller [I know that this is suboptimal, but I don't have enough machines to avoid this right now]. I am Domain Administrator and did the install as domain admin. Also, the domain admin account is the default dbo for the SQLServer 2005 install. I followed a default install of Reporting Services [under the default web site] and it worked properly. I then had an issue where I needed another site under the default web site to use ASP.NET 1.1, so I moved the Reporting Services website to a separate web site with a distinct assigned IP. I did this by "hand" in the IIS Manager. Since then I've had a rsLogonFailed error when trying to access reports from the Report Server. I reinstalled Reporting Services, but got a cryptic message indicating that the deinstall was not perfectly clean.

Since I really don't want to launch a major rebuilding effort on this computer, I've been trying to find the special sauce to put this back together again. I've adjusted the Reporting Services Configuration, the ASP.NET application pools, and the SQL DB logins and permissions. No success.

The executionlog table in the ReportServer$SQLServer2005 database records the failed logins. It indentifies the UserName and the status "rsLogonFailed", along with the reportID, timestamp, etc.

I have noticed, via Google, other users having similar problems. For instance, someone trying to establish an email subscription has an rsLogonFailed problem at: http://www.sqltalk.org/ftopic7220.html

Here is my trace:

w3wp!chunks!5!12/18/2005-22:19:49:: v VERBOSE: ### CopyImages(d221ebad-7547-4c48-9324-90a21d66a168,715a6af3-dd95-44f7-b3c5-c660f3c3393f)
w3wp!library!5!12/18/2005-22:19:49:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!library!5!12/18/2005-22:19:49:: v VERBOSE: Transaction rollback.
w3wp!dbcleanup!5!12/18/2005-22:25:28:: v VERBOSE: Starting database cleanup.

The error that you are getting is the closest to mine that I've seen on the net. Does anyone have any ideas?

Best,

Mike

|||

Have you received any solution for this problem? I am having the same problem and in desparate need for a fix.

I heard from the below site/comments that there is a problem with SQL Reporting Services 2005 and Windows Server 2003 SP1.

Apparently there are some issues with Windows 2003 when trying to
impersonate a user to a remote resource. We stumbled across a similar issue
when using SQL Reporting Services hosted on Windows 2003. We reinstalled the
entire reporting environment onto a Windows 2000 Server and the problem
immediately disappeared. These issues related to security problems access
resources on remote machines via a web application.

http://groups.google.com/group/microsoft.public.dotnet.framework.webservices/browse_thread/thread/bb9f3db6230a04ed/3d342d8c40e6aede?lnk=st&q=Reporting+Services+referenced+account+locked+out&rnum=1&hl=en#3d342d8c40e6aede

Thanks for any assistance, anyone can give me.

|||Open the datasource properties and make sure that credentials are either "Credentials stored securely in report server" or "Windows integrated security"|||Also make sure that you have a fully qualified user name, i.e. domain\username or machine\username.|||

If the suggestions above don't fix this error, try to update the password for the unattended execution account: rsconfig.exe -e ... - or through the RsConfigTool in RS 2005

Thanks

tudor

|||

I follow this thread and found the source of my problem. I had lost the execution account definition. when I restored that in reporting Services Configuration manager, the login failures stopped.

thank you

Tebby Wafer

|||Just an FYI. I had the very same problem, but in order to correct, I had to remove the execution account credentials. After doing so, my reports worked again. I'll try re-adding the execution account again at a later time if needed.|||I also had this problem on a development machine and it appeared to be because the password had changed on the Execution Account (it had been set as a user account). To resolve the problem I had to change the stored password on the execution account by going into the Reporting Services Configuration Manager (under Configuration Tools in the Start Menu) and clicking on the Execution Account option. You can change the account or reset the password here.|||I am experiencing the same issue with SSRS and Windows 2003 I now have WMI errors and the reinstallation of SSRS is a nightmare which I still haven't solved yet. This is just POOR product service by Microsoft. I am so frustrated I am considering discontinuing all reporting services and switch to another reporting platform.|||I was having a similar error just viewing a report. Reconfiguring the Execution Account solved my problem as well.|||

Hello, I am new to MS CRm and everything. Where can i find this execution account ?

Kumail

(Report Model Deployment Error) The value of parameter 'DataSources' is not valid

I've got a report model I am trying to move from a development server to a production server. I published it to my development RS, exported the SMDL file, then uploaded it to the production server. At that point, I tried assigning the data source to the model and got the error:

The value of parameter 'DataSources' is not valid in the browser.
Looking in the logs, the following trace is there:

w3wp!library!7!12/12/2005-13:23:00:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!webserver!7!12/12/2005-13:23:00:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: Logon failed. > Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException: Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
w3wp!library!5!12/12/2005-13:23:49:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!1!12/12/2005-13:23:49:: i INFO: Call to GetSystemPermissions
w3wp!library!7!12/12/2005-13:23:50:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!7!12/12/2005-13:23:51:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid.
w3wp!library!7!12/12/2005-13:30:18:: Using folder C:\Program Files\Microsoft SQL Server 2005\MSSQL.3\Reporting Services\RSTempFiles for temporary files.
w3wp!library!7!12/12/2005-13:30:18:: i INFO: Cleaned 0 batch records, 0 policies, 1 sessions, 0 cache entries, 1 snapshots, 1 chunks, 0 running jobs, 0 persisted streams

The problem is that the data source is selected to be Integrated Windows Authentication, so I'm a bit confused as to what's up with the model.

PS I am local admin on the machine as well as System Admin for reporting services.

I have a similar problem. I do not yet have a resolution:

Can't call reports from Report Manager.

I've installed Reporting Services 2005 on a Windows 2003 Server. The server has a successful side by side install of VS2003 and VS2005 and a successful side by side install of SQL Server 2000 and SQL Server 2005. It also is a Domain Controller [I know that this is suboptimal, but I don't have enough machines to avoid this right now]. I am Domain Administrator and did the install as domain admin. Also, the domain admin account is the default dbo for the SQLServer 2005 install. I followed a default install of Reporting Services [under the default web site] and it worked properly. I then had an issue where I needed another site under the default web site to use ASP.NET 1.1, so I moved the Reporting Services website to a separate web site with a distinct assigned IP. I did this by "hand" in the IIS Manager. Since then I've had a rsLogonFailed error when trying to access reports from the Report Server. I reinstalled Reporting Services, but got a cryptic message indicating that the deinstall was not perfectly clean.

Since I really don't want to launch a major rebuilding effort on this computer, I've been trying to find the special sauce to put this back together again. I've adjusted the Reporting Services Configuration, the ASP.NET application pools, and the SQL DB logins and permissions. No success.

The executionlog table in the ReportServer$SQLServer2005 database records the failed logins. It indentifies the UserName and the status "rsLogonFailed", along with the reportID, timestamp, etc.

I have noticed, via Google, other users having similar problems. For instance, someone trying to establish an email subscription has an rsLogonFailed problem at: http://www.sqltalk.org/ftopic7220.html

Here is my trace:

w3wp!chunks!5!12/18/2005-22:19:49:: v VERBOSE: ### CopyImages(d221ebad-7547-4c48-9324-90a21d66a168,715a6af3-dd95-44f7-b3c5-c660f3c3393f)
w3wp!library!5!12/18/2005-22:19:49:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!library!5!12/18/2005-22:19:49:: v VERBOSE: Transaction rollback.
w3wp!dbcleanup!5!12/18/2005-22:25:28:: v VERBOSE: Starting database cleanup.

The error that you are getting is the closest to mine that I've seen on the net. Does anyone have any ideas?

Best,

Mike

|||

Have you received any solution for this problem? I am having the same problem and in desparate need for a fix.

I heard from the below site/comments that there is a problem with SQL Reporting Services 2005 and Windows Server 2003 SP1.

Apparently there are some issues with Windows 2003 when trying to
impersonate a user to a remote resource. We stumbled across a similar issue
when using SQL Reporting Services hosted on Windows 2003. We reinstalled the
entire reporting environment onto a Windows 2000 Server and the problem
immediately disappeared. These issues related to security problems access
resources on remote machines via a web application.

http://groups.google.com/group/microsoft.public.dotnet.framework.webservices/browse_thread/thread/bb9f3db6230a04ed/3d342d8c40e6aede?lnk=st&q=Reporting+Services+referenced+account+locked+out&rnum=1&hl=en#3d342d8c40e6aede

Thanks for any assistance, anyone can give me.

|||Open the datasource properties and make sure that credentials are either "Credentials stored securely in report server" or "Windows integrated security"|||Also make sure that you have a fully qualified user name, i.e. domain\username or machine\username.|||

If the suggestions above don't fix this error, try to update the password for the unattended execution account: rsconfig.exe -e ... - or through the RsConfigTool in RS 2005

Thanks

tudor

|||

I follow this thread and found the source of my problem. I had lost the execution account definition. when I restored that in reporting Services Configuration manager, the login failures stopped.

thank you

Tebby Wafer

|||Just an FYI. I had the very same problem, but in order to correct, I had to remove the execution account credentials. After doing so, my reports worked again. I'll try re-adding the execution account again at a later time if needed.|||I also had this problem on a development machine and it appeared to be because the password had changed on the Execution Account (it had been set as a user account). To resolve the problem I had to change the stored password on the execution account by going into the Reporting Services Configuration Manager (under Configuration Tools in the Start Menu) and clicking on the Execution Account option. You can change the account or reset the password here.|||I am experiencing the same issue with SSRS and Windows 2003 I now have WMI errors and the reinstallation of SSRS is a nightmare which I still haven't solved yet. This is just POOR product service by Microsoft. I am so frustrated I am considering discontinuing all reporting services and switch to another reporting platform.|||I was having a similar error just viewing a report. Reconfiguring the Execution Account solved my problem as well.|||

Hello, I am new to MS CRm and everything. Where can i find this execution account ?

Kumail

(Report Model Deployment Error) The value of parameter 'DataSources' is not valid

I've got a report model I am trying to move from a development server to a production server. I published it to my development RS, exported the SMDL file, then uploaded it to the production server. At that point, I tried assigning the data source to the model and got the error:

The value of parameter 'DataSources' is not valid in the browser.
Looking in the logs, the following trace is there:

w3wp!library!7!12/12/2005-13:23:00:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!webserver!7!12/12/2005-13:23:00:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: Logon failed. > Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException: Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
w3wp!library!5!12/12/2005-13:23:49:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!1!12/12/2005-13:23:49:: i INFO: Call to GetSystemPermissions
w3wp!library!7!12/12/2005-13:23:50:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!7!12/12/2005-13:23:51:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid.
w3wp!library!7!12/12/2005-13:30:18:: Using folder C:\Program Files\Microsoft SQL Server 2005\MSSQL.3\Reporting Services\RSTempFiles for temporary files.
w3wp!library!7!12/12/2005-13:30:18:: i INFO: Cleaned 0 batch records, 0 policies, 1 sessions, 0 cache entries, 1 snapshots, 1 chunks, 0 running jobs, 0 persisted streams

The problem is that the data source is selected to be Integrated Windows Authentication, so I'm a bit confused as to what's up with the model.

PS I am local admin on the machine as well as System Admin for reporting services.

I have a similar problem. I do not yet have a resolution:

Can't call reports from Report Manager.

I've installed Reporting Services 2005 on a Windows 2003 Server. The server has a successful side by side install of VS2003 and VS2005 and a successful side by side install of SQL Server 2000 and SQL Server 2005. It also is a Domain Controller [I know that this is suboptimal, but I don't have enough machines to avoid this right now]. I am Domain Administrator and did the install as domain admin. Also, the domain admin account is the default dbo for the SQLServer 2005 install. I followed a default install of Reporting Services [under the default web site] and it worked properly. I then had an issue where I needed another site under the default web site to use ASP.NET 1.1, so I moved the Reporting Services website to a separate web site with a distinct assigned IP. I did this by "hand" in the IIS Manager. Since then I've had a rsLogonFailed error when trying to access reports from the Report Server. I reinstalled Reporting Services, but got a cryptic message indicating that the deinstall was not perfectly clean.

Since I really don't want to launch a major rebuilding effort on this computer, I've been trying to find the special sauce to put this back together again. I've adjusted the Reporting Services Configuration, the ASP.NET application pools, and the SQL DB logins and permissions. No success.

The executionlog table in the ReportServer$SQLServer2005 database records the failed logins. It indentifies the UserName and the status "rsLogonFailed", along with the reportID, timestamp, etc.

I have noticed, via Google, other users having similar problems. For instance, someone trying to establish an email subscription has an rsLogonFailed problem at: http://www.sqltalk.org/ftopic7220.html

Here is my trace:

w3wp!chunks!5!12/18/2005-22:19:49:: v VERBOSE: ### CopyImages(d221ebad-7547-4c48-9324-90a21d66a168,715a6af3-dd95-44f7-b3c5-c660f3c3393f)
w3wp!library!5!12/18/2005-22:19:49:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!library!5!12/18/2005-22:19:49:: v VERBOSE: Transaction rollback.
w3wp!dbcleanup!5!12/18/2005-22:25:28:: v VERBOSE: Starting database cleanup.

The error that you are getting is the closest to mine that I've seen on the net. Does anyone have any ideas?

Best,

Mike

|||

Have you received any solution for this problem? I am having the same problem and in desparate need for a fix.

I heard from the below site/comments that there is a problem with SQL Reporting Services 2005 and Windows Server 2003 SP1.

Apparently there are some issues with Windows 2003 when trying to
impersonate a user to a remote resource. We stumbled across a similar issue
when using SQL Reporting Services hosted on Windows 2003. We reinstalled the
entire reporting environment onto a Windows 2000 Server and the problem
immediately disappeared. These issues related to security problems access
resources on remote machines via a web application.

http://groups.google.com/group/microsoft.public.dotnet.framework.webservices/browse_thread/thread/bb9f3db6230a04ed/3d342d8c40e6aede?lnk=st&q=Reporting+Services+referenced+account+locked+out&rnum=1&hl=en#3d342d8c40e6aede

Thanks for any assistance, anyone can give me.

|||Open the datasource properties and make sure that credentials are either "Credentials stored securely in report server" or "Windows integrated security"|||Also make sure that you have a fully qualified user name, i.e. domain\username or machine\username.|||

If the suggestions above don't fix this error, try to update the password for the unattended execution account: rsconfig.exe -e ... - or through the RsConfigTool in RS 2005

Thanks

tudor

|||

I follow this thread and found the source of my problem. I had lost the execution account definition. when I restored that in reporting Services Configuration manager, the login failures stopped.

thank you

Tebby Wafer

|||Just an FYI. I had the very same problem, but in order to correct, I had to remove the execution account credentials. After doing so, my reports worked again. I'll try re-adding the execution account again at a later time if needed.|||I also had this problem on a development machine and it appeared to be because the password had changed on the Execution Account (it had been set as a user account). To resolve the problem I had to change the stored password on the execution account by going into the Reporting Services Configuration Manager (under Configuration Tools in the Start Menu) and clicking on the Execution Account option. You can change the account or reset the password here.|||I am experiencing the same issue with SSRS and Windows 2003 I now have WMI errors and the reinstallation of SSRS is a nightmare which I still haven't solved yet. This is just POOR product service by Microsoft. I am so frustrated I am considering discontinuing all reporting services and switch to another reporting platform.|||I was having a similar error just viewing a report. Reconfiguring the Execution Account solved my problem as well.|||

Hello, I am new to MS CRm and everything. Where can i find this execution account ?

Kumail

(Report Model Deployment Error) The value of parameter 'DataSources' is not valid

I've got a report model I am trying to move from a development server to a production server. I published it to my development RS, exported the SMDL file, then uploaded it to the production server. At that point, I tried assigning the data source to the model and got the error:

The value of parameter 'DataSources' is not valid in the browser.
Looking in the logs, the following trace is there:

w3wp!library!7!12/12/2005-13:23:00:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!webserver!7!12/12/2005-13:23:00:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: Logon failed. > Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException: Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
w3wp!library!5!12/12/2005-13:23:49:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!1!12/12/2005-13:23:49:: i INFO: Call to GetSystemPermissions
w3wp!library!7!12/12/2005-13:23:50:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!7!12/12/2005-13:23:51:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetPermissions:/ADS Reports/Production Data Sources/ADS
w3wp!library!5!12/12/2005-13:23:52:: i INFO: Call to GetSystemPermissions
w3wp!library!5!12/12/2005-13:23:52:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException: The value of parameter 'DataSources' is not valid.
w3wp!library!7!12/12/2005-13:30:18:: Using folder C:\Program Files\Microsoft SQL Server 2005\MSSQL.3\Reporting Services\RSTempFiles for temporary files.
w3wp!library!7!12/12/2005-13:30:18:: i INFO: Cleaned 0 batch records, 0 policies, 1 sessions, 0 cache entries, 1 snapshots, 1 chunks, 0 running jobs, 0 persisted streams

The problem is that the data source is selected to be Integrated Windows Authentication, so I'm a bit confused as to what's up with the model.

PS I am local admin on the machine as well as System Admin for reporting services.

I have a similar problem. I do not yet have a resolution:

Can't call reports from Report Manager.

I've installed Reporting Services 2005 on a Windows 2003 Server. The server has a successful side by side install of VS2003 and VS2005 and a successful side by side install of SQL Server 2000 and SQL Server 2005. It also is a Domain Controller [I know that this is suboptimal, but I don't have enough machines to avoid this right now]. I am Domain Administrator and did the install as domain admin. Also, the domain admin account is the default dbo for the SQLServer 2005 install. I followed a default install of Reporting Services [under the default web site] and it worked properly. I then had an issue where I needed another site under the default web site to use ASP.NET 1.1, so I moved the Reporting Services website to a separate web site with a distinct assigned IP. I did this by "hand" in the IIS Manager. Since then I've had a rsLogonFailed error when trying to access reports from the Report Server. I reinstalled Reporting Services, but got a cryptic message indicating that the deinstall was not perfectly clean.

Since I really don't want to launch a major rebuilding effort on this computer, I've been trying to find the special sauce to put this back together again. I've adjusted the Reporting Services Configuration, the ASP.NET application pools, and the SQL DB logins and permissions. No success.

The executionlog table in the ReportServer$SQLServer2005 database records the failed logins. It indentifies the UserName and the status "rsLogonFailed", along with the reportID, timestamp, etc.

I have noticed, via Google, other users having similar problems. For instance, someone trying to establish an email subscription has an rsLogonFailed problem at: http://www.sqltalk.org/ftopic7220.html

Here is my trace:

w3wp!chunks!5!12/18/2005-22:19:49:: v VERBOSE: ### CopyImages(d221ebad-7547-4c48-9324-90a21d66a168,715a6af3-dd95-44f7-b3c5-c660f3c3393f)
w3wp!library!5!12/18/2005-22:19:49:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Logon failed. > System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName, String pDomain, String pPassword)
at Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType credType, Guid dataSourceId, String userName, String userPwd, String domain)
End of inner exception stack trace
w3wp!library!5!12/18/2005-22:19:49:: v VERBOSE: Transaction rollback.
w3wp!dbcleanup!5!12/18/2005-22:25:28:: v VERBOSE: Starting database cleanup.

The error that you are getting is the closest to mine that I've seen on the net. Does anyone have any ideas?

Best,

Mike

|||

Have you received any solution for this problem? I am having the same problem and in desparate need for a fix.

I heard from the below site/comments that there is a problem with SQL Reporting Services 2005 and Windows Server 2003 SP1.

Apparently there are some issues with Windows 2003 when trying to
impersonate a user to a remote resource. We stumbled across a similar issue
when using SQL Reporting Services hosted on Windows 2003. We reinstalled the
entire reporting environment onto a Windows 2000 Server and the problem
immediately disappeared. These issues related to security problems access
resources on remote machines via a web application.

http://groups.google.com/group/microsoft.public.dotnet.framework.webservices/browse_thread/thread/bb9f3db6230a04ed/3d342d8c40e6aede?lnk=st&q=Reporting+Services+referenced+account+locked+out&rnum=1&hl=en#3d342d8c40e6aede

Thanks for any assistance, anyone can give me.

|||Open the datasource properties and make sure that credentials are either "Credentials stored securely in report server" or "Windows integrated security"|||Also make sure that you have a fully qualified user name, i.e. domain\username or machine\username.|||

If the suggestions above don't fix this error, try to update the password for the unattended execution account: rsconfig.exe -e ... - or through the RsConfigTool in RS 2005

Thanks

tudor

|||

I follow this thread and found the source of my problem. I had lost the execution account definition. when I restored that in reporting Services Configuration manager, the login failures stopped.

thank you

Tebby Wafer

|||Just an FYI. I had the very same problem, but in order to correct, I had to remove the execution account credentials. After doing so, my reports worked again. I'll try re-adding the execution account again at a later time if needed.|||I also had this problem on a development machine and it appeared to be because the password had changed on the Execution Account (it had been set as a user account). To resolve the problem I had to change the stored password on the execution account by going into the Reporting Services Configuration Manager (under Configuration Tools in the Start Menu) and clicking on the Execution Account option. You can change the account or reset the password here.|||I am experiencing the same issue with SSRS and Windows 2003 I now have WMI errors and the reinstallation of SSRS is a nightmare which I still haven't solved yet. This is just POOR product service by Microsoft. I am so frustrated I am considering discontinuing all reporting services and switch to another reporting platform.|||I was having a similar error just viewing a report. Reconfiguring the Execution Account solved my problem as well.|||

Hello, I am new to MS CRm and everything. Where can i find this execution account ?

Kumail