Log on server error

Hi all i am using crystal report with asp .net.

i am using report files already created an configured with a dsn.

when i try to view the report using crystal report viewer in a web form i am getting the error

"CrystalDecisions.CrystalReports.Engine.LogOnException: Logon failed."

i am using

<code>
ConnectionInfo cnnInfo = new ConnectionInfo ( ) ;

cnnInfo.ServerName = strConnInformation[0] ;
cnnInfo.DatabaseName = strConnInformation[1] ;
cnnInfo.UserID = strConnInformation[2] ;
cnnInfo.Password = strConnInformation[3] ;

ReportDocument rptDoc = new ReportDocument ( ) ;
rptDoc.Load ( Server.MapPath ( "..//Reports//" + reportFileName ),
OpenReportMethod.OpenReportByDefault ) ;

//CrystalDecisions.CrystalReports.Engine.Table table = rptDoc.Database.Tables[0] ;

CrystalDecisions.CrystalReports.Engine.Tables rptTables = rptDoc.Database.Tables ;
foreach ( CrystalDecisions.CrystalReports.Engine.Table tbl in rptTables )
{
tblLogOnInfo = tbl.LogOnInfo ;
tblLogOnInfo.ConnectionInfo = cnnInfo ;
tbl.ApplyLogOnInfo ( tblLogOnInfo ) ;

if ( tbl.Location.IndexOf ( "." ) > 0 )
{
tbl.Location = tbl.Location.Substring (
tbl.Location.LastIndexOf(".") + 1 ) ;
}
else
{
//tbl.Location = tbl.Location ;
}
}

</code>

its working fine when i try to execute a report file which configured direct to a database in another machine by specifying the server name, database name, user id and the password,

its showing the error only when i try to execute the report which configured using dsn. dsn is created in my machine and the actual database server is another one.

can any one help me in this matter as i have to use the reports with dsn only in my application.

i got the informations from the net that its same for both type of connectivity to use the ConnectionInfo object and the TableLogonInfo objects.

what my be the problem with me.

is its related to any permision issues.Hai Vinod,

Even i faced the same problem with my C# and Access .
But this prblem arised only when i have a subreport in my main report.

Do u have any subreports in ur appli...If so u have to provide login information to those reports also.

regards,
Kolluru.|||Thanks for your reply kolluru. i will try this and will get back :)|||Do u have any subreports in ur appli...If so u have to provide login information to those reports also.

Im having the same problem and I have subreports. How do you provide the login details for the subreports?sql

Log file not growing

I have a Db that is 3.8Gb and a log file that is 1mb the
log file does not grow. The db is setup with simple
recovery and the log file is configured to autogrow by
10%. Users are complaining that the DB is slow. My
hardware on this server is: 2 pentium xeon's with 4Gb of
ram 2 raid controllers 1 running raid 1 for the OS and
the other Raid 5 for the DB.In simple recovery mode the log is automatically truncated every time a
checkpoint occurs ( default every minute)... So the log will never get
larger than the longest running transaction..
"Carlos Santos" <anonymous@.discussions.microsoft.com> wrote in message
news:1b96f01c4209d$7352d860$a101280a@.phx
.gbl...
> I have a Db that is 3.8Gb and a log file that is 1mb the
> log file does not grow. The db is setup with simple
> recovery and the log file is configured to autogrow by
> 10%. Users are complaining that the DB is slow. My
> hardware on this server is: 2 pentium xeon's with 4Gb of
> ram 2 raid controllers 1 running raid 1 for the OS and
> the other Raid 5 for the DB.|||Thanks,
>--Original Message--
>In simple recovery mode the log is automatically
truncated every time a
>checkpoint occurs ( default every minute)... So the log
will never get
>larger than the longest running transaction..
>"Carlos Santos" <anonymous@.discussions.microsoft.com>
wrote in message
> news:1b96f01c4209d$7352d860$a101280a@.phx
.gbl...
the
of
>
>.
>

Log file not growing

