Long running report fails with http error

Hi,
I have a report that takes about an hour to run. When I run it, it runs for
an hour or so with "Generating Report", then the result page is the standard
IE "Action Canceled" page, and there is a javascript error. The javascript
error is Permission denied.
All other reports running on this server (which don't take as long to run)
are fine. I've checked IIS settings and blown the connection timeout to 9000
seconds.
It's as if the report is taking too long...
I've set all the URL stuff in the config files, but like I say, its only one
out of about a hundred reports that is failing.
Any ideas?
SteveHi,
I think this is something to do with your queries some where it is not
optimized. Just check whether the same query / procedure runs in your
management studio.
Amarnath
"Steve" wrote:
> Hi,
> I have a report that takes about an hour to run. When I run it, it runs for
> an hour or so with "Generating Report", then the result page is the standard
> IE "Action Canceled" page, and there is a javascript error. The javascript
> error is Permission denied.
> All other reports running on this server (which don't take as long to run)
> are fine. I've checked IIS settings and blown the connection timeout to 9000
> seconds.
> It's as if the report is taking too long...
> I've set all the URL stuff in the config files, but like I say, its only one
> out of about a hundred reports that is failing.
> Any ideas?
> Steve

Long line of text error

Hey,
After working on a package for a while, I started to get the following error
when re-opening the package:
"Document contains one or more extremely long lines of text.
These lines will cause the editor to respond slowly when you open the file.
Do you still want to open the file?"
What is the problem and if there is fix or workaround?
Thanks.There is no fix or workaround however don't worry because there isn't a problem either. Its just a VS thing rather than a SSIS thing that's all.

I think (but may be wrong) it appears when you have a pre-compiled script task/component in your package. Perhaps you could confirm?

-Jamie|||Yes, I have precompiled script tasks in package. Otherwise they don't work :)|||Don't they?

This is a complete digression from the main point of this thread but...why not? What error do you get?

-Jamie

P.S. As I say, forget about the "long lines of text" thing!|||it's on this tread
http://forums.microsoft.com/msdn/showpost.aspx?postid=68546&siteid=1
actually I had the same problem. with precompilation I get no error.

ps. thanks for answering on "long line text..." stuff.

Logshipping ERROR(urgent)

Hi Guys,
I am facing following problem with MSSQL Server 2000.
I am using Microsoft sql server Log Shipping feature to have a standby
server for disaster recovery purposes.
in the logshipping Destination server while restoring the transaction log
the restore process is failling with following error.
"[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
PrevPageLSN: (8122:7374:3)."
Both servers, source and destination were running with SQL SERVER
ENTERPRISE EDITION SP3 .
after this failure i rebuilded the logshipping process but same error
happened again so after one week updated the destination server with sql sp4
and rebuilded the logshipping process . but the same error happened again.
During this error SQL Server is creating a dump file and text file
pls advice
Are you sure that your databases are consistent - run checkdb...
Bojidar Alexandrov
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
|||Hi Bojidar Alexandrov,
in source or destination?
source is consistent as i am doing dbcc every day and no errors found.
"Bojidar Alexandrov" wrote:

> Are you sure that your databases are consistent - run checkdb...
> Bojidar Alexandrov
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> SQL
> sp4
>
|||"bijupg@.hotmail.com" schrieb:

> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
Did you do transaction log backups in between? Don't forget that they empty
the TA-Log and produce a new sequence number - then the logshipping (being
fully incremental) are missing some data and cannot work any more ...
|||No i am not doing any transaction log backup in between
"Christian Donner" wrote:

> "bijupg@.hotmail.com" schrieb:
>
> Did you do transaction log backups in between? Don't forget that they empty
> the TA-Log and produce a new sequence number - then the logshipping (being
> fully incremental) are missing some data and cannot work any more ...
|||The type of error you are seeing is most likely being caused by corruption
in your transaction logs. Review system event logs on both servers for ANY
hardware-related warnings and errors. Update all your firmware and drivers.
Adrian
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
> sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
|||Biju.
You have been having trouble with this DB many times in the past. You had
corruption, it showed as fixed, and now it is back. You do not have torn
page detection on. Turn ton page detect ion on.
If your corruption continues, you will soon have a database that all you can
do it delete.
It may be worth your while to open a case with Microsoft PSS.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> The type of error you are seeing is most likely being caused by corruption
> in your transaction logs. Review system event logs on both servers for ANY
> hardware-related warnings and errors. Update all your firmware and
> drivers.
> Adrian
>
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
>
|||Hi Mike,
can you pls advice how to open case with Microsoft PSS.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>
|||Hi guys,
DBCC CHECKDB is not giving any errors or warnings and database is
functioning normally.
there are no hardware related errors in event viewer.
and we are using compaq cluster with compaq smart array controller so is
there any chance to have a torn page?this type of diska should have mechanism
to ensure that data is completely written and also there are no power failure
at all.
i am using transactional replication for reporting and it is working fine if
there was any problem with source database then it should also fail like
logshipping.
what should be the ideal temperature in datacentres/server romms currently
we are keeping 20-22 degree celcius is it ok?
Pls advice.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>

Logshipping ERROR(urgent)

Hi Guys,
I am facing following problem with MSSQL Server 2000.
I am using Microsoft sql server Log Shipping feature to have a standby
server for disaster recovery purposes.
in the logshipping Destination server while restoring the transaction log
the restore process is failling with following error.
"[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft]&
#91;ODBC SQL
Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
PrevPageLSN: (8122:7374:3)."
Both servers, source and destination were running with SQL SERVER
ENTERPRISE EDITION SP3 .
after this failure i rebuilded the logshipping process but same error
happened again so after one week updated the destination server with sql sp
4
and rebuilded the logshipping process . but the same error happened again.
During this error SQL Server is creating a dump file and text file
pls adviceAre you sure that your databases are consistent - run checkdb...
Bojidar Alexandrov
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][OD
BC
SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), fo
r
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Hi Bojidar Alexandrov,
in source or destination?
source is consistent as i am doing dbcc every day and no errors found.
"Bojidar Alexandrov" wrote:

> Are you sure that your databases are consistent - run checkdb...
> Bojidar Alexandrov
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> SQL
> sp4
>|||"bijupg@.hotmail.com" schrieb:

> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft
][ODBC SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), fo
r
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
Did you do transaction log backups in between? Don't forget that they empty
the TA-Log and produce a new sequence number - then the logshipping (being
fully incremental) are missing some data and cannot work any more ...|||No i am not doing any transaction log backup in between
"Christian Donner" wrote:

