Showing posts with label msg. Show all posts
Showing posts with label msg. Show all posts

Monday, March 26, 2012

Pdf Export using WebService- Error

Hi,
I am trying SRS2005 export into pdf using webservices,I got an error msg as below,any suggestions appreciated.

System.Web.Services.Protocols.SoapException: The permissions granted to user 'PPCCWDDC450P81\IUSR_PPCCWDDC450P81' are insufficient for performing this operation. > Microsoft.ReportingServices.Diagnostics.Utilities.RSException: The permissions granted to user 'PPCCWDDC450P81\IUSR_PPCCWDDC450P81' are insufficient for performing this operation. > Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user 'PPCCWDDC450P81\IUSR_PPCCWDDC450P81' are insufficient for performing this operation.
at Microsoft.ReportingServices.Library.RSService._GetReportParameterDefinitionFromCatalog(CatalogItemContext reportContext, String historyID, Boolean forRendering, Guid& reportID, Int32& executionOption, String& savedParametersXml, ReportSnapshot& compiledDefinition, ReportSnapshot& snapshotData, Guid& linkID, DateTime& historyOrSnapshotDate, Byte[]& secDesc)
at Microsoft.ReportingServices.Library.RSService._GetReportParameters(ClientRequest session, String report, String historyID, Boolean forRendering, NameValueCollection values, DatasourceCredentialsCollection credentials)
at Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters)
at Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames)
at Microsoft.ReportingServices.Library.RenderFirstCancelableStep.Execute()
at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
End of inner exception stack trace
at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
at Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RSService rs, CatalogItemContext reportContext, ClientRequest session, JobType type, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames)
at Microsoft.ReportingServices.WebServer.ReportingService.Render(String Report, String Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters, DataSourceCredentials[] Credentials, String ShowHideToggle, Byte[]& Result, String& Encoding, String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings, String[]& StreamIds)
End of inner exception stack trace
at Microsoft.ReportingServices.WebServer.ReportingService.Render(String Report, String Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters, DataSourceCredentials[] Credentials, String ShowHideToggle, Byte[]& Result, String& Encoding, String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings, String[]& StreamIds)

Thanks,
Prabu

That means that you are trying to authenticate to reportserver with the user 'PPCCWDDC450P81\IUSR_PPCCWDDC450P81, this is an anonymous user that ASPNET uses for executing applications, you only have to add this user to the reportfolder or report item and give permissions of browser.sql

Monday, March 12, 2012

Password validation failed

Hello Group,
we got the following message when running execute sp_adduser
Server: Msg 15118, Level 16, State 1, Line 1
Password validation failed. The password does not meet Windows policy
requirements because it is not complex enough.
Server: Msg 15007, Level 16, State 1, Procedure sp_adduser, Line 15
is there a way to turn this off on sql server(2005sp2) level.
Thanks in advancedTal shalom
Firstv of all in SQL Server 2005 using CREATE USER ... is recommended way
instead of sp_adduser.
Now regarding to the error you are getting, it is because you created LOGIN
with 'weak' password.
Please run in query builder (take a look at CHECK_POLICY=OFF parameter in
the BOL)
create login tal with password ='t',
go
create user Joe for login tal
drop user joe
drop login tal
"Tal Bar-Or" <tal_baror@.hotmail.com> wrote in message
news:%23sZnW6gkHHA.3452@.TK2MSFTNGP04.phx.gbl...
> Hello Group,
> we got the following message when running execute sp_adduser
> Server: Msg 15118, Level 16, State 1, Line 1
> Password validation failed. The password does not meet Windows policy
> requirements because it is not complex enough.
> Server: Msg 15007, Level 16, State 1, Procedure sp_adduser, Line 15
> is there a way to turn this off on sql server(2005sp2) level.
> Thanks in advanced
>
>
>
>|||Shalom Uri,
Thanks for the answer. I understand that CHECK_POLICY=OFF can be done per
individual login . However can it be done on the SERVER level for ALL
logins. This would help us not nodify the
code when migrationg from SQL 2000 to SQL 2005
Thanks in advanced
Tal,
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eApc3BhkHHA.2272@.TK2MSFTNGP02.phx.gbl...
> Tal shalom
> Firstv of all in SQL Server 2005 using CREATE USER ... is recommended
> way instead of sp_adduser.
> Now regarding to the error you are getting, it is because you created
> LOGIN with 'weak' password.
> Please run in query builder (take a look at CHECK_POLICY=OFF parameter in
> the BOL)
> create login tal with password ='t',
> go
> create user Joe for login tal
> drop user joe
> drop login tal
>
>
> "Tal Bar-Or" <tal_baror@.hotmail.com> wrote in message
> news:%23sZnW6gkHHA.3452@.TK2MSFTNGP04.phx.gbl...
>|||Hi Tal
By default CHECK_POLICY=ON.CHECK_POLICY are only enforced on Windows Server
2003 so I have no idea how to change it .
"Tal Bar-Or" <tal_baror@.hotmail.com> wrote in message
news:%23n$ddThkHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Shalom Uri,
> Thanks for the answer. I understand that CHECK_POLICY=OFF can be done per
> individual login . However can it be done on the SERVER level for ALL
> logins. This would help us not nodify the
> code when migrationg from SQL 2000 to SQL 2005
> Thanks in advanced
> Tal,
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:eApc3BhkHHA.2272@.TK2MSFTNGP02.phx.gbl...
>