Error 823 that I cant fix

Hi,

I am running SQL 2000 server for datawarehousing and I am getting the following error in the application log when I build large tables:

Error: 823, Severity: 24, State: 3
I/O error 33(The process cannot access the file because another process has locked a portion of the file.) detected during write at offset 0x00000829618000 in file '<file name.mdf>'

I have run through MS Support and really haven't found helpful info on this. I don't know what process is locking the mdf file, but I don't beleive there are any server or even client side programs running against this datafile.

Any thoughts?

joeNot come across that error before, but I would try looking under the Managment section of your server in Enterprise Manager then Locks/Objects and see if you can spot an offending process. If there is one it may be worth trying to kill it.

Error 400 Bad Request in Reporting Services

Hi,
I get this strange error when I try to acess my SQL Reporting Services application.
I'm using SQL 2005 Beta 2. The installation was OK and the server is working fine. That is the only problem.
I checked the logs and a traced the database, but couldn't find someful usefull (at leat for me).
Here's the SQL2005 Report Server WebApp log:

w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing MaxScheduleWait to default value of '1' second(s) because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing DatabaseQueryTimeout to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing InstanceName to default value of '' because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing ProcessRecycleOptions to default value of '0' because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing RunningRequestsScavengerCycle to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing RunningRequestsDbCycle to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing RunningRequestsAge to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing CleanupCycleMinutes to default value of '10' minute(s) because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing WatsonFlags to default value of '1064' because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing WatsonDumpOnExceptions to default value of 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException' because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to default value of 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing SecureConnectionLevel to default value of '1' because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing WebServiceUseFileShareStorage to default value of 'False' because it was not specified in Configuration file.
w3wp!ui!1!25/8/2005-12:57:15:: e ERROR: The request failed with HTTP status 400: Bad Request.
w3wp!ui!1!25/8/2005-12:57:15:: e ERROR: HTTP status code --> 500
---Details---
System.Net.WebException: The request failed with HTTP status 400: Bad Request.
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Page.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
w3wp!ui!1!25/8/2005-12:57:20:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)
w3wp!ui!5!25/8/2005-12:57:44:: e ERROR: The request failed with HTTP status 400: Bad Request.
w3wp!ui!5!25/8/2005-12:57:44:: e ERROR: HTTP status code --> 500

Thanks in advance,

Anderson

Good Evening Anderson!
I had some "weird" problems immediately after I installed the SQL2005 JUNE CTP when initially launching RS. I do not know for cetain what your problems relates to above - but for some strange reason with my problem which I getting similar issues to your post was that the Virtual Directories (Reports and ReportServer) within IIS were somehow messed up!
So I deleted the two virtual directories and recreated and ensured I was not using 'Enable Anonymous Access' and I specified Integrated Windows Authentication.
Restarted IIS and everything was ok after that.
What version of Visual Studio are you using -? I had similar problems with bad requests without registering RS after install to .Net as well.
Best Regards,
Joe|||

Hi, Joe

Thanks for your interest.

I was having some trouble with the RS db. I've followed the steps below and now everything's ok:

1. Unistall RS;
2. Ensure RS database is deleted;
3. Reinstall RS;
4. Use RS Configuration Tool to setup everything.
Actually, I'm using SQL2K5April CTP and VS2K5 Beta 2.

Best regards,

Anderson

|||Hello Anderson!
these little things you have to go through to make things work sometimes!
Did you know the August SQL 2005 CTP is now available as well?
Best regards,
joe

error 37000

I tried to run my application linked to sqlserver DB. Iobtain this message :
Erreur d'exécution 40002
37000 : [Microsoft][ODBC SQL Server Driver] [SQL Server] the log file for
database "app" si full. Back up the transaction log for the database to free
up some log space
someboy could tell me it there is a possibility to do not write in log file ?
this transaction log is always active ?
thanks
tft
Hi,
Backup the Transaction log (See BACKUP LOG command in books online) and try
accessing the database. If you do not requite a
transaction log backup then change the recovery model for your database to
'SIMPLE'. After that truncate the transaction log using
BACKUP LOG <DBNAME> WITH TRUNCATE_ONLY
The above strategies will clear your trasnaction log.
Thanks
Hari
SQL Server MVP
"ft" <ft@.discussions.microsoft.com> wrote in message
news:19A68E4F-3C6A-4502-AE07-B4C8C9DBFBA3@.microsoft.com...
>I tried to run my application linked to sqlserver DB. Iobtain this message
>:
> Erreur d'excution 40002
> 37000 : [Microsoft][ODBC SQL Server Driver] [SQL Server] the log file for
> database "app" si full. Back up the transaction log for the database to
> free
> up some log space
> someboy could tell me it there is a possibility to do not write in log
> file ?
> this transaction log is always active ?
> thanks
> tft

