PDA

View Full Version : cant activate



shark
12-10-2009, 03:49 PM
hello,

do you have some problems with your server? im trying all day long to activate but i cant. i normally registered, but cant activate

i shut down all firewalls/avs, deleted holdemmanager.exe.ldat and nothing works. im usin win xp and running as admin

I get this message: Could not activate license at server.
The remote name could not be resolved: 'www.holdemmanager.net'

details

License Failure Details
--------------------------------------------------
12/10/2009 7:46:57 PM
HoldemManager.frmLoading
--------------------------------------------------

Errors connecting to the server.

DETAILS

Could not activate license at server.
The remote name could not be resolved: 'www.holdemmanager.net'

System Info
--------------------------------------------------

Timestamp: 2009-12-10T19:46:57 / 2009-12-10T20:46:57
Entry Assembly: HoldemManager, Version=1.9.1.0, Culture=neutral, PublicKeyToken=null
Base Directory: C:\Program Files\RVG Software\Holdem Manager\
Platform: Windows XP Professional 32-bit Service Pack 2 [5.1 Build 2600]
OS Version: 5.1.2600.131072
CLR Version: 2.0.50727.42
Process Bitness: 32-bit
Culture: en-US / en-US
Encoding: Central European (Windows)
IIS Available: True
Machine Code: TV99T-NA4TK-1G9HU-QXJ33-F9TUA

Assemblies
--------------------------------------------------

Accessibility *
2.0.0.0 / 2.0 R 42 for .NET 2.0
C:\WINDOWS\assembly\GAC_MSIL\Accessibility\2.0.0.0 __b03f5f7f11d50a3a\Accessibility.dll

ctjem_yg *
3.2.2000.0 / 2.0 R 42 (RTM 050727-4200) for .NET 2.0 (RTM 050727-4200)


DeployLX.Licensing.v3 *
3.2.2000.0 / 3.2 R 3751 for .NET 2.0
C:\Program Files\RVG Software\Holdem Manager\DeployLX.Licensing.v3.dll

DevComponents.DotNetBar2 *
7.9.9.3 / 7.9.9.3 for .NET
C:\Program Files\RVG Software\Holdem Manager\DevComponents.DotNetBar2.dll

HoldemManager *
1.9.1.0 / 1.9.1.0 for .NET
C:\Program Files\RVG Software\Holdem Manager\HoldemManager.exe

mscorlib
2.0.0.0 / 2.0 R 42 for .NET 2.0
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\msco rlib.dll

System
2.0.0.0 / 2.0 R 42 for .NET 2.0
C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5 c561934e089\System.dll

System.Configuration
2.0.0.0 / 2.0 R 42 for .NET 2.0
C:\WINDOWS\assembly\GAC_MSIL\System.Configuration\ 2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll

System.Drawing
2.0.0.0 / 2.0 R 42 for .NET 2.0
C:\WINDOWS\assembly\GAC_MSIL\System.Drawing\2.0.0. 0__b03f5f7f11d50a3a\System.Drawing.dll

System.Web
2.0.0.0 / 2.0 R 42 for .NET 2.0
C:\WINDOWS\assembly\GAC_32\System.Web\2.0.0.0__b03 f5f7f11d50a3a\System.Web.dll

System.Web.Services
2.0.0.0 / 2.0 R 42 for .NET 2.0
C:\WINDOWS\assembly\GAC_MSIL\System.Web.Services\2 .0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll

System.Windows.Forms
2.0.0.0 / 2.0 R 42 for .NET 2.0
C:\WINDOWS\assembly\GAC_MSIL\System.Windows.Forms\ 2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll

System.Xml
2.0.0.0 / 2.0 R 42 for .NET 2.0
C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b 77a5c561934e089\System.Xml.dll

i hope youll answer asap

netsrak
12-10-2009, 04:31 PM
Yes, we have DNS problems at the moment.



“We are sorry for the technical difficulties you are experiencing. The problem is temporary and was caused when the company that host our servers reset the DNS records which tells how to resolve which IP address HoldemManager.net is located at. You will be able to access the website and/or use your existing copy of HM/OM as soon as your ISP updates their DNS record for HoldemManager.net The vast majority of ISP’s have already updated their DNS information and most others should updated within the next few hours. Once again, our sincere apologies for this inconvenience.”

shark
12-10-2009, 04:34 PM
ok, thank you very much

TheLastNail
12-10-2009, 11:16 PM
i have the same problem after reinstalling

where can we await this to be fixed? cant play at all :(

fozzy71
12-11-2009, 12:23 AM
Unfortunately you will have to wait for your DNS server to update.

henkeone
12-11-2009, 06:35 AM
Use googles DNS-service or a similar service and it will work fine. :D

perenolde
12-11-2009, 11:09 AM
i hope they will update them soon, iam still waiting :(

fozzy71
12-11-2009, 01:47 PM
Possible temporary workaround:


1) Go to C:\Windows\System32\drivers\etc, copy the hosts file to your Desktop and open it with notepad.
2) Scroll to the bottom and add the following line: 66.77.69.66 holdemmanager.net
3) Save and close the file.
4) Copy the file back to C:\Windows\System32\drivers\etc.
5) Overwrite the existing file if being asked.

Please note, that you have to remove this line after 3-4 days from the file again.

loosemymind
12-11-2009, 02:21 PM
Possible temporary workaround:


1) Go to C:\Windows\System32\drivers\etc, copy the hosts file to your Desktop and open it with notepad.
2) Scroll to the bottom and add the following line: 66.77.69.66 holdemmanager.net
3) Save and close the file.
4) Copy the file back to C:\Windows\System32\drivers\etc.
5) Overwrite the existing file if being asked.

Please note, that you have to remove this line after 3-4 days from the file again.

doesnt work on my pc:(

Apanage
12-11-2009, 02:48 PM
The fix doesn't work for me either

Alex $pirin
12-11-2009, 05:19 PM
I`m not an advanced system administrator, but can give you a decision, that worked for me.
I followed Fozzy`s recommendation and added new line to "hosts", but it didn`t work. Then I remembered, that a week ago google made public dns resolver and tried it... ACTIVATION SUCCESFULL!
to use google`s DNS you have to change your provider`s DNS with these:

Prefered - 8.8.8.8
Alternative - 8.8.4.4
that`s all

I hope it will help you and please forgive me for my poor English)

fozzy71
12-11-2009, 07:19 PM
The fix doesn't work for me either

It is no longer a DNS issue and seems to be a routing issue on the part of our hosting company. Unfortunately we are at their mercy to get this resolved.

fozzy71
12-12-2009, 05:29 PM
Over the past 24 hours, a small % of customers were unable to load www.holdemmanager.net or successfully authenticate their HEM or OM product codes when starting the software. The issue was isolated to a network issue with the company that host the HEM server and they have advised us that it has now been resolved. We sincerely apologize for any inconvenience for those that were affected by this.