logshipping load failure

Hi Guys,
I implemented log shipping but if database is open during
load the restore is failing.
i think i selected "terminate users in database" option.
how i can confirm whether i selected this option? and if
not how can i change this.
THNKS
BIJU
Biju,
the easiest way to check and change this property is to edit the maintenance
plan, goto the logshipping tab and edit, on the initialize tab select
'Terminate Users in Database'.
HTH,
Paul Ibison

Log-shipping failure

Hi All,
sql server 2000 enterprise edition, 8.00.760
Am trying to set logs-shipping between two databases on two different servers on the same domain. Am using same sql server agent account for both the servers.
After log-shipping is configured, am able to see the transaction logs being backed up in the primary server, then copied on to the secondary server folder. But when it is trying to restore the transaction logs on the secondary server, I get the following
error:
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029).
FYI, We are using compatibility level of 65 on the primary server, as this is how we want it. But I can change the compatibility level on secondary server to 80 (if its a must). Am wondering, if this is one of the reason for failure.
More information:
I have confugured it to restore in STANDBY mode and terminate any user connections. And the secondary server is used for monitoring log shipping activities.
Has anybody faced similar problem? Please advise
Thanks much
GYK
> Hi All,
> sql server 2000 enterprise edition, 8.00.760
> Am trying to set logs-shipping between two databases on two
> different servers on the same domain. Am using same sql server
> agent account for both the servers.
> After log-shipping is configured, am able to see the transaction
> logs being backed up in the primary server, then copied on to
> the secondary server folder. But when it is trying to restore the
> transaction logs on the secondary server, I get the following error:
> sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029).
> FYI, We are using compatibility level of 65 on the primary server,
> as this is how we want it. But I can change the compatibility
> level on secondary server to 80 (if its a must). Am wondering,
> if this is one of the reason for failure.
> More information:
> I have confugured it to restore in STANDBY mode and terminate
> any user connections. And the secondary server is used for
> monitoring log shipping activities.
> Has anybody faced similar problem? Please advise
> Thanks much
> GYK
Check that the sql server agent account has enough permissions on the
secondary server.
Run the sqlmaint with the parameters from the command-line and see what
errors are returned.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Log-shipping failure

Hi All,
sql server 2000 enterprise edition, 8.00.760
Am trying to set logs-shipping between two databases on two different server
s on the same domain. Am using same sql server agent account for both the se
rvers.
After log-shipping is configured, am able to see the transaction logs being
backed up in the primary server, then copied on to the secondary server fold
er. But when it is trying to restore the transaction logs on the secondary s
erver, I get the following
error:
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029).
FYI, We are using compatibility level of 65 on the primary server, as this i
s how we want it. But I can change the compatibility level on secondary serv
er to 80 (if its a must). Am wondering, if this is one of the reason for fai
lure.
More information:
I have confugured it to restore in STANDBY mode and terminate any user conne
ctions. And the secondary server is used for monitoring log shipping activit
ies.
Has anybody faced similar problem? Please advise
Thanks much
GYK> Hi All,
> sql server 2000 enterprise edition, 8.00.760
> Am trying to set logs-shipping between two databases on two
> different servers on the same domain. Am using same sql server
> agent account for both the servers.
> After log-shipping is configured, am able to see the transaction
> logs being backed up in the primary server, then copied on to
> the secondary server folder. But when it is trying to restore the
> transaction logs on the secondary server, I get the following error:
> sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029).
> FYI, We are using compatibility level of 65 on the primary server,
> as this is how we want it. But I can change the compatibility
> level on secondary server to 80 (if its a must). Am wondering,
> if this is one of the reason for failure.
> More information:
> I have confugured it to restore in STANDBY mode and terminate
> any user connections. And the secondary server is used for
> monitoring log shipping activities.
> Has anybody faced similar problem? Please advise
> Thanks much
> GYK
--
Check that the sql server agent account has enough permissions on the
secondary server.
Run the sqlmaint with the parameters from the command-line and see what
errors are returned.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Logon failure?