I have a Db that is 3.8Gb and a log file that is 1mb the
log file does not grow. The db is setup with simple
recovery and the log file is configured to autogrow by
10%. Users are complaining that the DB is slow. My
hardware on this server is: 2 pentium xeon's with 4Gb of
ram 2 raid controllers 1 running raid 1 for the OS and
the other Raid 5 for the DB.In simple recovery mode the log is automatically truncated every time a
checkpoint occurs ( default every minute)... So the log will never get
larger than the longest running transaction..
"Carlos Santos" <anonymous@.discussions.microsoft.com> wrote in message
news:1b96f01c4209d$7352d860$a101280a@.phx.gbl...
> I have a Db that is 3.8Gb and a log file that is 1mb the
> log file does not grow. The db is setup with simple
> recovery and the log file is configured to autogrow by
> 10%. Users are complaining that the DB is slow. My
> hardware on this server is: 2 pentium xeon's with 4Gb of
> ram 2 raid controllers 1 running raid 1 for the OS and
> the other Raid 5 for the DB.|||Thanks,
>--Original Message--
>In simple recovery mode the log is automatically
truncated every time a
>checkpoint occurs ( default every minute)... So the log
will never get
>larger than the longest running transaction..
>"Carlos Santos" <anonymous@.discussions.microsoft.com>
wrote in message
>news:1b96f01c4209d$7352d860$a101280a@.phx.gbl...
>> I have a Db that is 3.8Gb and a log file that is 1mb
the
>> log file does not grow. The db is setup with simple
>> recovery and the log file is configured to autogrow by
>> 10%. Users are complaining that the DB is slow. My
>> hardware on this server is: 2 pentium xeon's with 4Gb
of
>> ram 2 raid controllers 1 running raid 1 for the OS and
>> the other Raid 5 for the DB.
>
>.
>sql

Log file not growing

I have a Db that is 3.8Gb and a log file that is 1mb the
log file does not grow. The db is setup with simple
recovery and the log file is configured to autogrow by
10%. Users are complaining that the DB is slow. My
hardware on this server is: 2 pentium xeon's with 4Gb of
ram 2 raid controllers 1 running raid 1 for the OS and
the other Raid 5 for the DB.
In simple recovery mode the log is automatically truncated every time a
checkpoint occurs ( default every minute)... So the log will never get
larger than the longest running transaction..
"Carlos Santos" <anonymous@.discussions.microsoft.com> wrote in message
news:1b96f01c4209d$7352d860$a101280a@.phx.gbl...
> I have a Db that is 3.8Gb and a log file that is 1mb the
> log file does not grow. The db is setup with simple
> recovery and the log file is configured to autogrow by
> 10%. Users are complaining that the DB is slow. My
> hardware on this server is: 2 pentium xeon's with 4Gb of
> ram 2 raid controllers 1 running raid 1 for the OS and
> the other Raid 5 for the DB.
|||Thanks,
>--Original Message--
>In simple recovery mode the log is automatically
truncated every time a
>checkpoint occurs ( default every minute)... So the log
will never get
>larger than the longest running transaction..
>"Carlos Santos" <anonymous@.discussions.microsoft.com>
wrote in message
>news:1b96f01c4209d$7352d860$a101280a@.phx.gbl...
the
of
>
>.
>

locks preventing backup of database

The database is configured for single publisher, many subscribers,
merge replication. The maintenance plan started to fail a couple of
months ago and the database would not get backed up. After clearing
all the locks, I am able to backup the database manually. The locks
return again and I'm not able to backup the database with the
maintenance plan. How can I get around the lock issue or solve it so
that I can backup the database again?

Thanks,
Chris"cloverme" <ads4sms@.yahoo.com> wrote in message
news:fe5c75a8.0401071659.5b96ba2c@.posting.google.c om...
> The database is configured for single publisher, many subscribers,
> merge replication. The maintenance plan started to fail a couple of
> months ago and the database would not get backed up. After clearing
> all the locks, I am able to backup the database manually. The locks
> return again and I'm not able to backup the database with the
> maintenance plan. How can I get around the lock issue or solve it so
> that I can backup the database again?

How are you trying to back it up? I've never seen locks prevent a db
backup.

> Thanks,
> Chris