> "bijupg@.hotmail.com" schrieb:
>
> Did you do transaction log backups in between? Don't forget that they empt
y
> the TA-Log and produce a new sequence number - then the logshipping (being
> fully incremental) are missing some data and cannot work any more ...|||The type of error you are seeing is most likely being caused by corruption
in your transaction logs. Review system event logs on both servers for ANY
hardware-related warnings and errors. Update all your firmware and drivers.
Adrian
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft
][ODBC
> SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), fo
r
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
> sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Biju.
You have been having trouble with this DB many times in the past. You had
corruption, it showed as fixed, and now it is back. You do not have torn
page detection on. Turn ton page detect ion on.
If your corruption continues, you will soon have a database that all you can
do it delete.
It may be worth your while to open a case with Microsoft PSS.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> The type of error you are seeing is most likely being caused by corruption
> in your transaction logs. Review system event logs on both servers for ANY
> hardware-related warnings and errors. Update all your firmware and
> drivers.
> Adrian
>
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
>|||Hi Mike,
can you pls advice how to open case with Microsoft PSS.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you c
an
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>|||Hi guys,
DBCC CHECKDB is not giving any errors or warnings and database is
functioning normally.
there are no hardware related errors in event viewer.
and we are using compaq cluster with compaq smart array controller so is
there any chance to have a torn page?this type of diska should have mechanis
m
to ensure that data is completely written and also there are no power failur
e
at all.
i am using transactional replication for reporting and it is working fine if
there was any problem with source database then it should also fail like
logshipping.
what should be the ideal temperature in datacentres/server romms currently
we are keeping 20-22 degree celcius is it ok?
Pls advice.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you c
an
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>

Logshipping ERROR(urgent)

