Errors

10/29/2013 00:42 olinou2#1
So im getting two errors which idk what should be done to fix it...

PS_Game


PS_Login

10/30/2013 12:47 olinou2#2
bump
10/31/2013 10:38 Mithrandir.#3
Check your NPCQuest.SData in your server files, and encrypt/decrypt it again.
10/31/2013 22:31 olinou2#4
alright so looks like the PS_Game error is fixed , now what about the PS_Login ones?

Thanks
10/31/2013 22:44 Mithrandir.#5
Reason:
Quote:
Originally Posted by treica View Post
I see that it blocking your IP, because you use the dupe fix stored procedure, so you have to introduce on the procedure your IP and run it again on DB ( in chase you have an Static IP, or do remove it) and is happens only to ranked 16, 32, 48, 64, 80 accounts because is protecting to do not get hacked your staff.
So set your IP there or change the procedure usp_Try_GameLogin_Taiwan normally how it was.!
Fix:
Code:
USE [PS_UserData]
GO
DROP PROCEDURE dbo.usp_Try_GameLogin_Taiwan
GO
/****** Object:  StoredProcedure [dbo].[usp_Try_GameLogin_Taiwan]    Script Date: 10/31/2013 22:40:59 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER OFF
GO

/****** Object:  Stored Procedure dbo.usp_Try_GameLogin_Taiwan    Script Date: 2008-6-7 18:34:05 ******/

/*==================================================
@date	2007-12-04
@brief	Login Proc( Taiwan )
==================================================*/

CREATE  Proc [dbo].[usp_Try_GameLogin_Taiwan]

@UserID 	varchar(18),
@InPassword	varchar(32),

@SessionID 	bigint,
@UserIP 	varchar(15),

-- 罹晦梱雖 蹂 檣濠, 釭該雖朝 頂睡 滲熱

@UserUID 	int = 0,
@LoginType 	smallint = 1, 
@LoginTime 	datetime = NULL

AS

SET NOCOUNT ON

DECLARE 

@Leave 		tinyint,
@Status 		smallint,

@CompanyIP 	varchar(15),
@TempIP 	varchar(15),
@Check		int

SET @Status =		 -1
SET @LoginTime = 	GETDATE()

--------------------------------------------------
SET @CompanyIP = 	'61.107.81'
SET @UserIP =		LTRIM( RTRIM(@UserIP) )
--------------------------------------------------
SET @Check = 0
--------------------------------------------------

SELECT @UserUID=UserUID, @Status=Status, @Leave=Leave FROM Users_Master WHERE UserID = @UserID

-- NotExist User OR Leave User
IF( @UserUID = 0 OR @Leave = 1 )
BEGIN
	SET @Status = -3
END
ELSE
BEGIN
	-- Check Password
	EXEC dbo.sp_LoginSuccessCheck @UserID, @InPassword, @Check output
	IF ( @@ERROR = 0 )
	BEGIN
		IF( @Check <> 1 )
		BEGIN
			SET @Status = -1
		END
	END
	ELSE
	BEGIN
		SET @Status = -1
	END

	/* Old
	SET @InEnPassword = master.dbo.fn_md5(@InPassword)
	IF ( @InEnPassword <> @EnPassword )
	BEGIN
		SET @Status = -1
	END
	*/
END

-- BlockUser Check
IF( (@Status >= 2) AND (@Status <= 6) )
BEGIN
	-- Get Block Limit Date AND Replace date text
	DECLARE @BlockEndDate datetime
	SELECT @BlockEndDate = BlockEndDate FROM Users_Block WHERE UserUID = @UserUID
	IF ( @@ROWCOUNT <> 0 )
	BEGIN
		-- Block Release
		IF ( @BlockEndDate <= @LoginTime )
		BEGIN
			SET @Status = 0
			UPDATE Users_Master SET Status = @Status WHERE UserUID = @UserUID
		END
	END
END

-- Admin IP Check(2006-02-21)
/*
IF( @Status = 16 OR @Status = 32 OR @Status = 48 OR @Status = 64 OR @Status = 80 )
BEGIN
	SET @TempIP = LEFT(@UserIP, 9)
	IF( @TempIP <> @CompanyIP )
	BEGIN
		SET @Status = -999
	END
END
*/

-- Select 
SELECT @Status AS Status, @UserUID AS UserUID

-- Log Insert
IF( @Status = 0 OR @Status = 16 OR @Status = 32 OR @Status = 48 OR @Status = 64 OR @Status = 80 )
BEGIN
	EXEC usp_Insert_LoginLog_E @SessionID=@SessionID, @UserUID=@UserUID, @UserIP=@UserIP, @LogType=0, @LogTime=@LoginTime, @LoginType=@LoginType
END
SET NOCOUNT OFF
11/01/2013 04:52 olinou2#6
Ill give a thanks for the try but that is no the solution , considering every single accounts including those with status 0, gets this error. Ima still give it a shot tomorrow. I also didnt run any ani dupe procedure for now so dont know where the link is :3 , yet you didnt know that so i cant blame you for sure.

Tyvm for trying tho, really appreciated.

Ps : since i actually didnt try it yet , i'd ask you to forgive me if im wrong, and it is the only possible answer .
11/01/2013 10:00 Mithrandir.#7
You executed the query?

And maybe the anti dupe procedure was already in the database you're using.
11/01/2013 12:52 olinou2#8
wow looks like it worked , tyvm!!

What do i have to do with that ip tho ? i shoulda write my external ip or 127.0.0.1?