x64 Windows 2003 VPS MatchAgent and Connect Issue

[rozandas]

Hi to all of the RaGEZONE GunZ Dev Dept. =)

I would really appreciate the help. I'm going ballistic here.
I'm currently trying to migrate my Gunz server from my Home-PC (32-bit OS)
to a Windows Server 2003 x64 Enterprise VPS.
I've Successfully set up the database on the VPS with 0 problems, but
when migrating my Gunz server files(exact copy), MatchServer and MatchAgent don't seem to be working properly.

Here's what happens on the VPS:

i start MatchServer.exe - ok (Both Process and Application Appears)
i start Locator.exe - ok (Both Process and Application Appears)
i start MatchAgent.exe - FAIL (Process Appears but the application doesn't)

In TaskManager, MatchAgent only shows as a process but not as an Application.
Unlike how it worked fine at the Home-PC Everything worked flawlessly (Both Process and Application Appears) for each and every one of them

I tried ignoring the fact the MatchAgent wasn't showing up and just tried connecting using the Gunz client.
I did connect fine but after a couple of seconds being connected match server closes on the VPS and I get a connection fail on the Client.

Note:
I followed The Guide of BR/Jan/June Guide
and used Server Files of BR/Jan/June Xiao's Rev5

To my knowledge, I believed everything is in order.
I'm also aware of the 64-bit install of SQL Server 2005 on the VPS and the x64 Visual C++ Runtime install on the server. The IP and Ports are Correct (hence a WAN-IP blocked out in the IMG Below) and ping-check between the servers isn't a problem.

I'm Really sure somethings up with the MatchAgent.

But, the problem still remains on the VPS
i start MatchAgent.exe - FAIL (Process Appears but the application doesn't)

and i can't connect:
"I tried ignoring the fact the MatchAgent wasn't showing up and just tried connecting using the Gunz client.
I did connect fine but after a couple of seconds being connected match server closes on the VPS and I get a connection fail on the Client."

[MentaL]

[Linear88]

The image is normal since you're on a vista platform.

[randy1234]

maybe u did not PortFowrd?

[Linear88]

maybe u did not PortFowrd?

Port Forwarding is not the problem in this case. >.>

Disable DEP.

[rozandas]

Port Forwarding is not the problem in this case. >.>

Disable DEP.

In the VPS [Windows Server 2003 ENT x64]
I disabled the entire DEP and that crashed the SQL servers and everything. So, I just rolled back.
Then, I tried to just turnoff the DEP for the MatchAgent, Locator, and MatchServer. Yet, there doesn't seem to be any changes.

*The issue is with MWS-2003 Ent x64 not Windows Vista.

[Wucas]

loool on the picture of the matchserver on the vps, scroll up on the matchserver, they are exactly the same.

Idk about the matchagent issue, have you asked your vps provider to preform a restart?

[NinethGod]

The MatchServers are exactly the same. You need to scroll up bro.

Does the server work if you open
MatchServer.exe
MatchAgent.exe
Locator.exe

Maybe something else is blocking it or you edit something wrong. Check it over.

[rozandas]

The Server Runs with the exe's open but the MatchAgent is still an issue and the connect is still an issue.

A topic Merge with : http://forum.ragezone.com/f311/match...4x-vps-595728/

btw, Using A FranTech Performance VPS. NOT an RO Package. it's completely isolated from it.

[Guy]

loool on the picture of the matchserver on the vps, scroll up on the matchserver, they are exactly the same.

Idk about the matchagent issue, have you asked your vps provider to preform a restart?

You can perform a restart yourself on a VPS, assuming you have administrative access.

Port Forwarding is not the problem in this case. >.>

Disable DEP.

DEP being a security feature to limit the amount of damage from an overflow, disabling it certainly wouldn't be the solution.

[AlphaMatrix]

You can perform a restart yourself on a VPS, assuming you have administrative access.



DEP being a security feature to limit the amount of damage from an overflow, disabling it certainly wouldn't be the solution.

what would be the solution then? lol

[KingMG]

Heeelp, i got the same problem:(

[SukhO]

me tooooo

[ElternalFire]

You need 32bit =D
I have 2003 and 32bit and everything works fine.

[PenguinGuy]

me tooooo

I had this problem as well. But I figured I shouldn't bump a thread with an idiotic post such as that.

[GzFKoron]

me tooooo

Wow, talk about bumping a 8 month thread.