Hi Guys,
I am facing following problem with MSSQL Server 2000.
I am using Microsoft sql server Log Shipping feature to have a standby
server for disaster recovery purposes.
in the logshipping Destination server while restoring the transaction log
the restore process is failling with following error.
"[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
PrevPageLSN: (8122:7374:3)."
Both servers, source and destination were running with SQL SERVER
ENTERPRISE EDITION SP3 .
after this failure i rebuilded the logshipping process but same error
happened again so after one week updated the destination server with sql sp4
and rebuilded the logshipping process . but the same error happened again.
During this error SQL Server is creating a dump file and text file
pls adviceAre you sure that your databases are consistent - run checkdb...
Bojidar Alexandrov
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Hi Bojidar Alexandrov,
in source or destination?
source is consistent as i am doing dbcc every day and no errors found.
"Bojidar Alexandrov" wrote:
> Are you sure that your databases are consistent - run checkdb...
> Bojidar Alexandrov
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> > Hi Guys,
> > I am facing following problem with MSSQL Server 2000.
> > I am using Microsoft sql server Log Shipping feature to have a standby
> > server for disaster recovery purposes.
> > in the logshipping Destination server while restoring the transaction log
> > the restore process is failling with following error.
> >
> > "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> SQL
> > Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> > transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> > Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> > PrevPageLSN: (8122:7374:3)."
> >
> > Both servers, source and destination were running with SQL SERVER
> > ENTERPRISE EDITION SP3 .
> > after this failure i rebuilded the logshipping process but same error
> > happened again so after one week updated the destination server with sql
> sp4
> > and rebuilded the logshipping process . but the same error happened again.
> > During this error SQL Server is creating a dump file and text file
> >
> > pls advice
>|||"bijupg@.hotmail.com" schrieb:
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
Did you do transaction log backups in between? Don't forget that they empty
the TA-Log and produce a new sequence number - then the logshipping (being
fully incremental) are missing some data and cannot work any more ...|||No i am not doing any transaction log backup in between
"Christian Donner" wrote:
> "bijupg@.hotmail.com" schrieb:
> > Hi Guys,
> > I am facing following problem with MSSQL Server 2000.
> > I am using Microsoft sql server Log Shipping feature to have a standby
> > server for disaster recovery purposes.
> > in the logshipping Destination server while restoring the transaction log
> > the restore process is failling with following error.
> >
> > "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
> > Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> > transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> > Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> > PrevPageLSN: (8122:7374:3)."
> >
> > Both servers, source and destination were running with SQL SERVER
> > ENTERPRISE EDITION SP3 .
> > after this failure i rebuilded the logshipping process but same error
> > happened again so after one week updated the destination server with sql sp4
> > and rebuilded the logshipping process . but the same error happened again.
> > During this error SQL Server is creating a dump file and text file
> >
> > pls advice
> Did you do transaction log backups in between? Don't forget that they empty
> the TA-Log and produce a new sequence number - then the logshipping (being
> fully incremental) are missing some data and cannot work any more ...|||The type of error you are seeing is most likely being caused by corruption
in your transaction logs. Review system event logs on both servers for ANY
hardware-related warnings and errors. Update all your firmware and drivers.
Adrian
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
> sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Biju.
You have been having trouble with this DB many times in the past. You had
corruption, it showed as fixed, and now it is back. You do not have torn
page detection on. Turn ton page detect ion on.
If your corruption continues, you will soon have a database that all you can
do it delete.
It may be worth your while to open a case with Microsoft PSS.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> The type of error you are seeing is most likely being caused by corruption
> in your transaction logs. Review system event logs on both servers for ANY
> hardware-related warnings and errors. Update all your firmware and
> drivers.
> Adrian
>
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
>> Hi Guys,
>> I am facing following problem with MSSQL Server 2000.
>> I am using Microsoft sql server Log Shipping feature to have a standby
>> server for disaster recovery purposes.
>> in the logshipping Destination server while restoring the transaction log
>> the restore process is failling with following error.
>> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
>> SQL
>> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
>> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
>> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
>> PrevPageLSN: (8122:7374:3)."
>> Both servers, source and destination were running with SQL SERVER
>> ENTERPRISE EDITION SP3 .
>> after this failure i rebuilded the logshipping process but same error
>> happened again so after one week updated the destination server with sql
>> sp4
>> and rebuilded the logshipping process . but the same error happened
>> again.
>> During this error SQL Server is creating a dump file and text file
>> pls advice
>|||Hi Mike,
can you pls advice how to open case with Microsoft PSS.
"Mike Epprecht (SQL MVP)" wrote:
> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> > The type of error you are seeing is most likely being caused by corruption
> > in your transaction logs. Review system event logs on both servers for ANY
> > hardware-related warnings and errors. Update all your firmware and
> > drivers.
> >
> > Adrian
> >
> >
> > "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> > message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> >> Hi Guys,
> >> I am facing following problem with MSSQL Server 2000.
> >> I am using Microsoft sql server Log Shipping feature to have a standby
> >> server for disaster recovery purposes.
> >> in the logshipping Destination server while restoring the transaction log
> >> the restore process is failling with following error.
> >>
> >> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> >> SQL
> >> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> >> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> >> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> >> PrevPageLSN: (8122:7374:3)."
> >>
> >> Both servers, source and destination were running with SQL SERVER
> >> ENTERPRISE EDITION SP3 .
> >> after this failure i rebuilded the logshipping process but same error
> >> happened again so after one week updated the destination server with sql
> >> sp4
> >> and rebuilded the logshipping process . but the same error happened
> >> again.
> >> During this error SQL Server is creating a dump file and text file
> >>
> >> pls advice
> >
> >
>
>|||Hi guys,
DBCC CHECKDB is not giving any errors or warnings and database is
functioning normally.
there are no hardware related errors in event viewer.
and we are using compaq cluster with compaq smart array controller so is
there any chance to have a torn page?this type of diska should have mechanism
to ensure that data is completely written and also there are no power failure
at all.
i am using transactional replication for reporting and it is working fine if
there was any problem with source database then it should also fail like
logshipping.
what should be the ideal temperature in datacentres/server romms currently
we are keeping 20-22 degree celcius is it ok?
Pls advice.
"Mike Epprecht (SQL MVP)" wrote:
> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> > The type of error you are seeing is most likely being caused by corruption
> > in your transaction logs. Review system event logs on both servers for ANY
> > hardware-related warnings and errors. Update all your firmware and
> > drivers.
> >
> > Adrian
> >
> >
> > "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> > message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> >> Hi Guys,
> >> I am facing following problem with MSSQL Server 2000.
> >> I am using Microsoft sql server Log Shipping feature to have a standby
> >> server for disaster recovery purposes.
> >> in the logshipping Destination server while restoring the transaction log
> >> the restore process is failling with following error.
> >>
> >> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> >> SQL
> >> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> >> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> >> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> >> PrevPageLSN: (8122:7374:3)."
> >>
> >> Both servers, source and destination were running with SQL SERVER
> >> ENTERPRISE EDITION SP3 .
> >> after this failure i rebuilded the logshipping process but same error
> >> happened again so after one week updated the destination server with sql
> >> sp4
> >> and rebuilded the logshipping process . but the same error happened
> >> again.
> >> During this error SQL Server is creating a dump file and text file
> >>
> >> pls advice
> >
> >
>
>sql

logshipping error

Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS AdviceThis is a multi-part message in MIME format.
--040104080107040407070908
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:
>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>
--040104080107040407070908
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Sounds like the corruption on the primary DB has put the tlog syncs
out of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the
log shipping pair for you using the DB maint wizard.)</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:bijupg@.hotmail.com">bijupg@.hotmail.com</a> wrote:
<blockquote cite="midD73EA24F-DBEA-4E4F-9F4F-797DC31E31FF@.microsoft.com"
type="cite">
<pre wrap="">Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS Advice
</pre>
</blockquote>
</body>
</html>
--040104080107040407070908--|||This is a multi-part message in MIME format.
--=_NextPart_000_000D_01C56A79.C4EDC0F0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon
--=_NextPart_000_000D_01C56A79.C4EDC0F0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon

---

--=_NextPart_000_000D_01C56A79.C4EDC0F0--

Logshipping error