Hello,
We just installed SQL Server developer's edition on a new Windows XP Pro
workstation. But whenever we bring up the SQL Server service manager, and
click Start, we get the error:
"The service did not start due to logon failure"
When we did the install, we left the "sa" password blank, and we're using
SQL Server authentication. Can anyone say what might be wrong?
Thanks!!
It's most likely the Windows account that starts up the SQL Server
service. The password is probably expired. Check your SQL
Server Service log on credentials
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL Server developer's edition on a new Windows XP Pro
> workstation. But whenever we bring up the SQL Server service manager, and
> click Start, we get the error:
> "The service did not start due to logon failure"
> When we did the install, we left the "sa" password blank, and we're using
> SQL Server authentication. Can anyone say what might be wrong?
> Thanks!!
>
|||Oh, by the way... USE A STRONG PASSWORD FOR 'sa'!!!!
Don't use blanks; a lot of SQL Server exploits use a brute force method
to compromise a system. They'll check for passwords such 'sa' or blank.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL Server developer's edition on a new Windows XP Pro
> workstation. But whenever we bring up the SQL Server service manager, and
> click Start, we get the error:
> "The service did not start due to logon failure"
> When we did the install, we left the "sa" password blank, and we're using
> SQL Server authentication. Can anyone say what might be wrong?
> Thanks!!
>
|||Oh yes, for server deployments of SQL Server, we always use strong
passwords, but the workstation in question is at a home office, and not
connected to the Internet. Thanks!
"Armando Prato" <aprato@.REMOVEMEkronos.com> wrote in message
news:O#ZOgN1dFHA.3836@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Oh, by the way... USE A STRONG PASSWORD FOR 'sa'!!!!
> Don't use blanks; a lot of SQL Server exploits use a brute force method
> to compromise a system. They'll check for passwords such 'sa' or blank.
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
and[vbcol=seagreen]
using
>

Logon failure?

Hello,
We just installed SQL Server developer's edition on a new Windows XP Pro
workstation. But whenever we bring up the SQL Server service manager, and
click Start, we get the error:
"The service did not start due to logon failure"
When we did the install, we left the "sa" password blank, and we're using
SQL Server authentication. Can anyone say what might be wrong?
Thanks!!It's most likely the Windows account that starts up the SQL Server
service. The password is probably expired. Check your SQL
Server Service log on credentials
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL Server developer's edition on a new Windows XP Pro
> workstation. But whenever we bring up the SQL Server service manager, and
> click Start, we get the error:
> "The service did not start due to logon failure"
> When we did the install, we left the "sa" password blank, and we're using
> SQL Server authentication. Can anyone say what might be wrong?
> Thanks!!
>|||Oh, by the way... USE A STRONG PASSWORD FOR 'sa'!!!!
Don't use blanks; a lot of SQL Server exploits use a brute force method
to compromise a system. They'll check for passwords such 'sa' or blank.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL Server developer's edition on a new Windows XP Pro
> workstation. But whenever we bring up the SQL Server service manager, and
> click Start, we get the error:
> "The service did not start due to logon failure"
> When we did the install, we left the "sa" password blank, and we're using
> SQL Server authentication. Can anyone say what might be wrong?
> Thanks!!
>|||Oh yes, for server deployments of SQL Server, we always use strong
passwords, but the workstation in question is at a home office, and not
connected to the Internet. Thanks!
"Armando Prato" <aprato@.REMOVEMEkronos.com> wrote in message
news:O#ZOgN1dFHA.3836@.tk2msftngp13.phx.gbl...
> Oh, by the way... USE A STRONG PASSWORD FOR 'sa'!!!!
> Don't use blanks; a lot of SQL Server exploits use a brute force method
> to compromise a system. They'll check for passwords such 'sa' or blank.
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL Server developer's edition on a new Windows XP Pro
> > workstation. But whenever we bring up the SQL Server service manager,
and
> > click Start, we get the error:
> >
> > "The service did not start due to logon failure"
> >
> > When we did the install, we left the "sa" password blank, and we're
using
> > SQL Server authentication. Can anyone say what might be wrong?
> >
> > Thanks!!
> >
> >
>

Logon failure?