error 37000

I tried to run my application linked to sqlserver DB. Iobtain this message :
Erreur d'exécution 40002
37000 : [Microsoft][ODBC SQL Server Driver] [SQL Server] the log
file for
database "app" si full. Back up the transaction log for the database to free
up some log space
someboy could tell me it there is a possibility to do not write in log file
?
this transaction log is always active ?
thanks
tftHi,
Backup the Transaction log (See BACKUP LOG command in books online) and try
accessing the database. If you do not requite a
transaction log backup then change the recovery model for your database to
'SIMPLE'. After that truncate the transaction log using
BACKUP LOG <DBNAME> WITH TRUNCATE_ONLY
The above strategies will clear your trasnaction log.
Thanks
Hari
SQL Server MVP
"ft" <ft@.discussions.microsoft.com> wrote in message
news:19A68E4F-3C6A-4502-AE07-B4C8C9DBFBA3@.microsoft.com...
>I tried to run my application linked to sqlserver DB. Iobtain this message
>:
> Erreur d'excution 40002
> 37000 : [Microsoft][ODBC SQL Server Driver] [SQL Server] the l
og file for
> database "app" si full. Back up the transaction log for the database to
> free
> up some log space
> someboy could tell me it there is a possibility to do not write in log
> file ?
> this transaction log is always active ?
> thanks
> tft

error 37000

I tried to run my application linked to sqlserver DB. Iobtain this message :
Erreur d'exécution 40002
37000 : [Microsoft][ODBC SQL Server Driver] [SQL Server] the log file for
database "app" si full. Back up the transaction log for the database to free
up some log space
someboy could tell me it there is a possibility to do not write in log file ?
this transaction log is always active ?
thanks
tftHi,
Backup the Transaction log (See BACKUP LOG command in books online) and try
accessing the database. If you do not requite a
transaction log backup then change the recovery model for your database to
'SIMPLE'. After that truncate the transaction log using
BACKUP LOG <DBNAME> WITH TRUNCATE_ONLY
The above strategies will clear your trasnaction log.
Thanks
Hari
SQL Server MVP
"ft" <ft@.discussions.microsoft.com> wrote in message
news:19A68E4F-3C6A-4502-AE07-B4C8C9DBFBA3@.microsoft.com...
>I tried to run my application linked to sqlserver DB. Iobtain this message
>:
> Erreur d'exécution 40002
> 37000 : [Microsoft][ODBC SQL Server Driver] [SQL Server] the log file for
> database "app" si full. Back up the transaction log for the database to
> free
> up some log space
> someboy could tell me it there is a possibility to do not write in log
> file ?
> this transaction log is always active ?
> thanks
> tft

Error 245 terminates execution