Hi,
I get the following error after I setup logshipping and
try to restore the copied trn file.
Any ideas'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4326:
[Microsoft][ODBC SQL Server Driver][SQL Server]The log in
this backup set terminates at LSN 37123000007023700001,
which is too early to apply to the database. A more
recent log backup that includes LS
N 37731000001578500001 can be
restored.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE
LOG is terminating
abnormally.| I get the following error after I setup logshipping and
| try to restore the copied trn file.
| Any ideas'
|
| [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4326:
| [Microsoft][ODBC SQL Server Driver][SQL Server]The log in
| this backup set terminates at LSN 37123000007023700001,
| which is too early to apply to the database. A more
| recent log backup that includes LS
| N 37731000001578500001 can be
| restored.
|
| [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE
| LOG is terminating
| abnormally.
--
It looks like your transaction log backups are out-of-synch. Can you review
your scheduled jobs and make sure that only the log shipping process and no
other independent jobs are creating transaction log backups.
Hope this helps,
--
Eric Cárdenas
SQL Server support

logshipping error

Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][OD
BC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS AdviceSounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:

>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][O
DBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>|||yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon

logshipping error

Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS Advice
Sounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:

>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>
|||yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon

logs - configuration option changed

Using SS2000. I often see a line in the logs that says "configuration opton 'allow updates' changed from 0 to 1. Run the RECONFIGURE s Error 15457, serverity 0, State 1"
Another entry will change the option from 1 to 0. What's going on? Is a dts package doing this as part of a normal run?
Thanks,
Dan D.
That is usually associated with someone using EM to view certain options.
It is nothing to be concerned with.
Andrew J. Kelly SQL MVP
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:FAD761D0-4D1B-4EB4-BF9E-18155CC0ED9C@.microsoft.com...
> Using SS2000. I often see a line in the logs that says "configuration
opton 'allow updates' changed from 0 to 1. Run the RECONFIGURE s Error
15457, serverity 0, State 1"
> Another entry will change the option from 1 to 0. What's going on? Is a
dts package doing this as part of a normal run?
> Thanks,
> --
> Dan D.
|||No one claims to have been on the system at that time (1 AM local time). Could some system process make the changes?
Thanks,
Dan D.
"Andrew J. Kelly" wrote:

> That is usually associated with someone using EM to view certain options.
> It is nothing to be concerned with.
> --
> Andrew J. Kelly SQL MVP
>
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:FAD761D0-4D1B-4EB4-BF9E-18155CC0ED9C@.microsoft.com...
> opton 'allow updates' changed from 0 to 1. Run the RECONFIGURE s Error
> 15457, serverity 0, State 1"
> dts package doing this as part of a normal run?
>
>
|||Do you have a maintenance plan set up and if so does it have the option to
fix minor errors? This may cause an entry like this but I am not 100 %
sure. Are there any scheduled jobs that collect information from the server
with say sp_dboption?
Andrew J. Kelly SQL MVP
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:95E34CD1-BDFA-423B-B05B-C319F7E8E3E3@.microsoft.com...
> No one claims to have been on the system at that time (1 AM local time).
Could some system process make the changes?[vbcol=seagreen]
> Thanks,
> --
> Dan D.
>
> "Andrew J. Kelly" wrote:
options.[vbcol=seagreen]
a[vbcol=seagreen]
|||There are no maintenance plans. There was one dts package that was running at the time of the message. I'll look through it and see what I can find.
Thanks,
Dan D.
"Andrew J. Kelly" wrote:

> Do you have a maintenance plan set up and if so does it have the option to
> fix minor errors? This may cause an entry like this but I am not 100 %
> sure. Are there any scheduled jobs that collect information from the server
> with say sp_dboption?
> --
> Andrew J. Kelly SQL MVP
>
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:95E34CD1-BDFA-423B-B05B-C319F7E8E3E3@.microsoft.com...
> Could some system process make the changes?
> options.
> a
>
>

LOGS

hello, i get this error
Microsoft OLE DB Provider for SQL Server error '80040e14'
The log file for database 'autosmotos' is full. Back up the transaction log
for the database to free up some log space.
So i try to delete the LOF file with this command:
ALTER DATABASE [autosmotos]
REMOVE FILE [autosmotos_Log]
GO
But i get
The primary data or log file cannot be removed from a database
Q: how i can i set off this option or how can i empty the log file ?
Gerard.hi Gérard,
I'll do a shrink over that .LDF file or in the case that you would have
enough free space, you could make another LOG file in the same volume.
A question, what recovery model own your database? If your database contains
only 'development data' or 'test data' a good idea is have as simple model.
Current location: Alicante (ES)
"Gérard Leclercq" wrote:

> hello, i get this error
> Microsoft OLE DB Provider for SQL Server error '80040e14'
> The log file for database 'autosmotos' is full. Back up the transaction lo
g
> for the database to free up some log space.
>
> So i try to delete the LOF file with this command:
> ALTER DATABASE [autosmotos]
> REMOVE FILE [autosmotos_Log]
> GO
>
> But i get
> The primary data or log file cannot be removed from a database
>
> Q: how i can i set off this option or how can i empty the log file ?
>
> Gerard.
>
>
>|||underprocessable|||BACKUP LOG autosmotos WITH TRUNCATE_ONLY
GO
DBCC SHRINKFILE(autosmotos_LOG,1)
GO
You may then want to issue the following command :-
ALTER DATABASE autosmotos SET RECOVERY SIMPLE
But i would suggest reading up on this 1st
HTH. Ryan
"Grard Leclercq" <gl@.pasdemail.fr> wrote in message
news:MQ8Uf.330505$cT4.10333346@.phobos.telenet-ops.be...
>I work in hard conditions. The db is on a internetserver. I don't have
>access to the Enterprise so i have to ask, and ask, and ask my provider but
>i get no help. I found a trial version of a on-line manager. In attach some
>settings. Maybe this help.
> Is there an instruction to delete or schrink the log file or to turn it
> off ?
> "Enric" <vtam13@.terra.es.(donotspam)> schreef in bericht
> news:9033071E-3A41-42C8-85B2-A35FE6919F70@.microsoft.com...
>
>|||Thank you, the log is empty now(i suppose because the error is not longer
there)
gerard
"Ryan" <Ryan_Waight@.nospam.hotmail.com> schreef in bericht
news:uLJ7qSZTGHA.6084@.TK2MSFTNGP14.phx.gbl...
> BACKUP LOG autosmotos WITH TRUNCATE_ONLY
> GO
> DBCC SHRINKFILE(autosmotos_LOG,1)
> GO
> You may then want to issue the following command :-
> ALTER DATABASE autosmotos SET RECOVERY SIMPLE
> But i would suggest reading up on this 1st
> --
> HTH. Ryan
>
> "Grard Leclercq" <gl@.pasdemail.fr> wrote in message
> news:MQ8Uf.330505$cT4.10333346@.phobos.telenet-ops.be...
>

LogReader SubSystem

I'm trying to setup a publisher on an msde database and am getting an error
when running my script. The error in the event viewer (and job history)
is -
Step 2 of job 'machine\instance-database-1' cannot be run because the
LogReader subsystem failed to load. The job has been suspended.
The job category is REPL -LogReader. Any ideas what I can do or what I
missed?
TIA,
Dave
on your msde server open a command prompt and go to c:\program
files\Microsoft sql server\80\com and type logread
do you get an error message?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Dave" <dave.golightly@.stgutah.com> wrote in message
news:uZYCJIYpEHA.2304@.TK2MSFTNGP14.phx.gbl...
> I'm trying to setup a publisher on an msde database and am getting an
error
> when running my script. The error in the event viewer (and job history)
> is -
> Step 2 of job 'machine\instance-database-1' cannot be run because the
> LogReader subsystem failed to load. The job has been suspended.
> The job category is REPL -LogReader. Any ideas what I can do or what I
> missed?
> TIA,
> Dave
>
|||I got -
"'logread' is not recognized as an internal or external command, operable
program or batch file"
So the installshield object I'm using to install the msde isn't installing
the logread file. Is there any other files I should be checking for?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uhmT8OZpEHA.744@.TK2MSFTNGP10.phx.gbl...
> on your msde server open a command prompt and go to c:\program
> files\Microsoft sql server\80\com and type logread
> do you get an error message?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Dave" <dave.golightly@.stgutah.com> wrote in message
> news:uZYCJIYpEHA.2304@.TK2MSFTNGP14.phx.gbl...
> error
>
|||Oops, I'm making a huge mistake here. MSDE servers are not enable to be
transactional publishers. You will have to make it a merge publisher.
Sorry about that.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Dave" <dave.golightly@.stgutah.com> wrote in message
news:Os127ZZpEHA.3688@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> I got -
> "'logread' is not recognized as an internal or external command, operable
> program or batch file"
> So the installshield object I'm using to install the msde isn't installing
> the logread file. Is there any other files I should be checking for?
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uhmT8OZpEHA.744@.TK2MSFTNGP10.phx.gbl...
history)
>
|||I'm trying to create a snapshot publisher. Is there a setting I've got
wrong?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eG0FwfZpEHA.592@.TK2MSFTNGP11.phx.gbl...
> Oops, I'm making a huge mistake here. MSDE servers are not enable to be
> transactional publishers. You will have to make it a merge publisher.
> Sorry about that.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Dave" <dave.golightly@.stgutah.com> wrote in message
> news:Os127ZZpEHA.3688@.TK2MSFTNGP09.phx.gbl...
> history)
>
|||Here's the script -
-- Adding the snapshot publication
exec sp_addpublication @.publication = N'inspPro Snapshot Publication',
@.restricted = N'false', @.sync_method = N'native', @.repl_freq = N'snapshot',
@.description = N'Snapshot publication of inspPro database from Publisher
[workstation]\INSPPRO.', @.status = N'active', @.allow_push = N'true',
@.allow_pull = N'true', @.allow_anonymous = N'true', @.enabled_for_internet =
N'false', @.independent_agent = N'true', @.immediate_sync = N'true',
@.allow_sync_tran = N'false', @.autogen_sync_procs = N'true', @.retention = 0,
@.allow_queued_tran = N'true', @.snapshot_in_defaultfolder = N'true',
@.compress_snapshot = N'false', @.ftp_port = 21, @.ftp_login = N'anonymous',
@.allow_dts = N'false', @.allow_subscription_copy = N'false', @.conflict_policy
= N'sub reinit', @.centralized_conflicts = N'true', @.conflict_retention = 14,
@.queue_type = N'sql', @.add_to_active_directory = N'false',
@.logreader_job_name = N'[workstation]\INSPPRO-inspPro-1'
GO
exec sp_addpublication_snapshot @.publication = N'inspPro Snapshot
Publication',@.frequency_type = 4, @.frequency_interval = 1,
@.frequency_relative_interval = 1, @.frequency_recurrence_factor = 0,
@.frequency_subday = 8, @.frequency_subday_interval = 1, @.active_start_date =
0, @.active_end_date = 0, @.active_start_time_of_day = 0,
@.active_end_time_of_day = 235959, @.snapshot_job_name = N'inspPro Snapshot
Snapshot Agent'
GO
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eG0FwfZpEHA.592@.TK2MSFTNGP11.phx.gbl...
> Oops, I'm making a huge mistake here. MSDE servers are not enable to be
> transactional publishers. You will have to make it a merge publisher.
> Sorry about that.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Dave" <dave.golightly@.stgutah.com> wrote in message
> news:Os127ZZpEHA.3688@.TK2MSFTNGP09.phx.gbl...
> history)
>
|||This looks like a updateable subscription using the queue reader. I don't
believe this is supported on MSDE where MSDE is the publisher.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Dave" <dave.golightly@.stgutah.com> wrote in message
news:e0W6CpZpEHA.3868@.TK2MSFTNGP15.phx.gbl...
> Here's the script -
> -- Adding the snapshot publication
> exec sp_addpublication @.publication = N'inspPro Snapshot Publication',
> @.restricted = N'false', @.sync_method = N'native', @.repl_freq =
N'snapshot',
> @.description = N'Snapshot publication of inspPro database from Publisher
> [workstation]\INSPPRO.', @.status = N'active', @.allow_push = N'true',
> @.allow_pull = N'true', @.allow_anonymous = N'true', @.enabled_for_internet =
> N'false', @.independent_agent = N'true', @.immediate_sync = N'true',
> @.allow_sync_tran = N'false', @.autogen_sync_procs = N'true', @.retention =
0,
> @.allow_queued_tran = N'true', @.snapshot_in_defaultfolder = N'true',
> @.compress_snapshot = N'false', @.ftp_port = 21, @.ftp_login = N'anonymous',
> @.allow_dts = N'false', @.allow_subscription_copy = N'false',
@.conflict_policy
> = N'sub reinit', @.centralized_conflicts = N'true', @.conflict_retention =
14,
> @.queue_type = N'sql', @.add_to_active_directory = N'false',
> @.logreader_job_name = N'[workstation]\INSPPRO-inspPro-1'
> GO
> exec sp_addpublication_snapshot @.publication = N'inspPro Snapshot
> Publication',@.frequency_type = 4, @.frequency_interval = 1,
> @.frequency_relative_interval = 1, @.frequency_recurrence_factor = 0,
> @.frequency_subday = 8, @.frequency_subday_interval = 1, @.active_start_date
=[vbcol=seagreen]
> 0, @.active_end_date = 0, @.active_start_time_of_day = 0,
> @.active_end_time_of_day = 235959, @.snapshot_job_name = N'inspPro Snapshot
> Snapshot Agent'
> GO
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eG0FwfZpEHA.592@.TK2MSFTNGP11.phx.gbl...
operable[vbcol=seagreen]
an[vbcol=seagreen]
the[vbcol=seagreen]
what
>