Hello,
We just installed SQL Server developer's edition on a new Windows XP Pro
workstation. But whenever we bring up the SQL Server service manager, and
click Start, we get the error:
"The service did not start due to logon failure"
When we did the install, we left the "sa" password blank, and we're using
SQL Server authentication. Can anyone say what might be wrong?
Thanks!!It's most likely the Windows account that starts up the SQL Server
service. The password is probably expired. Check your SQL
Server Service log on credentials
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL Server developer's edition on a new Windows XP Pro
> workstation. But whenever we bring up the SQL Server service manager, and
> click Start, we get the error:
> "The service did not start due to logon failure"
> When we did the install, we left the "sa" password blank, and we're using
> SQL Server authentication. Can anyone say what might be wrong?
> Thanks!!
>|||Oh, by the way... USE A STRONG PASSWORD FOR 'sa'!!!!
Don't use blanks; a lot of SQL Server exploits use a brute force method
to compromise a system. They'll check for passwords such 'sa' or blank.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL Server developer's edition on a new Windows XP Pro
> workstation. But whenever we bring up the SQL Server service manager, and
> click Start, we get the error:
> "The service did not start due to logon failure"
> When we did the install, we left the "sa" password blank, and we're using
> SQL Server authentication. Can anyone say what might be wrong?
> Thanks!!
>|||Oh yes, for server deployments of SQL Server, we always use strong
passwords, but the workstation in question is at a home office, and not
connected to the Internet. Thanks!
"Armando Prato" <aprato@.REMOVEMEkronos.com> wrote in message
news:O#ZOgN1dFHA.3836@.tk2msftngp13.phx.gbl...
> Oh, by the way... USE A STRONG PASSWORD FOR 'sa'!!!!
> Don't use blanks; a lot of SQL Server exploits use a brute force method
> to compromise a system. They'll check for passwords such 'sa' or blank.
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:OfpH2J1dFHA.1136@.TK2MSFTNGP12.phx.gbl...
and[vbcol=seagreen]
using[vbcol=seagreen]
>

Logon failure: the user has not been granted the requested logon t

I get the following error when I try running a report using Reporting
Services 2005. The Data Source gets to SQL Server using a domain account. The
Application Pool is running under NETWORK SERVICE.
I see a lot of postings about allowing for Logon Locally. I am sure this
could fix the issue, but why is that standard practice? I don't allow that
for impersonating a user in a standard web application (with web.config --
impersonate user).
===== Error ========= An error has occurred during report processing.
Cannot impersonate user for data source 'DataSourceName'.
Logon failed.
Logon failure: the user has not been granted the requested logon type at
this computer. (Exception from HRESULT: 0x80070569)We don't use logon locally rights...
Instead, we grant NETWORK SERVICE account the right to connect to the SQL
Server database (the specific database) instead.
Some administrators would flip out if they had to change their local
security policy. At least as a DBA I can make this change without having to
involve layers of people to get it implemented.
=-Chris
"Sanjay T" <SanjayT@.discussions.microsoft.com> wrote in message
news:2D831614-9BF9-4C7A-B290-13A1DCD23498@.microsoft.com...
>I get the following error when I try running a report using Reporting
> Services 2005. The Data Source gets to SQL Server using a domain account.
> The
> Application Pool is running under NETWORK SERVICE.
> I see a lot of postings about allowing for Logon Locally. I am sure this
> could fix the issue, but why is that standard practice? I don't allow that
> for impersonating a user in a standard web application (with web.config --
> impersonate user).
>
> ===== Error =========> An error has occurred during report processing.
> Cannot impersonate user for data source 'DataSourceName'.
> Logon failed.
> Logon failure: the user has not been granted the requested logon type at
> this computer. (Exception from HRESULT: 0x80070569)

Logon Failure when executing report