I noticed some funny behaviour in a business application i support, it turned
out it was caused by a conversion error.
Essentially this code emmulates my problem:
PRINT 'Start'
PRINT CONVERT(int,'a')
PRINT 'End'
This code will yield the following result:
Start
Server: Msg 245, Level 16, State 1, Line 2
Syntax error converting the varchar value 'a' to a column of data type int.
In other words the conversion attempt stops execution of the script, despite
error 245 only being a severity 16 error. Does anyone else get this problem?
Suggestions?Some datatype conversion errors will terminate the batch, that is true. There is no setting that
will change it. Code defensively and check for this in the code so it doesn't happen. Also see the
error handling articles at www.sommarskog.se.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sbt" <sbt@.discussions.microsoft.com> wrote in message
news:36C8E4B5-9282-4207-92B2-868D7755ADDE@.microsoft.com...
>I noticed some funny behaviour in a business application i support, it turned
> out it was caused by a conversion error.
> Essentially this code emmulates my problem:
> PRINT 'Start'
> PRINT CONVERT(int,'a')
> PRINT 'End'
> This code will yield the following result:
> Start
> Server: Msg 245, Level 16, State 1, Line 2
> Syntax error converting the varchar value 'a' to a column of data type int.
> In other words the conversion attempt stops execution of the script, despite
> error 245 only being a severity 16 error. Does anyone else get this problem?
> Suggestions?|||sbt
Wait for SQL Server 2005 to be used
BEGIN TRY
CATCH......
END TRY
"sbt" <sbt@.discussions.microsoft.com> wrote in message
news:36C8E4B5-9282-4207-92B2-868D7755ADDE@.microsoft.com...
> I noticed some funny behaviour in a business application i support, it
turned
> out it was caused by a conversion error.
> Essentially this code emmulates my problem:
> PRINT 'Start'
> PRINT CONVERT(int,'a')
> PRINT 'End'
> This code will yield the following result:
> Start
> Server: Msg 245, Level 16, State 1, Line 2
> Syntax error converting the varchar value 'a' to a column of data type
int.
> In other words the conversion attempt stops execution of the script,
despite
> error 245 only being a severity 16 error. Does anyone else get this
problem?
> Suggestions?|||Ye, having a background as a C++ programmer, I'm really missing proper
exception handling, however the database server is not likely to be upgraded
any time soon, so sadly thats not an option.
"Uri Dimant" skrev:
> sbt
> Wait for SQL Server 2005 to be used
> BEGIN TRY
> CATCH......
> END TRY
>
> "sbt" <sbt@.discussions.microsoft.com> wrote in message
> news:36C8E4B5-9282-4207-92B2-868D7755ADDE@.microsoft.com...
> > I noticed some funny behaviour in a business application i support, it
> turned
> > out it was caused by a conversion error.
> >
> > Essentially this code emmulates my problem:
> > PRINT 'Start'
> > PRINT CONVERT(int,'a')
> > PRINT 'End'
> >
> > This code will yield the following result:
> > Start
> > Server: Msg 245, Level 16, State 1, Line 2
> > Syntax error converting the varchar value 'a' to a column of data type
> int.
> >
> > In other words the conversion attempt stops execution of the script,
> despite
> > error 245 only being a severity 16 error. Does anyone else get this
> problem?
> > Suggestions?
>
>

Error 245 terminates execution

I noticed some funny behaviour in a business application i support, it turned
out it was caused by a conversion error.
Essentially this code emmulates my problem:
PRINT 'Start'
PRINT CONVERT(int,'a')
PRINT 'End'
This code will yield the following result:
Start
Server: Msg 245, Level 16, State 1, Line 2
Syntax error converting the varchar value 'a' to a column of data type int.
In other words the conversion attempt stops execution of the script, despite
error 245 only being a severity 16 error. Does anyone else get this problem?
Suggestions?
Some datatype conversion errors will terminate the batch, that is true. There is no setting that
will change it. Code defensively and check for this in the code so it doesn't happen. Also see the
error handling articles at www.sommarskog.se.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sbt" <sbt@.discussions.microsoft.com> wrote in message
news:36C8E4B5-9282-4207-92B2-868D7755ADDE@.microsoft.com...
>I noticed some funny behaviour in a business application i support, it turned
> out it was caused by a conversion error.
> Essentially this code emmulates my problem:
> PRINT 'Start'
> PRINT CONVERT(int,'a')
> PRINT 'End'
> This code will yield the following result:
> Start
> Server: Msg 245, Level 16, State 1, Line 2
> Syntax error converting the varchar value 'a' to a column of data type int.
> In other words the conversion attempt stops execution of the script, despite
> error 245 only being a severity 16 error. Does anyone else get this problem?
> Suggestions?
|||sbt
Wait for SQL Server 2005 to be used
BEGIN TRY
CATCH......
END TRY
"sbt" <sbt@.discussions.microsoft.com> wrote in message
news:36C8E4B5-9282-4207-92B2-868D7755ADDE@.microsoft.com...
> I noticed some funny behaviour in a business application i support, it
turned
> out it was caused by a conversion error.
> Essentially this code emmulates my problem:
> PRINT 'Start'
> PRINT CONVERT(int,'a')
> PRINT 'End'
> This code will yield the following result:
> Start
> Server: Msg 245, Level 16, State 1, Line 2
> Syntax error converting the varchar value 'a' to a column of data type
int.
> In other words the conversion attempt stops execution of the script,
despite
> error 245 only being a severity 16 error. Does anyone else get this
problem?
> Suggestions?
|||Ye, having a background as a C++ programmer, I'm really missing proper
exception handling, however the database server is not likely to be upgraded
any time soon, so sadly thats not an option.
"Uri Dimant" skrev:

> sbt
> Wait for SQL Server 2005 to be used
> BEGIN TRY
> CATCH......
> END TRY
>
> "sbt" <sbt@.discussions.microsoft.com> wrote in message
> news:36C8E4B5-9282-4207-92B2-868D7755ADDE@.microsoft.com...
> turned
> int.
> despite
> problem?
>
>

Error 245 terminates execution

I noticed some funny behaviour in a business application i support, it turne
d
out it was caused by a conversion error.
Essentially this code emmulates my problem:
PRINT 'Start'
PRINT CONVERT(int,'a')
PRINT 'End'
This code will yield the following result:
Start
Server: Msg 245, Level 16, State 1, Line 2
Syntax error converting the varchar value 'a' to a column of data type int.
In other words the conversion attempt stops execution of the script, despite
error 245 only being a severity 16 error. Does anyone else get this problem?
Suggestions?Some datatype conversion errors will terminate the batch, that is true. Ther
e is no setting that
will change it. Code defensively and check for this in the code so it doesn'
t happen. Also see the
error handling articles at www.sommarskog.se.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sbt" <sbt@.discussions.microsoft.com> wrote in message
news:36C8E4B5-9282-4207-92B2-868D7755ADDE@.microsoft.com...
>I noticed some funny behaviour in a business application i support, it turn
ed
> out it was caused by a conversion error.
> Essentially this code emmulates my problem:
> PRINT 'Start'
> PRINT CONVERT(int,'a')
> PRINT 'End'
> This code will yield the following result:
> Start
> Server: Msg 245, Level 16, State 1, Line 2
> Syntax error converting the varchar value 'a' to a column of data type int
.
> In other words the conversion attempt stops execution of the script, despi
te
> error 245 only being a severity 16 error. Does anyone else get this proble
m?
> Suggestions?|||sbt
Wait for SQL Server 2005 to be used
BEGIN TRY
CATCH......
END TRY
"sbt" <sbt@.discussions.microsoft.com> wrote in message
news:36C8E4B5-9282-4207-92B2-868D7755ADDE@.microsoft.com...
> I noticed some funny behaviour in a business application i support, it
turned
> out it was caused by a conversion error.
> Essentially this code emmulates my problem:
> PRINT 'Start'
> PRINT CONVERT(int,'a')
> PRINT 'End'
> This code will yield the following result:
> Start
> Server: Msg 245, Level 16, State 1, Line 2
> Syntax error converting the varchar value 'a' to a column of data type
int.
> In other words the conversion attempt stops execution of the script,
despite
> error 245 only being a severity 16 error. Does anyone else get this
problem?
> Suggestions?|||Ye, having a background as a C++ programmer, I'm really missing proper
exception handling, however the database server is not likely to be upgraded
any time soon, so sadly thats not an option.
"Uri Dimant" skrev:

> sbt
> Wait for SQL Server 2005 to be used
> BEGIN TRY
> CATCH......
> END TRY
>
> "sbt" <sbt@.discussions.microsoft.com> wrote in message
> news:36C8E4B5-9282-4207-92B2-868D7755ADDE@.microsoft.com...
> turned
> int.
> despite
> problem?
>
>

Error 242, Severity : 16, State : 3.

I tried to transfer the data from one application to another. Under the SQL Profile it stated Error 242, Severity : 16, State : 3. Any idea? SQL provide an logging "sa" error. I have checked the password for the application setup, odbc and SQL, they are a
ll identical. The applications have no problem
Hi Li,
I feel that this error is no way related to a Login issue. This MSG: 242
normally comes while you give invalid date format on
datetime data type.
set language us_english
declare @.k datetime
set @.k='25/07/2004'
Thanks
Hari
MCDBA
"Li" <Li@.discussions.microsoft.com> wrote in message
news:EE5A8215-D6C3-4A3B-BDBF-F10BFA93E58E@.microsoft.com...
> I tried to transfer the data from one application to another. Under the
SQL Profile it stated Error 242, Severity : 16, State : 3. Any idea? SQL
provide an logging "sa" error. I have checked the password for the
application setup, odbc and SQL, they are all identical. The applications
have no problem
>