LOGREADER NOT START - No body can help?

When I try to start the agent (replication monitor->Agents -> log reader
Agent - with red cross). show me this error :
22022 sqlserveragent error: request to run job svr-personal-origen-1 (from
user personal\alioscha) refused because the job has been suspended.
SO windows 2000. server 2000 sp1
ANY HELP WILL BE APPRECIATED.
right click on this job and start it under sa.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Alioscha Debali" <adebali@.copetel.com.ar> wrote in message
news:%23RpNHcHNFHA.568@.TK2MSFTNGP09.phx.gbl...
> When I try to start the agent (replication monitor->Agents -> log reader
> Agent - with red cross). show me this error :
> 22022 sqlserveragent error: request to run job svr-personal-origen-1 (from
> user personal\alioscha) refused because the job has been suspended.
> SO windows 2000. server 2000 sp1
>
> ANY HELP WILL BE APPRECIATED.
>
>
>
|||Hilary thank you for your answer, But I have tried and it did not work.
"Hilary Cotter" wrote:

> right click on this job and start it under sa.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Alioscha Debali" <adebali@.copetel.com.ar> wrote in message
> news:%23RpNHcHNFHA.568@.TK2MSFTNGP09.phx.gbl...
>
>
|||Hilary. Into folder Admin->Jobs , There is a Job "SVR-PERSONAL-ORIGEN-1"
with red cross ( category REPL-LogReader) YES/ NO (job susp)/YES/SUSP
Right click.->General Label. Owner: sa.
Do I doing something wrong?
Thank again for your help.
"Alioscha Debali" <Alioscha Debali@.discussions.microsoft.com> escribi en el
mensaje news:84FDD7B9-91A9-4635-9174-BA75C3C4AE1A@.microsoft.com...[vbcol=seagreen]
> Hilary thank you for your answer, But I have tried and it did not work.
>
>
> "Hilary Cotter" wrote:
reader[vbcol=seagreen]
(from[vbcol=seagreen]

Logreader failed to construct replicated command from LSN

I have this error coming up 'The process could not execute 'sp_replcmds' on
'VDB1' which always seems to accompany 'Logreader failed to construct
replicated command from LSN {0008e253:00009ddb:0003}.'
I turned on verbose logging and it gave this:
2007-05-04 01:31:16.018 Publisher: {call sp_replcmds (500, 0, 0, , 15,
500000)}
2007-05-04 01:31:16.065 I~0x0008e25300009ddb0005~1:
Looking up that sequence number with:
exec sp_browsereplcmds @.xact_seqno_start = '0x0008e25300009ddb0005'
, @.xact_seqno_end = '0x0008e25300009ddb0005'
Returned nothing.
I also tried:
select * from MSrepl_transactions
where xact_seqno = '0x0008e25300009ddb0005'
It returned nothing also.
This same error is preventing 2 publications, but other 8 are working fine.
I have stopped and started log reader job a couple of times.
Any ideas?
Thanks,
Chuck Lathrope
www.sqlwebpedia.com
I've bumped into this from time to time. What you need to do is to run
profiler with the xactSequence number column.
Next time you get this error, look up the offending statement, for example
it could be a proc which is writing something unexpected to the database.
Last time I got this, it was an update to a text column with a ''.
"Chuck Lathrope" <computerguy_chuck@.fixmehotmail.com> wrote in message
news:5likshd2rlr9.1cei74wrqkxlw$.dlg@.40tude.net...
>I have this error coming up 'The process could not execute 'sp_replcmds' on
> 'VDB1' which always seems to accompany 'Logreader failed to construct
> replicated command from LSN {0008e253:00009ddb:0003}.'
> I turned on verbose logging and it gave this:
> 2007-05-04 01:31:16.018 Publisher: {call sp_replcmds (500, 0, 0, , 15,
> 500000)}
> 2007-05-04 01:31:16.065 I~0x0008e25300009ddb0005~1:
> Looking up that sequence number with:
> exec sp_browsereplcmds @.xact_seqno_start = '0x0008e25300009ddb0005'
> , @.xact_seqno_end = '0x0008e25300009ddb0005'
> Returned nothing.
> I also tried:
> select * from MSrepl_transactions
> where xact_seqno = '0x0008e25300009ddb0005'
> It returned nothing also.
> This same error is preventing 2 publications, but other 8 are working
> fine.
> I have stopped and started log reader job a couple of times.
> Any ideas?
> Thanks,
> Chuck Lathrope
> www.sqlwebpedia.com
|||On Fri, 4 May 2007 08:29:28 -0400, Hilary Cotter wrote:
Thanks, it only seems to be getting worse for me. The replication monitor
can't expand the server nodes now. I restarted sql service on the
distributor and that didn't help. Has anyone seen that?
I am setting the -ReadBatchsize to 1 as Jonathan suggested, hopefully it
can find to correct issue as this command in error reports looks to be
pointed to something already completed.
-Chuck
[vbcol=seagreen]
> I've bumped into this from time to time. What you need to do is to run
> profiler with the xactSequence number column.
> Next time you get this error, look up the offending statement, for example
> it could be a proc which is writing something unexpected to the database.
> Last time I got this, it was an update to a text column with a ''.
>
> "Chuck Lathrope" <computerguy_chuck@.fixmehotmail.com> wrote in message
> news:5likshd2rlr9.1cei74wrqkxlw$.dlg@.40tude.net...
|||Update:
One of the two publications started to work, not sure why or when.
The batchsize to 1 still brought back the same LSN error - which is still
returning nothing when I query it with:
select * from MSrepl_transactions
where xact_seqno = '0x0008e25300009ddb0005'
We are going to kill the publications and recreate them - luckily they are
not super critical like the others.
Still having Replication Monitor issues (Still running SP1 on server; SP2
on my local box).
-Chuck
On Fri, 4 May 2007 08:29:28 -0400, Hilary Cotter wrote:
Thanks, it only seems to be getting worse for me. The replication monitor
can't expand the server nodes now. I restarted sql service on the
distributor and that didn't help. Has anyone seen that?
I am setting the -ReadBatchsize to 1 as Jonathan suggested, hopefully it
can find to correct issue as this command in error reports looks to be
pointed to something already completed.
-Chuck
[vbcol=seagreen]
> I've bumped into this from time to time. What you need to do is to run
> profiler with the xactSequence number column.
> Next time you get this error, look up the offending statement, for example
> it could be a proc which is writing something unexpected to the database.
> Last time I got this, it was an update to a text column with a ''.
>
> "Chuck Lathrope" <computerguy_chuck@.fixmehotmail.com> wrote in message
> news:5likshd2rlr9.1cei74wrqkxlw$.dlg@.40tude.net...
|||While recreating the publications, the snapshot errored because of an
obsolete XSD for an XML table. We have the option set to false to publish
the XSD's, so not sure how this came about.
Now that these are working, the Replication Monitor server nodes can be
expanded now.
-Chuck
On Fri, 4 May 2007 10:15:26 -0700, Chuck Lathrope wrote:
[vbcol=seagreen]
> Update:
> One of the two publications started to work, not sure why or when.
> The batchsize to 1 still brought back the same LSN error - which is still
> returning nothing when I query it with:
> select * from MSrepl_transactions
> where xact_seqno = '0x0008e25300009ddb0005'
> We are going to kill the publications and recreate them - luckily they are
> not super critical like the others.
> Still having Replication Monitor issues (Still running SP1 on server; SP2
> on my local box).
> -Chuck
>
> On Fri, 4 May 2007 08:29:28 -0400, Hilary Cotter wrote:
> Thanks, it only seems to be getting worse for me. The replication monitor
> can't expand the server nodes now. I restarted sql service on the
> distributor and that didn't help. Has anyone seen that?
> I am setting the -ReadBatchsize to 1 as Jonathan suggested, hopefully it
> can find to correct issue as this command in error reports looks to be
> pointed to something already completed.
> -Chuck

LogOnInfo is not a member of Schools.Table.

Hello,

I am gettign an error while I am using Crystal Report 9 with asp.net 1. Actually, till yesterday I it was working fine and today, I have changed the position of my computer. I don't know what happened. Please help.

Error is

1) C:\Schooloutlook\FormFile\Report\MForm7.aspx.vb(77): 'LogOnInfo' is not a member of 'Schools.Table'.