I'm using RS 2005. I created a report that works fine in Visual Studio
and I can deploy it to the report server without any errors. But when
I try to execute the report in the Report Manager or by using a URL, I
get the following error: Logon Failed: unknown user name or bad
password. I have the default security settings for the report (Builtin
Administrators Group only). I am logged on as a domain administrator
when I try to run the report. What logon is the error referring to?
Thanks in advance for any help.How do you authenticate against your datasource?
What happens if you try it from a different computer?
If you are using NT authentication in your datasource, check what user you
are running the report as. One way is by adding your report site to Trusted
SItes in IE (Internet Options -Security) and then set Always prompt for
username and password in the Security Settings.
Kaisa M. Lindahl
"dba56" <lvigorito@.berdonllp.com> wrote in message
news:1137038010.522621.70160@.o13g2000cwo.googlegroups.com...
> I'm using RS 2005. I created a report that works fine in Visual Studio
> and I can deploy it to the report server without any errors. But when
> I try to execute the report in the Report Manager or by using a URL, I
> get the following error: Logon Failed: unknown user name or bad
> password. I have the default security settings for the report (Builtin
> Administrators Group only). I am logged on as a domain administrator
> when I try to run the report. What logon is the error referring to?
> Thanks in advance for any help.
>|||Thanks for the quick response. It turned out to be the execution
account. Don't know why it needs to log on with the execution account
when executing a report. But once I entered the correct login and
password for the execution account in the configuration utility,
reports run without any glitches.|||Hi
I've the same problem when executing my report from the Report Manager. It
works fine in the development tool though.
I run my report under almost the same conditions as you did, i.e
- as a local admin on the test server (Report Service and source database on
the same machine, the development tool to)
- The data source is set the SQL authentication and I have gone as far as
using the sa login
- In the config manager I have updated the Sevice to run as a local user
which is a member of the admin group and the two ReportinServices groups.
I still get the "log in failure". What more is there to do?
/Jesper
"dba56" wrote:
> Thanks for the quick response. It turned out to be the execution
> account. Don't know why it needs to log on with the execution account
> when executing a report. But once I entered the correct login and
> password for the execution account in the configuration utility,
> reports run without any glitches.
>

Logon failure in sql server 2000

Hi every one
I have got a problem with my Ms SQL Server: I have defined a server and
in the server i am running a rainbow portal, however i cant get my
rainbow working because it says that SQL does not exist or access
denied. I checked me services for sql and it gives a message saying
the following "Could not start the MSSQL... Service on Local
Computer... Error 1069: The service did not start due to logon
failure." Aparently i am logged in as the administrator in the server,
so i don=B4t understand why this is happening. If anyone can give some
inputs on that i will highly appreciate.
Thanks in advance for any help
ErnestoEmesto,
What account MSSQL service run on the machine? You can check it from
the Services control panel. If it is not run as 'local system', which
is by default, then make sure that account is a member of local
administrator.
Mel|||In Services go to property of that server , go to logon tab and apply
new password for that account.
Make sure that account is not locked.
Make sure that account is member of administrator group
Regards
Amish Shah

Logon failure in sql server 2000

Hi every one
I have got a problem with my Ms SQL Server: I have defined a server and
in the server i am running a rainbow portal, however i cant get my
rainbow working because it says that SQL does not exist or access
denied. I checked me services for sql and it gives a message saying
the following "Could not start the MSSQL... Service on Local
Computer... Error 1069: The service did not start due to logon
failure." Aparently i am logged in as the administrator in the server,
so i don=B4t understand why this is happening. If anyone can give some
inputs on that i will highly appreciate.
Thanks in advance for any help
ErnestoEmesto,
What account MSSQL service run on the machine? You can check it from
the Services control panel. If it is not run as 'local system', which
is by default, then make sure that account is a member of local
administrator.
Mel|||In Services go to property of that server , go to logon tab and apply
new password for that account.
Make sure that account is not locked.
Make sure that account is member of administrator group
Regards
Amish Shah

Logon failure executing reports in SRS2005

