Typical srv 3.8/4.4 Configuration Mistakes

[KEMBL]

1) MSSQL 2000 are not compatible with Windows XP, try to use MSDE (but better use W2003S + MSSQL2000)

2) When you upgrade from 3.8 to 4.4 your RM server be aware, DSN for 3.8 and 4.4 are different

RMEBrain0 - for 3.8 server
RMBrain0 - for 4.4 server

If you use different machines for RedMoon DB and RedMoon Server files, u must have same account ( login and password ) on both computers and use "With Windows NT auth"

3) when you read "open up RMSrvScript.ini, change the "Base" value to where your server is" in 3.8 readme file, that mean you must use
Base=C:\RedMoonSVR\bin\
not only Base=C:\RedMoonSVR\
and dont forget "\" at and

4) When you start server look in to c:\RedmoonSVR\Bin\Log\RMDBErrorLog\
check log file to mistakes, for example you may not have some tables
like tblUserCountLog1_200409, see tables name tblUserCountLog1_somedata and copy it to tblUserCountLog1_200409

[MentaL]

[KEMBL]

5) Black screen problem solve. Simptoms:
All server files work, RM client success connect to RM server and select char, but when press "start game" no maps arived in game area (main screen stays black, menus F1-F12 work fine).

This is simple problem with adds new char to account, by default server inserts map num 2 to table Redmoon..TblGameID1, but this map may not exists on the server!!!!
check C:\RedmoonSVR\RMServerMgr\Config\RMSrvScript.ini to solve exists or not...
My way to fix this trouble is simple edit map num to one, that exists on the server...
for example it is map 21 or 22, all deal i did after new char add...

[KEMBL]

That script is a way to terminate trouble 5)
it is MsSQL JOB, that each 3 minutes change map number 1 to 21 where Lvl=1 and MAp=2
so, player create the char wait 3 minutes and success login to game....
other way to solve that problem is up map num 2, if it works right on your server.
change N'GAME\kembl' to your Server/User name or simple add job by your self

Update RedMoon..tblGameID1 SET Map=21 where GameID in (select GameID from tblGameID1 where Lvl=1 and MAp=2)

P.S. You can't use trigers on RedMoon base, cause it is way to crash client. I don't know whay, but it is established fact.

-- JOB
-- Script generated on 24.09.2004 11:36
-- By: sa


BEGIN TRANSACTION
DECLARE @JobID BINARY(16)
DECLARE @ReturnCode INT
SELECT @ReturnCode = 0
IF (SELECT COUNT(*) FROM msdb.dbo.syscategories WHERE name = N'[Uncategorized (Local)]') < 1
EXECUTE msdb.dbo.sp_add_category @name = N'[Uncategorized (Local)]'

-- Delete the job with the same name (if it exists)
SELECT @JobID = job_id
FROM msdb.dbo.sysjobs
WHERE (name = N'RedMoon_Map_UP')
IF (@JobID IS NOT NULL)
BEGIN
-- Check if the job is a multi-server job
IF (EXISTS (SELECT *
FROM msdb.dbo.sysjobservers
WHERE (job_id = @JobID) AND (server_id <> 0)))
BEGIN
-- There is, so abort the script
RAISERROR (N'Unable to import job ''RedMoon_Map_UP'' since there is already a multi-server job with this name.', 16, 1)
GOTO QuitWithRollback
END
ELSE
-- Delete the [local] job
EXECUTE msdb.dbo.sp_delete_job @job_name = N'RedMoon_Map_UP'
SELECT @JobID = NULL
END

BEGIN

-- Add the job
EXECUTE @ReturnCode = msdb.dbo.sp_add_job @job_id = @JobID OUTPUT , @job_name = N'RedMoon_Map_UP', @owner_login_name = N'GAME\kembl', @description = N'No description available.', @category_name = N'[Uncategorized (Local)]', @enabled = 1, @notify_level_email = 0, @notify_level_page = 0, @notify_level_netsend = 0, @notify_level_eventlog = 2, @delete_level= 0
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback

-- Add the job steps
EXECUTE @ReturnCode = msdb.dbo.sp_add_jobstep @job_id = @JobID, @step_id = 1, @step_name = N'First', @command = N'Update RedMoon..tblGameID1 SET Map=21 where GameID in (select GameID from tblGameID1 where Lvl=1 and MAp=2)', @database_name = N'redmoon', @server = N'', @database_user_name = N'', @subsystem = N'TSQL', @cmdexec_success_code = 0, @flags = 0, @retry_attempts = 0, @retry_interval = 1, @output_file_name = N'', @on_success_step_id = 0, @on_success_action = 1, @on_fail_step_id = 0, @on_fail_action = 2
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
EXECUTE @ReturnCode = msdb.dbo.sp_update_job @job_id = @JobID, @start_step_id = 1

IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback

-- Add the job schedules
EXECUTE @ReturnCode = msdb.dbo.sp_add_jobschedule @job_id = @JobID, @name = N'RM_Map_up', @enabled = 1, @freq_type = 4, @active_start_date = 20040924, @active_start_time = 0, @freq_interval = 1, @freq_subday_type = 4, @freq_subday_interval = 3, @freq_relative_interval = 0, @freq_recurrence_factor = 0, @active_end_date = 99991231, @active_end_time = 235959
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback

-- Add the Target Servers
EXECUTE @ReturnCode = msdb.dbo.sp_add_jobserver @job_id = @JobID, @server_name = N'(local)'
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback

END
COMMIT TRANSACTION
GOTO EndSave
QuitWithRollback:
IF (@@TRANCOUNT > 0) ROLLBACK TRANSACTION
EndSave:

[KEMBL]

6) One of wrong deal with RedMoon database in table names,
it must to be up to date so name like 'tblUserLog1_200407'
is not valid ( that example from file battlematch(kor).zip )

ftp://wu.aaanet.ru/redmoon/procedure...ate_tables.txt
You mast to create All that procedures from file abow, and start it when needs

RM_MAKE_tblBattleZoneScore_TABLE - daily (at 00:01 )

This, start each month (at 00:01 every first day of month)
RM_MAKE_tblDeathLog1_TABLE
RM_MAKE_tblGamePlayLog1_TABLE
RM_MAKE_tblItemLog1_TABLE
RM_MAKE_tblLevelLog1_TABLE
RM_MAKE_tblMailLog1_TABLE
RM_MAKE_tblPAYLOG_TABLE
RM_MAKE_tblUserCountLog1_TABLE
RM_MAKE_tblUserLog1_TABLE

RM_MAKE_ALL_TABLES - starts all when you first create and start batabse

The way to solve that problem is rename bases or recreate it with valid names and indexes, check this file ftp://wu.aaanet.ru/redmoon/procedure...ate_tables.txt

[PaiNe]

1) MSSQL 2000 are not compatible with Windows XP, try to use MSDE (but better use W2003S + MSSQL2000)

how do I fix this? I had Windows XP Professional before and MSSQL worked fine, but I had to format my computer and I installed XP Professional again and it doesnt work now...hmmm

[KEMBL]

Hm, maybe this deal with XP SP1/SP2, but anyway Microsoft not alowed to do this and i think they have a reason... Read this paper http://www.microsoft.com/sql/techinf...inxpsp2faq.asp

[KEMBL]

7) Error in stored procedure RMS_INITIALIZEBILLBATTLEMATCH
Eror causes when you try to exec this procedure with SQL Query Analyzer
use redmoon
EXEC RMS_INITIALIZEBILLBATTLEMATCH 1, 0

for solve this problem open table tblCurrentBattleMatchInfo with design view in MS SQL Enterprise Manager and set up this fields like this:

bWin set by default to 0
AvgMemberLevel set by default to 1
TotalScore set by default to 0
SmashedTower set by default to 0
Score set by default to 0

Save changes

And this one trouble, one or more object contains an INSERT statement without explicit specification of target column list.! It is generally recommended to explicitly specify the column list target of the INSERT operation, but in redmoon stored procedures it is not....
see:
a)
...............
BILL_GET_NEW_ALLAT_IDX 14 Object contains an INSERT statement without explicit specification of target column list.
BILL_INSERT_ORDER_TEST 21 Object contains an INSERT statement without explicit specification of target column list.
RMS_ARMY_ADDARMYINITMEMBER 36 Object contains an INSERT statement without explicit specification of target column list.
RMS_ARMY_ADDARMYMEMBER 34 Object contains an INSERT statement without explicit specification of target column list.
............ end etc (31 total qualifying rows in example)...

b) More objects in redmoon base are referencing tables/views without specifying a schema! Performance and predictability of the application may be improved by specifying schema names...

c)

Two objects has statements using TOP without specifying an ORDER BY clause! It is generally recommended to use specify ORDER BY clause when using TOP. Otherwise, results will be plan dependent.

RMS_ARMY_WRITEARMYBASELOG and
RMS_DOITEMGROWTH Object has statements using TOP without specifying an ORDER BY clause.

Note: This ( a), b), c) ) is only bad programming style, not a mistake
A future version of SQL Server will disallow or strict usage of this syntax.

[Shoki]

Cannot connect to billDB server for 4.4 but 3.8 works fine? I changed RMEbrain0 to RMbrain0 ...

[Sl4d3]

dun change RMEBrain0 to RMBrain if you watch the ini file it RMEBrain0 in both....

[MG1978]

MSQL does work with windows xp pro.

I have service pack 1&2 installed both databases work.

And the billdb error with 4.4 is probally because they are using the wrong rmp.dll its different for both versions.