2) C:\Schooloutlook\FormFile\Report\MLocalDensity.aspx.vb(118): 'Location' is not a member of 'Schools.Table'.

Thanks
CeemaOpen the report and Do verify database

Logon from remote system error

Hi all,
When I am installing Commerce Server on my SQL Server 2005 machine I get
an error reported in the logs that that says "Login failed for user 'CSNET\t
aziegma'.
[CLIENT: 192.168.25.12] Error: 18456, Severity: 14, State: 16. I have lo
oked
on google for information. I have also posted in the Commerce Server groups.
I can run queries against the databases the remote system is trying to acces
s
no problem. But when Commerce Server tries to access it it errors out. Also,
when I view the Activity Monitor next to the processes kicked off by the
remote machine it says .net sqlserver client provider. Is there something
I need to set up for .net? I am stumped.
thanks,
tziegmannDoes Commerce Server never work or is it just an issue for this user?
depending on the configuration, this might be a "double hop" issue. If you
are not logged in directly to the to the commerce server machine but logged
in to another machine accessing Commerce Server, the Commerce Server would
require delegation permission to log into SQL Server with the client's
credentials. This only works if your networks supports Kerberos
authentication and delegation is allowed. Many networks don't allow this.
Note that this answer is based on a lot of assumptions about your
configuration and is basically a guess based on your mention of Commerce
Server.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"tziegmann" <tziegmann@.msn.com> wrote in message
news:428ac052327f8c80d356188011c@.news.microsoft.com...
> Hi all,
> When I am installing Commerce Server on my SQL Server 2005 machine I get
> an error reported in the logs that that says "Login failed for user
> 'CSNET\taziegma'. [CLIENT: 192.168.25.12] Error: 18456, Severity: 14,
> State: 16. I have looked on google for information. I have also posted in
> the Commerce Server groups. I can run queries against the databases the
> remote system is trying to access no problem. But when Commerce Server
> tries to access it it errors out. Also, when I view the Activity Monitor
> next to the processes kicked off by the remote machine it says .net
> sqlserver client provider. Is there something I need to set up for .net? I
> am stumped.
> thanks,
> tziegmann
>

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 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 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