Environment: Application server with WS2003, IIS 6.0 and Reporting Services
2005; Database server with WS2003 and SQL Server 2005.
Each time I want to execure a report I get the following error message:
Logon failed. -->
Logon failure: the user has not been granted the requested logon type at
this computer. (Exception from HRESULT: 0x80070569)
Reporting Services Configuration tool does not show any errors.
Web Service and Windows Service identity both use NT AUTHPORITY/NETWORK
SERVICE.
Database Connection uses sa.
It does not make any difference from where I execute the report, application
server, client, Report Manager, Report Builder, always the same login
fauilure.What user is the Application Pool for the report virtual directories running
under?
I did have lots of problems with a RS server where someone had used a domain
user as the identity for the application pool. This domain user did not have
the access rigth to "Log on as a service", which was needed. I changed the
identity to run as network service, and all the errors went away. Might help
for you as well.
Kaisa M. Lindahl Lervik
"ChrisWF" <ChrisWF@.discussions.microsoft.com> wrote in message
news:0E9D8B8F-2A31-4731-B7B0-9F7D6348D3A1@.microsoft.com...
> Environment: Application server with WS2003, IIS 6.0 and Reporting
> Services
> 2005; Database server with WS2003 and SQL Server 2005.
> Each time I want to execure a report I get the following error message:
> Logon failed. -->
> Logon failure: the user has not been granted the requested logon type at
> this computer. (Exception from HRESULT: 0x80070569)
> Reporting Services Configuration tool does not show any errors.
> Web Service and Windows Service identity both use NT AUTHPORITY/NETWORK
> SERVICE.
> Database Connection uses sa.
> It does not make any difference from where I execute the report,
> application
> server, client, Report Manager, Report Builder, always the same login
> fauilure.|||They run under the Network Service account.
But your response triggered me to check once more the execution account (a
domain account) I use to perform unattended operations. When I added this
account to the administrators group it worked. Probably not the right
solution but at least I could move on with the testing.
Thanks,
Chris
"Kaisa M. Lindahl Lervik" wrote:
> What user is the Application Pool for the report virtual directories running
> under?
> I did have lots of problems with a RS server where someone had used a domain
> user as the identity for the application pool. This domain user did not have
> the access rigth to "Log on as a service", which was needed. I changed the
> identity to run as network service, and all the errors went away. Might help
> for you as well.
> Kaisa M. Lindahl Lervik
> "ChrisWF" <ChrisWF@.discussions.microsoft.com> wrote in message
> news:0E9D8B8F-2A31-4731-B7B0-9F7D6348D3A1@.microsoft.com...
> > Environment: Application server with WS2003, IIS 6.0 and Reporting
> > Services
> > 2005; Database server with WS2003 and SQL Server 2005.
> >
> > Each time I want to execure a report I get the following error message:
> >
> > Logon failed. -->
> > Logon failure: the user has not been granted the requested logon type at
> > this computer. (Exception from HRESULT: 0x80070569)
> >
> > Reporting Services Configuration tool does not show any errors.
> > Web Service and Windows Service identity both use NT AUTHPORITY/NETWORK
> > SERVICE.
> > Database Connection uses sa.
> >
> > It does not make any difference from where I execute the report,
> > application
> > server, client, Report Manager, Report Builder, always the same login
> > fauilure.
>
>

logon failure error in Reporting Services (rskeymgmt error)

Hi,
I have Reporting Services 2000 installed and I have a remote report server
database.
The Report Server is configured to use a domain user account to connect to
the report server database.
The password of the domain user account is changed a few days ago and I
updated the ReportServerConfig using rsconfig utility.
But, I am still getting the error logon failed error :
â'The report server cannot open a connection to the report server database.
The logon failed. (rsReportServerDatabaseLogonFailed) Get Online Help
Logon failure: unknown user name or bad password.
When I tried to take a backup (extract) of the existing symmetric keys using
rskeymgmt utility, I get the error, unable to connect to the database.
Can somebody provide me the resolution? Can I delete the keys without taking
a backup?
Thanks,
MujirDid you get this resolved we are experiencing the same thing?
"Mujir" wrote:
> Hi,
>
> I have Reporting Services 2000 installed and I have a remote report server
> database.
> The Report Server is configured to use a domain user account to connect to
> the report server database.
>
> The password of the domain user account is changed a few days ago and I
> updated the ReportServerConfig using rsconfig utility.
> But, I am still getting the error logon failed error :
> â'The report server cannot open a connection to the report server database.
> The logon failed. (rsReportServerDatabaseLogonFailed) Get Online Help
> Logon failure: unknown user name or bad password.
>
> When I tried to take a backup (extract) of the existing symmetric keys using
> rskeymgmt utility, I get the error, unable to connect to the database.
> Can somebody provide me the resolution? Can I delete the keys without taking
> a backup?
>
> Thanks,
> Mujir
>|||Not exactly, I configured it to use a different account and it works now.
"OriginalStealth" wrote:
> Did you get this resolved we are experiencing the same thing?
> "Mujir" wrote:
> > Hi,
> >
> >
> >
> > I have Reporting Services 2000 installed and I have a remote report server
> > database.
> >
> > The Report Server is configured to use a domain user account to connect to
> > the report server database.
> >
> >
> >
> > The password of the domain user account is changed a few days ago and I
> > updated the ReportServerConfig using rsconfig utility.
> >
> > But, I am still getting the error logon failed error :
> >
> > â'The report server cannot open a connection to the report server database.
> > The logon failed. (rsReportServerDatabaseLogonFailed) Get Online Help
> >
> > Logon failure: unknown user name or bad password.
> >
> >
> >
> > When I tried to take a backup (extract) of the existing symmetric keys using
> > rskeymgmt utility, I get the error, unable to connect to the database.
> >
> > Can somebody provide me the resolution? Can I delete the keys without taking
> > a backup?
> >
> >
> > Thanks,
> > Mujir
> >

