I've scripted a sql trace for Sql Server 2000 and added the filename in the appropreate location andthe result is a column called ErrorCode with a value of 14. Can anyone tell me what this error code means and what could be infered about what I need to resolve it?
Thanks,
Marc
When a user finally confirms his order in a shopping cart application (using MS-Access as the backend), the items he has purchased are populated in a Access DB table named Orders & his personal details (like name, mail, billing address, shipping address etc.) are populated in another table named CustDetails. Both the DB tables have a column named OrderID. This column is the Primary Key in the CustDetails table & the Foreign Key in the Orders table. The Session.SessionID becomes the unique OrderID.After confirming an order, if the user refreshes the page, the app will try to populate the same Session.SessionID in the CustDetails table but since the column OrderID is a Primary Key column in the table CustDetails, it won't accept duplicate OrderIDs. Under such circumstances, an OleDbException will be raised.Since a DB app can throw other OleDbExceptions other than the one about which I mentioned above, I want to display custom error messages to the user. For e.g. if he refreshes the page after confirming his order, I want to display a message saying "Your order has already been placed".To do this, I tried using the ErrorCode property of the OleDbException class but what I found is the ErrorCode changes from time to time! Had a particular ErrorCode been assigned to the error, I could have done something like this (assuming that the ErrorCode for the above error is -12345 which is constant):Try 'some codeCatch ex As OleDbException If (ex.ErrorCode = -12345) Then Response.Write("Your order has already been placed") ElseIf (ex.ErrorCode = <some other constant ErrorCode>) Then Response.Write("Another custom error message") End IfEnd TryBut I can't do the above since the ErrorCode changes from time to time.So how do I display custom error messages to users under such circumstances?Of course, I can use the Message property of the OleDbException class but that would be a rather tedious workaround.
View 4 Replies View RelatedHi,
In my local , application is working fyn...but when i had uploaded in the file in Live and executed the SP's ,It is showing up the error 8144...
Whene i had checked in google it is showing:
has too many arguments specified: Msg 8144....But i had not passed to many arguments...
(The same SP is working in local but not in live)...
The related files also i had shifted to live...
This is the SP I Have used....
while Submiting iam getting error
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
--- STORED PROCEDURE USP_CREATE_USER TO SAVE THE APPLICATION INFORMATION INTO DATABASE
CREATE PROCEDURE dbo.USP_CREATE_APPLICATION_ONLINE
(
@ApplicationID INT,
@Broker CHAR(1),
@Name VARCHAR(30),
@Phone VARCHAR(15),
@Email VARCHAR(50),
@LoanAmount Decimal(9),
@LoanPurpose VARCHAR(200),
@DeedType_ID VARCHAR(50),
@SubDeedType_ID INT,
@DeedAddress VARCHAR(200),
@City VARCHAR(50),
@CountryID INT,
--@StateID INT,
@MarketValue Decimal(9),
@LoanTerm INT,
@Appraised CHAR(3),
@Comments VARCHAR(50),
@DeleteFlag VARCHAR(1),
@RETURN int OUT,
@ERRORCODE int OUT
)
AS
set @RETURN=1
SET NOCOUNT ON
iF EXISTS(SELECT * FROM APPLICATION_ONLINE WHERE ApplicationID=@ApplicationID)
Begin
BEGIN TRANSACTION TRANSUPDATE
UPDATE APPLICATION_ONLINE SET
ApplicationID = @ApplicationID,
Broker = @Broker,
[Name] = @Name,
Phone = @Phone,
Email = @Email,
LoanAmount=@LoanAmount,
LoanPurpose=@LoanPurpose,
DeedType_ID=@DeedType_ID,
SubDeedType_ID=@SubDeedType_ID,
DeedAddress =@DeedAddress,
City =@City,
CountryID = @CountryID,
MarketValue = @MarketValue,
LoanTerm = @LoanTerm,
Appraised =@Appraised,
Comments =@Comments
WHERE [ApplicationID] = @ApplicationID
SET @ERRORCODE=@@ERROR
IF @ERRORCODE <> 0
BEGIN
ROLLBACK TRANSACTION TRANSUPDATE
SET @ERRORCODE=@@ERROR
RETURN
END
ELSE
BEGIN
COMMIT TRANSACTION TRANSUPDATE
SET @ERRORCODE=50002
RETURN
END
END
else
BEGIN
BEGIN TRANSACTION TRANSINSERT
INSERT INTO APPLICATION_ONLINE(
ApplicationID,
Broker,
[Name],
Phone,
Email,
LoanAmount,
LoanPurpose,
DeedType_ID,
SubDeedType_ID,
DeedAddress,
City,
CountryID,
-- StateID,
MarketValue,
LoanTerm,
Appraised ,
Comments,
DeleteFlag
)
VALUES
(
@ApplicationID,
@Broker,
@Name,
@Phone,
@Email,
@LoanAmount,
@LoanPurpose,
@DeedType_ID,
@SubDeedType_ID,
@DeedAddress,
@City,
@CountryID,
-- @StateID,
@MarketValue,
@LoanTerm,
@Appraised,
@Comments,
@DeleteFlag
)
SET @ERRORCODE=@@ERROR
IF @ERRORCODE <> 0
BEGIN
ROLLBACK TRANSACTION TRANSINSERT
SET @ERRORCODE=50004
RETURN
END
ELSE
BEGIN
COMMIT TRANSACTION TRANSINSERT
SET @ERRORCODE=50001
RETURN
END
END
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
Thanks
This is a request to the Microsoft SSIS staff.
I did a search for the keywords in the description and can already see a lot of people frustrated about this.
A lot of well designed integration packages will route error messages to an error table or file.
SSIS appends a couple of extra error columns called ErrorCode and ErrorColumn. At runtime, an extra
column is visible in the DataViewer called ErrorCode - Description.
The description is hardcoded into the dtsmsg.h file in the SDK folder of Sql Server.
This file is very hard to parse.
Can some from SSIS please post an XML or CSV file with all the error codes and descriptions for us to download please.
This will be such a big help in debugging.
Many Thanks.
Shailen Sukul
Software Architect/Developer/Consultant
(BSc | Mcts (Biztalk (IP)) | Mcpd | Mcts (Web, Win, Dist Apps) | Mcsd.NET | Mcsd | Mcad)
Ashlen Consulting Services Pty Ltd
(http://www.ashlen.com.au)
MSN | Skype | GTalk Id: shailensukul
Ph: +61 0421 277 812
Fax: +61 3 9011 9732
Linked In: http://www.linkedin.com/in/shailensukul
Hi,I'm trying to execute server-side trace with SqlServer 2000 oncluster. After scripting trace by Profiler I executed this script inQueryanalyzer and got error code 12. According to BOL this code saysthat file is not created but I don't know why, is there are anyobstacles which preventing to add this trace??Does anybody had that problem?If it helps I added script which I tried to execute:-- Create a Queuedeclare @rc intdeclare @TraceID intdeclare @maxfilesize bigintset @maxfilesize = 5exec @rc = sp_trace_create @TraceID output, 0, N'C:Profiler_result
esult.trc', @maxfilesize, NULLif (@rc != 0) goto error-- Client side File and Table cannot be scripted-- Set the eventsdeclare @on bitset @on = 1exec sp_trace_setevent @TraceID, 10, 1, @on/*here are n-setevents*/exec sp_trace_setevent @TraceID, 43, 35, @on-- Set the Filtersdeclare @intfilter intdeclare @bigintfilter bigintexec sp_trace_setfilter @TraceID, 1, 1, 6, N'history'exec sp_trace_setfilter @TraceID, 1, 1, 6, N'move_history'exec sp_trace_setfilter @TraceID, 10, 0, 7, N'SQL Profiler'exec sp_trace_setfilter @TraceID, 35, 1, 6, N'kis'-- Set the trace status to startexec sp_trace_setstatus @TraceID, 1-- display trace id for future referencesselect TraceID=@TraceIDgoto finisherror:select ErrorCode=@rcfinish:goThanks in advance for any adviceRegards,Bartolo
SSIS automatically adds the columns ErrorCode and ErrorColumn to the error pipe routing bad rows. However, both these columns appear to be meaningless. We need to translate the error column to the actual problem column and the error code to a meaningful error. ErrorColumn is the more important issue for us. The question is 'Are these just useless columns? If not, how do we translate them into something useful?'
Thanks
Installed SQL express 2005 w/Studio Manager. Everything installed Ok except got an error IIS was not running or not installed.
When installing a software program, when it tries to create the database I get an error at the initialization:
An error has occured while processing an SQL statement. Please refer to the system administrator guide for further assistance.
ERRORCODE:37000
ERROR:CREATE DATABASE failed. Some of the file names cound not be created. Check related errors.
SQL STATEMENT
CREATE DATABASE xxxx
Has anyone seen or know a fix for this? Thanks in advance.
Hi again!
I have another problem, this time with a flatfile source component. The file is pretty simple organized and in fact everything works as expected.
The file itself comes from an FTP server, so it is not available at designtime. For setting up the flatfile source i downloaded it, but afterwards i delete it, set 'dalayvalidation' to true and try to execute.
FTP download works fine, the file is there but then i get the errormessage:
Copier ErrorCodes [586]: The data type for "output column "Flat File Source Error Output Column" (610)" is DT_NTEXT, which is not supported with ANSI files. Use DT_TEXT instead and convert the data to DT_NTEXT using the data conversion component.
When i try to set the datatype of the Error Output Column (610) to DT_NEXT i only get an errormessage telling me that this would not be a valid value for this property.
The only chance i have to get it working again is to completely delete the flatfile-source, readd and setup it again, then everything works... but only until i remove the files and try to download them via FTP. It's strange :-( and annoying.
Anyone any idea?
kind regards,
Wolfgang
Hello,
Within my SSIS packages I use a logging logic quite similar as the one described by Jamie Thomson here : http://blogs.conchango.com/jamiethomson/archive/2005/06/11/SSIS_3A00_-Custom-Logging-Using-Event-Handlers.aspx
But I still have a small "problem". When my package end with success the ErrorCode returned at the OnInformation event handler level is :
0x4001100B
1073811467
DTS_I_COMMITTINGTRANSACTION
Committing distributed transaction started by this container.
Instead of :
0x40013001
1073819649
DTS_MSG_PACKAGESUCCESS
Package "__" finished successfully.
Another example.
When there's an integrity constraint violation, I've got the following ErrorCode returned :
0xC0047021
-1073450975
DTS_E_THREADFAILED
Thread "__" has exited with error code __.
Instead of :
0xC020907D
-1071607683
DTS_E_OLEDBDESTINATIONADAPTERSTATIC_INTEGRITYVIOLATION
The data value violates integrity constraints.
Anyone has a clue ?
Thanks a lot by advance.
Cheers,
Bertrand
I am transfering a database from sql server 2000 to sql server 2005 using copy database wizard.
I have this error coming up error
Error: ERROR : errorCode=-1073548784 description=Executing the query "EXEC dbo.sp_grantdbaccess @loginame = N'Testusername', @name_in_db = N'username' " failed with the following error: "The login already has an account under a different user name.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. helpFile= helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC} StackTrace: at Microsoft.SqlServer.Management.Dts.DtsTransferProvider.ExecuteTransfer() at Microsoft.SqlServer.Management.Smo.Transfer.TransferData() at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.TransferDatabasesUsingSMOTransfer()
How do i handle this error...looked online but didn't find right answers...
Please let me know
I have an OLE-DB Command transformation that inserts a row. If the insert SQL command fails for some reason, I use the "Redirect Row" option to send the row to another OLE-DB Command transformation that logs the error on that row to a "failed rows" table. In this table I log the ErrorCode and ErrorColumn values that come with the error path from the first OLE-DB Command.
OK, that's all working great. However, here's the kicker: there's no error description value. The ErrorCode value, naturally, is the decimal form of an HRESULT--for example, -1071607696. Without some further information, however, this code is not useful for troubleshooting.
Has anyone figured out a trick here? I'm not even certain that this is an SSIS HRESULT, since it could for all I know be from the OLE-DB layer, the database layer, or somewhere else.
Thanks,
Dan
I am currently redirecting lookup failures into error tables with ErrorCode and ErrorColumn. It works fine until I want to transfer data into the archived database. The SSIS pacakage generate by SQL Exporting tool is throwing an "duplicate name of 'output column ErrorCode and ErrorColumn" error. This is caused by oledb source error output. The error output automatically add ErrorCode and ErrorColumn to the error output selection and not happy with it.
I think the question is down to "How to importing/exporting data when table contains ErrorCode or ErrorColumn column?"
I'm sorry for asking this, as I'm sure tha the answer is in one of the 208 matches I found searching on "ErrorCode". Unfortunately, this project is overdue and I need a solution fairly soon.
I should add that I've only been developing in SSIS since August 2007.
I have a complicated package, loading about 17 outputs of the XML Source into staging tables. I have been using the error outputs of any standard components I use, out of faith that, if Microsoft provided them, then they should be useful for something. I've been directing all of the error outputs for one of the 17 "tables" from the XML Source into a Union All, and then into an "Error staging table", for each of the 17 outputs. This table includes all of the possible columns, but permits nulls for all of them. It also incldues the ErrorCode and ErrorColumn.
Unfortunately, if these latter two are useful for anyting, I haven't found it yet.
Right now, working with our first "mostly real" data, I'm getting 100% of my input rows written into error tables. Unfortunately, the information in the tables are of limited use in determining what went wrong. For instance, the ErrorColumn seems only to be populated if there was a specific error with a specific column. The Lookup component, doesn't seem to populate ErrorColumn, even if only one column was used for the lookup! No information about the component producing the error output is supplied in the error output, either, which makes it difficult to determine which of the five or so possible error outputs is the one that produced the particular error row.
This proves that I'm missing something simple. How do people handle errors? In my custom components, I learned to use the Fire* methods to produce detailed messages before redirecting the row to the error output, but this sort of thing is not available through the standard components.
Do I really have to create a separate "add useful information to the error output" component, and use it on each error output?
Sorry for the attitude, but just when I think I'm winning, SSIS brings me back down to earth!