Logon failed for user '(null)'..... error

We are receiving the error "Logon failed for
user '(null)'. Reason: Not associated with a trusted SQL
Server Connection".
We have a WinForms application written in VB.NET 2003 and
connect to a SQL Server 2000 (SP3) DB with the following
connection string:
gstrConn = _
"Server=SQL2000;" & _
"DataBase=dbname;" & _
"Integrated Security=SSPI;"
The application works perfectly for the users on one
network domain, but the error listed above appears when
trying to access the DB application from a user's
workstation on another domain. The user has a SQL Server
account. We have even tried to have the user run the DB
application in a smart client "trusted assembly"
environment but also get the error. What must be
configured differently and how?
A poor state employee-
Jeromeprevious message: "The application works perfectly for the users on one
network domain, but the error listed above appears when
trying to access the DB application from a user's
workstation on another domain. The user has a SQL Server
account. "
To make a Trusted connection the domains need to have a Trust between them.
The users need to be defined as either a domain user or from a domain
group.
If the user has a SQL Server account, then you are not using Integrated
Security. This is SQL Security. If you want to use SQL Security then you
need to change your connection string. If you want to keep the connection
string as is, then make sure the clients in the other domain can make a
Trusted Connection to SQL. Add the users from the other domain in SQL
Enterprise Manager.
Then, either load the SQL client tools on one of the workstations & test
connections from Query Analyser or try creating a sample ODBC DSN and
request Windows Authentication.
Read this information and it will make more sense.
http://www.microsoft.com/technet/tr...chnet/prodtechn
ol/sql/maintain/security/sp3sec/default.asp
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Cheif!
Unfortunately, I am not the network or SQL Server
Administrator but I am passing the information on to the
LAN/SQL Administrator. Hopefully, they will know how to
set up the trust between the domains since they are all
within our same division.
My connection string is fine for using Windows
Authentication right?
Also- All users no matter what domain they are on should
be able to access the DB if the domains are trusted, right?
(and the users have SQL Server IDs)
Sorry- I am LAN ignorant and overwhelmed at present trying
to get a grip on VB.NET. (Some finger pointing going own
here but we are civil and friendly).
Ailing in Alabama
Jrome
Merry Christmas from Dixie!