Logon Failure during exporting

Using Crystal Report for VS.Net in one of my .Net project, to connect to Oracle database "myDB" to generate a report. Things seems OK till it hits the "ExportToDisk" method, and gave me a "Logon Failure" exception.

Googled around and somebody said that I have to use "setDatabaseLogon()" method to set the uid/pass during runtime. So I did but it still didn't work.

Here's my source code, hope somebody could shed some light on this. Thanks !

******************************
"myConnection" is an estabilished OleDbConnection that was used repeatedly through the project. "dsTemp" is a dataset
******************************
Dim rptWKIT As New crWKIT()
Dim exportFileName As String = "exportedReport.rpt"
Dim exportPath As String = Application.StartupPath & "\" & exportFileName

Try
dsTemp.Clear()
Dim myDA As New OleDb.OleDbDataAdapter()
Dim myCmd As New OleDb.OleDbCommand()
myCmd.Connection = myConnection
myCmd.CommandText = "SELECT * FROM WKIT"
myCmd.CommandType = CommandType.Text
myDA.SelectCommand() = myCmd
myDA.Fill(dsTemp, "WKIT")

rptWKIT.SetDataSource(dsTemp)
rptWKIT.SetDatabaseLogon(sUser, sPass)
rptWKIT.Load()

rptWKIT.ExportToDisk(ExportFormatType.RichText, exportPath)
Catch x As Exception
MessageBox.Show(x.Message + x.Source + x.StackTrace, "Report Error", MessageBoxButtons.OK, MessageBoxIcon.Error)
End TrySee if you find asnwer here
http://support.businessobjects.com/|||Thanks. I just figured this out... after the rptWKIT.SetDataSource(dsTemp), there's no need to do the next 2 steps:

rptWKIT.SetDatabaseLogon(sUser, sPass)
rptWKIT.Load()

It can just export without any problem. But when do Load() again, guess CR is confused...|||Glad to know you sorted it out :)

Logon failure : (rsInternalError)