Error 242, Severity : 16, State : 3.

I tried to transfer the data from one application to another. Under the SQL
Profile it stated Error 242, Severity : 16, State : 3. Any idea? SQL provide
an logging "sa" error. I have checked the password for the application setu
p, odbc and SQL, they are a
ll identical. The applications have no problemHi Li,
I feel that this error is no way related to a Login issue. This MSG: 242
normally comes while you give invalid date format on
datetime data type.
set language us_english
declare @.k datetime
set @.k='25/07/2004'
Thanks
Hari
MCDBA
"Li" <Li@.discussions.microsoft.com> wrote in message
news:EE5A8215-D6C3-4A3B-BDBF-F10BFA93E58E@.microsoft.com...
> I tried to transfer the data from one application to another. Under the
SQL Profile it stated Error 242, Severity : 16, State : 3. Any idea? SQL
provide an logging "sa" error. I have checked the password for the
application setup, odbc and SQL, they are all identical. The applications
have no problem
>

Error 242, Severity : 16, State : 3.

I tried to transfer the data from one application to another. Under the SQL Profile it stated Error 242, Severity : 16, State : 3. Any idea? SQL provide an logging "sa" error. I have checked the password for the application setup, odbc and SQL, they are a
ll identical. The applications have no problem
If you look in BooksOnLine you will see that the error is regarding data
conversion and not permissions.
"The conversion of a char data type to a datetime data type resulted in an
out-of-range datetime value."
You have at least one bad datetime value somewhere.
Andrew J. Kelly SQL MVP
"Li" <Li@.discussions.microsoft.com> wrote in message
news:A51B52EC-7EE8-4FDB-B7B6-6F85AF781557@.microsoft.com...
> I tried to transfer the data from one application to another. Under the
SQL Profile it stated Error 242, Severity : 16, State : 3. Any idea? SQL
provide an logging "sa" error. I have checked the password for the
application setup, odbc and SQL, they are all identical. The applications
have no problem
|||In the profiler trace, you have the spid that raised the error. Look for
the BatchStarting, or if captured - the StmtStarting event and look for the
values that were passed in this query that caused the error. It could be
erronoues data in this case, and not so much the odbc driver at fault.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Error 242, Severity : 16, State : 3.

I tried to transfer the data from one application to another. Under the SQL Profile it stated Error 242, Severity : 16, State : 3. Any idea? SQL provide an logging "sa" error. I have checked the password for the application setup, odbc and SQL, they are all identical. The applications have no problemHi Li,
I feel that this error is no way related to a Login issue. This MSG: 242
normally comes while you give invalid date format on
datetime data type.
set language us_english
declare @.k datetime
set @.k='25/07/2004'
Thanks
Hari
MCDBA
"Li" <Li@.discussions.microsoft.com> wrote in message
news:EE5A8215-D6C3-4A3B-BDBF-F10BFA93E58E@.microsoft.com...
> I tried to transfer the data from one application to another. Under the
SQL Profile it stated Error 242, Severity : 16, State : 3. Any idea? SQL
provide an logging "sa" error. I have checked the password for the
application setup, odbc and SQL, they are all identical. The applications
have no problem
>

Error 242, Severity : 16, State : 3

I tried to transfer the data from one application to another. Under the SQL
Profile it stated Error 242, Severity : 16, State : 3. Any idea? SQL provide
an logging "sa" error. I have checked the password for the application setu
p, odbc and SQL, they are a
ll identical. The applications have no problem.Hi Li,
I feel that this error is no way related to a Login issue. This MSG: 242
normally comes while you give invalid date format on
datetime data type.
set language us_english
declare @.k datetime
set @.k='25/07/2004'
Thanks
Hari
MCDBA
"Li" <Li@.discussions.microsoft.com> wrote in message
news:B29BFC56-EBF9-48AB-8DE4-8898659BEC9C@.microsoft.com...
> I tried to transfer the data from one application to another. Under the
SQL Profile it stated Error 242, Severity : 16, State : 3. Any idea? SQL
provide an logging "sa" error. I have checked the password for the
application setup, odbc and SQL, they are all identical. The applications
have no problem.