i cant find any good fix about this error
evertime i try to make a acc this error comes up
duplicate row. player already excist
any1 found solution to this error yet
i cant find any good fix about this error
evertime i try to make a acc this error comes up
duplicate row. player already excist
any1 found solution to this error yet
Are you creating using the stored procedure directly or gm tools?
gm tools with sql 2000
I should have watched my mouth and not said/talked shit to DeadlyData telling him things like your are not welcome here because then I become the one who is truly not welcome here.
Try executing the cabal_registerAccount stored procedure in the account db, right-click and execute manually. The tools are calling the same procedure so i need to know if it is the stored procedure or my tools causing the error. All i can report from the tools is what the DB tells me and the DB is capable of returning some very funny values that just don't make sense.
Also, try running the query below on your account DB. You should get a series of numbers and letters back and not NULL. If you get a null it means your xp_md5 support is broken so check it under the Extended procedures folder of your "master" db, check the path is correct and that the permissions on the .dll isn't restricting access.
Code:select dbo.fn_md5('test')
ok i will try it thanks
and i have already try other name
That worked for me, at some point the xp_md5.dll path got changed to something like "D:\cabal\xp_..." so redirecting it to the System32 copy did the job, thanks :DOriginally Posted by chumpywumpy
check your xp_md5.dll path (C:\xp_md5.dll)
I should have watched my mouth and not said/talked shit to DeadlyData telling him things like your are not welcome here because then I become the one who is truly not welcome here.
this is what i found i know there something wrong with md 5 file
Extract or build the DLL file xp_md5.dll and place it in C:\Program Files\Microsoft SQL or win32
Server\MSSQL\Binn (or wherever appropriate). A precompiled DLL is in the Release directory of the source distribution.
Create an Extended Stored Procedure called xp_md5 in the "master" database. Right-click "Extended Stored Procedures" under the master database in the Server Manager and click "New Extended Stored Procedure...". Enter xp_md5 for the "Name" and for the "Path", enter the full path to xp_md5.dll.
Note: If you want to add it manually:
Collapse Copy Code
USE master;
EXEC sp_addextendedproc 'xp_md5', 'xp_md5.dll'
Create a user-defined function for each database in which you plan to use the MD5 procedure. Right-click "User Defined Functions" under the appropriate database(s) and click "New User Defined Function...". Enter the following: Collapse Copy Code
CREATE FUNCTION [dbo].[fn_md5] (@data TEXT)
RETURNS CHAR(32) AS
BEGIN
DECLARE @hash CHAR(32)
EXEC master.dbo.xp_md5 @data, -1, @hash OUTPUT
RETURN @hash
END
(Optional) Create other user-defined functions to let you specify the data length (for substrings, BINARY and other fixed-width types). In this particular function, we take an IMAGE for input and an optional LENGTH. A negative LENGTH value causes the DLL to try to compute the length of the input automatically (this is the default): Collapse Copy Code
CREATE FUNCTION [dbo].[fn_md5x] (@data IMAGE, @len INT = -1)
RETURNS CHAR(32) AS
BEGIN
DECLARE @hash CHAR(32)
EXEC master.dbo.xp_md5 @data, @len, @hash OUTPUT
RETURN @hash
END
Usage:
FN_MD5
The User-Defined Functions can be used as follows:
Collapse Copy Code
-- Sample SQL statement:
-- fn_md5() tries to automatically calculate the length of the input string
SELECT dbo.fn_md5('Hello world!');
-- fn_md5x() takes an optional length arg for substrings, fixed-width types, etc.
SELECT dbo.fn_md5x('Hello world!', 12);
Output for both statements:
Collapse Copy Code
86fb269d190d2c85f6e0468ceca42a20
XP_MD5: EXEC xp_md5 <@data> [@length = -1] [@hash OUTPUT]
To use the Extended Stored Procedure directly:
Collapse Copy Code
-- Sample command:
EXEC master.dbo.xp_md5 'Hello world!'
Output:
Collapse Copy Code
86fb269d190d2c85f6e0468ceca42a20
Or if you want the result saved to a variable instead:
Collapse Copy Code
DECLARE @hash CHAR(32)
EXEC master.dbo.xp_md5 'Hello world!', -1, @hash OUTPUT
PRINT @hash
Output:
Collapse Copy Code
86fb269d190d2c85f6e0468ceca42a20
Examples
Collapse Copy Code
-- These are just examples for use with the given functions above.
-- Feel free to create your own functions that take the input type you want.
-- Use CAST() with caution, as it may truncate and have other unintended consequences.
-- For TEXT, NTEXT, VARCHAR:
SELECT dbo.fn_md5(data) FROM table;
-- For VARBINARY:
SELECT dbo.fn_md5(CAST(data AS VARCHAR(8000))) FROM table;
-- For IMAGE:
SELECT dbo.fn_md5x(data, DEFAULT) FROM table;
-- For CHAR: (we can use LEN() on this fixed-width type to trim the padding)
SELECT dbo.fn_md5x(data, LEN(data)) FROM table;
-- For NCHAR: (we can use LEN() on this fixed-width type to trim the padding)
SELECT dbo.fn_md5x(CAST(data AS CHAR(4000)), LEN(data)) FROM table;
-- For BINARY:
SELECT dbo.fn_md5x(data, 12) FROM table;
-- FOR SQL_VARIANT:
SELECT dbo.fn_md5x(CAST(data AS VARCHAR(8000)), DATALENGTH(data)) FROM table;
Miscellaneous
For purposes of speed, I did not include any real input data verification (e.g., type checking, data length checking, etc.). I opted to exclude that in order to maximize speed, as I originally wrote this for use in an application that inserts millions of rows at a time. I also know that I'm always calling the procedure properly. If you want to make it more robust - like if you do not know what kind of data will be passed to the function - then I highly recommend you add those safeguards.
One last thing, I added the linker option /OPT:NOWIN98 to minimize the binary size. This may cause a performance hit on non-NT systems (e.g., Win95, Win98, etc.). If you're using the DLL on such a system, I would recompile it without that linker option.
i have gotten that error using chumpy's gm tools only when i supply an item option value that consists of too many characters. that is the only time i have seen such an error...
Reply With Quote