On a SQL server 2000 SP4 on XP PRO SP2, I have installed Reporting Services.
I have created an local administrator user and I have given this local
account as "Domain user Account" during installation.
When I try to acces report server, it fails with the message "Logon failure:
unknown user name or bad password. "
In the logfile of Reporting services, I read these informations :
aspnet_wp!library!690!02/03/2006-16:24:09:: i INFO: Call to GetPermissions:/
aspnet_wp!crypto!690!02/03/2006-16:24:09:: i INFO: Initializing crypto as
user: U000103096\ASPNET
aspnet_wp!crypto!690!02/03/2006-16:24:09:: i INFO: Exporting public key
aspnet_wp!library!690!02/03/2006-16:24:10:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
Une erreur interne s'est produite sur le serveur de rapports. Pour plus
d'informations, consultez le journal des erreurs., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
Une erreur interne s'est produite sur le serveur de rapports. Pour plus
d'informations, consultez le journal des erreurs. -->
System.Runtime.InteropServices.COMException (0x8007052E): Logon failure:
unknown user name or bad password.
Can somebody help me to solve this problem ? Thanks for allHi Gaby,
Welcome to the MSDN newsgroup.
From your description, I understand you have installed SQL Server 2000(with
reporting service) on a Windows XP SP2 machine. Also, during the
installation time, you configured the Reporting Service to use a certain
domain account which has been granted the "Local Administrator" role.
However, when you try accessing the report server application, it threw the
following exception:
"Logon failure: unknown user name or bad password. " ,correct?
Based on the log file content you provided, the error occured when the
report server try performing some security operations like reading account
info. I've also checked the error and find some reference in MSDN on the
similiar problem. Are you try viewing a report which use external
datasource and use prompted or stored Windows credentials to connect to the
external datasource? If so, you can have a look at the following
troubleshooting article, and the below section
"Connection error, where login failed for <servername>\ASPNET"
is describing the similiar problem as yours.
#Troubleshooting Server and Database Problems
http://msdn.microsoft.com/library/en-us/rstshoot/htm/trs_tshootdev_v1_3dcz.a
sp?frame=true
Please feel free to post here if there's anything else we can help.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi Steven
Thank you for your help but I am sorry to say that your recommendations
didn't work on my PC
I have just installed an SQL Server on my windows XP (SQL server 2000 + SP4)
and the Reporting Services (+ service pack 2). After that, before making any
own report, I have just tried to contact the report server, on this PC, in
an IE5 session with the address : localhost\reports. And then I have received
the error message : logon failed !!
My PC is an "entreprise PC", this a lot of components "masterised" in a
"logically gathered software" and I think that perhaps some authorizations
are not correctly installed for my requirements, but I don't know where I
have to search !!
"Steven Cheng[MSFT]" wrote:
> Hi Gaby,
> Welcome to the MSDN newsgroup.
> From your description, I understand you have installed SQL Server 2000(with
> reporting service) on a Windows XP SP2 machine. Also, during the
> installation time, you configured the Reporting Service to use a certain
> domain account which has been granted the "Local Administrator" role.
> However, when you try accessing the report server application, it threw the
> following exception:
> "Logon failure: unknown user name or bad password. " ,correct?
> Based on the log file content you provided, the error occured when the
> report server try performing some security operations like reading account
> info. I've also checked the error and find some reference in MSDN on the
> similiar problem. Are you try viewing a report which use external
> datasource and use prompted or stored Windows credentials to connect to the
> external datasource? If so, you can have a look at the following
> troubleshooting article, and the below section
> "Connection error, where login failed for <servername>\ASPNET"
> is describing the similiar problem as yours.
> #Troubleshooting Server and Database Problems
> http://msdn.microsoft.com/library/en-us/rstshoot/htm/trs_tshootdev_v1_3dcz.a
> sp?frame=true
> Please feel free to post here if there's anything else we can help.
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>
>
>
>
>|||Thanks for your response Gaby,
So the problem is somewhat different from that mentioned in the doc. Since
the error stack shows there is some login fail error and also mentioend the
MACHINE\ASPNET account, I think you can try the followings to see whether
it is concerned with account permission:
1. Change the reporting service windows service's identity from the current
account( the one you specified during setup) to Local System.
2. Temporarlily Add the ASP.NET process account (machine\ASPNET) into
local administrators group or just replace the ASP.NET process account
from "Machine" to "SYSTEM", this can be set in the .net framework's
machine.config(under C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\CONFIG)
After that, restart reporting service to see whether it work.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Thank you for your help. At the end, it works. I have just modified the
machine.config file of the current version of the framework (in the CONFIG
Folder), and change, in the processModel parameter, the value of the userName
parameter, from "machine" to "SYSTEM".
By stopping and restarting only the reporting service and the IIS server,
this modification don't work but after the "total reboot" of my computer, all
is OK and I can now see the contents of the folder in the Reports Server
Thank you for all (and I hope that our discussion can help other persons)
"Steven Cheng[MSFT]" wrote:
> Thanks for your response Gaby,
> So the problem is somewhat different from that mentioned in the doc. Since
> the error stack shows there is some login fail error and also mentioend the
> MACHINE\ASPNET account, I think you can try the followings to see whether
> it is concerned with account permission:
> 1. Change the reporting service windows service's identity from the current
> account( the one you specified during setup) to Local System.
> 2. Temporarlily Add the ASP.NET process account (machine\ASPNET) into
> local administrators group or just replace the ASP.NET process account
> from "Machine" to "SYSTEM", this can be set in the .net framework's
> machine.config(under C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\CONFIG)
> After that, restart reporting service to see whether it work.
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>
>
>|||You're welcome Gaby,
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Logon failure