quote:

---

>--Original Message--
>previous message: "The application works perfectly for

---

the users on one

quote:

---

>network domain, but the error listed above appears when
>trying to access the DB application from a user's
>workstation on another domain. The user has a SQL Server
>account. "
>To make a Trusted connection the domains need to have a

---

Trust between them.

quote:

---

> The users need to be defined as either a domain user or

---

from a domain

quote:

---

>group.
>If the user has a SQL Server account, then you are not

---

using Integrated

quote:

---

>Security. This is SQL Security. If you want to use SQL

---

Security then you

quote:

---

>need to change your connection string. If you want to

---

keep the connection

quote:

---

>string as is, then make sure the clients in the other

---

domain can make a

quote:

---

>Trusted Connection to SQL. Add the users from the other

---

domain in SQL

quote:

---

>Enterprise Manager.
>Then, either load the SQL client tools on one of the

---

workstations & test

quote:

---

>connections from Query Analyser or try creating a sample

---

ODBC DSN and

quote:

---

>request Windows Authentication.
>
>Read this information and it will make more sense.
>http://www.microsoft.com/technet/treeview/default.asp?

---

url=/technet/prodtechn

quote:

---

>ol/sql/maintain/security/sp3sec/default.asp
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and

---

confers no rights.

quote:

---

>
>.
>

---

|||Previous post questions:
My connection string is fine for using Windows
Authentication right?
-- Yes.
Also- All users no matter what domain they are on should
be able to access the DB if the domains are trusted, right?
-- Yes. They should have SQL logins defined by NT users or groups.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.