To get my reports to work from the 2005 Report Manager I had to put the
Execution Account into the Local Administrators Group, otherwise I got a
Logon Failoure message when attempting to view the report. Is this how it's
sipposed to be?Don't use anonymous access with windows authentication......
Kinda defeats the purpose.
"Jim Abel" <JimAbel@.discussions.microsoft.com> wrote in message
news:8453498E-99F8-43AA-8ADD-9005C6F2FF35@.microsoft.com...
> To get my reports to work from the 2005 Report Manager I had to put the
> Execution Account into the Local Administrators Group, otherwise I got a
> Logon Failoure message when attempting to view the report. Is this how
> it's
> sipposed to be?|||What do you mean about Anonymous access? In the Report Configuration page I
had a limited donain account set for the services and the execution account.
When a report was selected to be viewed a logon failure error resulted saying
that "The user has not been granted the requested logon type at this machine
"
I was unable to figure out how to change the requested logon type, so I
added the account to the Local Administrators group and I no longer got the
Logon failure error. Now I thought that Microsoft was attempting to secure
the way that things worked so that an account as in this case would not need
to have such elevated permissions. I am looking for information that can
explain what is required for an account to be able to execute reports when
requested and validation that they have to be in the Administrative group.
The anonymous caused me confusion because I don't see where it comes into
play.
Thanks
"Chris Taylor" wrote:
> Don't use anonymous access with windows authentication......
> Kinda defeats the purpose.
> "Jim Abel" <JimAbel@.discussions.microsoft.com> wrote in message
> news:8453498E-99F8-43AA-8ADD-9005C6F2FF35@.microsoft.com...
> > To get my reports to work from the 2005 Report Manager I had to put the
> > Execution Account into the Local Administrators Group, otherwise I got a
> > Logon Failoure message when attempting to view the report. Is this how
> > it's
> > sipposed to be?
>
>

Logon Failure

I have W2003 server with Sql running. User is trying to open a report from the database. It was working fine.
Message pops up stating:
The report server cannot open a connection to the report server database. The logon failed. (rsReportServerDatabaseLogonFailed) Get Online Help Logon failure: unknown user name or bad password. Any help would be appreciated.
i am also getting the same issue, if you got any solution please let me know|||I'm also getting the logon failed error when using a data driven subscription to the report and the query validation is succesful, anyone knows how to fix that?
|||

Cehck your data source connection. Make sure the account has enought permissions to access the database.

|||Tried it with sa account, the same error...

Logon failed when attempting to run report

When attempting to run a report, the following error appeared.
What does the following error message mean?
Logon failed.
Logon failure: unknown user name or bad password. (Exception from HRESULT:
0x8007052E)Looks like your report credentials are not set.
Go to Report Manager, navigate to the report, go to properties and make
sure your data sources are all correctly set up

login problems

After migrating SQL Server 2000 from NT to 2003, I have a login failure for
one user when trying to access a database.When I go to the user's login
properties, Database Access, I check the Permit box for the database for the
user and click OK.
I get an Microsoft SQL-DMO error message:
Error 21002:[SQL-DMO]User 'MW_DBA' already exists.
How can I fix this?
Antonin
Antonin
It sounds like your logins and User ID's have got out of synch. Try running
the following on the master database
EXEC sp_change_users_login 'Auto_Fix', 'MW_DBA'
Hope this helps
John
|||Hi John,
Thanks for your reply. I tried it and got this:
The number of orphaned users fixed by updating users was 0.
The number of orphaned users fixed by adding new logins and then updating
users was 0.
Antonin
"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:D9637F5C-58DF-4940-8E0F-9E4D2A507B51@.microsoft.com...
> Antonin
> It sounds like your logins and User ID's have got out of synch. Try
> running
> the following on the master database
> EXEC sp_change_users_login 'Auto_Fix', 'MW_DBA'
> Hope this helps
> John

login problems

After migrating SQL Server 2000 from NT to 2003, I have a login failure for
one user when trying to access a database.When I go to the user's login
properties, Database Access, I check the Permit box for the database for the
user and click OK.
I get an Microsoft SQL-DMO error message:
Error 21002:[SQL-DMO]User 'MW_DBA' already exists.
How can I fix this?
AntoninAntonin
It sounds like your logins and User ID's have got out of synch. Try running
the following on the master database
EXEC sp_change_users_login 'Auto_Fix', 'MW_DBA'
Hope this helps
John|||Hi John,
Thanks for your reply. I tried it and got this:
The number of orphaned users fixed by updating users was 0.
The number of orphaned users fixed by adding new logins and then updating
users was 0.
Antonin
"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:D9637F5C-58DF-4940-8E0F-9E4D2A507B51@.microsoft.com...
> Antonin
> It sounds like your logins and User ID's have got out of synch. Try
> running
> the following on the master database
> EXEC sp_change_users_login 'Auto_Fix', 'MW_DBA'
> Hope this helps
> John