Lisence problem

Options
oman
oman ✭
edited June 2012 in Photon Server
When I change the lisence from 100 limit to unlimit 30 days trial , the photon can be started but the client can't connect to the server and vice versa, why ? What should I do to use the photon again?

Comments

  • Tobias
    Tobias admin
    Options
    Are you sure the server starts? It could look like it a while before it shuts down when the trial is expired. Have a look at the logs and allow Photon some time to start properly.
    You want to do load testing beyond 100 concurrent players? Else you don't need the trial really.
  • oman
    oman ✭
    Options
    I am sure the server starts. the problem is not the trial is expired, because the lisence 30 day trial what I used is just downloaded. Yes, I want to test the performance beyond concurrent players with the non players limited but 30 day trial lisence. every time , as long as I change the lisence, the client would can't connect to the server, I don't know it is a bug or anything else. Pls help me.
  • Kaiserludi
    Kaiserludi admin
    Options
    Have you removed the old license file? It should only be one license file in the folder, otherwise Photon would not know, which one to use.
  • oman
    oman ✭
    Options
    Yes, I removed the old license file.
  • oman
    oman ✭
    Options
    the below is the log info:

    6044: 08:45:44.569 - ---
    6044: 08:45:44.569 - Service: "Photon Socket Server" starting
    6044: 08:45:44.569 - Config File: E:\software\Photon\ExitGames-Photon-Server-SDK_v3-0-13-2524-RC5\deploy\bin_Win32\PhotonServer.config
    6044: 08:45:44.573 - Will produce at most: 10 crash dumps
    6044: 08:45:44.573 - Existing dump file: PhotonSocketServer.exe-20120507-115839-4460-4468-1.dmp
    6044: 08:45:44.574 - Existing dump file: PhotonSocketServer.exe-20120507-115846-4460-1428-2.dmp
    6044: 08:45:44.574 - Existing dump file: PhotonSocketServer.exe-20120507-115846-4460-1428-3.dmp
    6044: 08:45:44.574 - Existing dump file: PhotonSocketServer.exe-20120507-115848-4460-5000-4.dmp
    6044: 08:45:44.574 - Existing dump file: PhotonSocketServer.exe-20120507-115852-4460-5000-5.dmp
    6044: 08:45:44.574 - Existing dump file: PhotonSocketServer.exe-20120507-115857-4460-5000-6.dmp
    6044: 08:45:44.574 - Existing dump file: PhotonSocketServer.exe-20120507-115901-4460-5000-7.dmp
    6044: 08:45:44.574 - Existing dump file: PhotonSocketServer.exe-20120507-115906-4460-1144-8.dmp
    6044: 08:45:44.574 - Existing dump file: PhotonSocketServer.exe-20120507-115913-4460-5000-9.dmp
    6044: 08:45:44.574 - Max dumps to produce reduced to 1 due to existing dump files
    6044: 08:45:44.574 - Server Starting...
    6044: 08:45:44.574 - Tick count: 1208212 (wraps in: 49.6963 days)
    6044: 08:45:44.574 - Tick count 64: 1208212
    6044: 08:45:44.574 - Photon Version: 3.0.7.825
    6044: 08:45:44.575 - Config File: E:\software\Photon\ExitGames-Photon-Server-SDK_v3-0-13-2524-RC5\deploy\bin_Win32\PhotonServer.config
    6044: 08:45:44.578 - Not using performance counters as they are not currently installed. Run the service with /InstallCounters to install them.
    6044: 08:45:44.601 - About to load runtime: PhotonHostRuntime.PhotonDomainManager from PhotonHostRuntime, Culture=neutral, PublicKeyToken=02C301B61B060C4D
    6044: 08:45:44.601 - About to load CLR - versions available:
    6044: 08:45:44.601 - v2.0.50727
    6044: 08:45:44.601 - v4.0.30319
    6044: 08:45:44.601 - Configuration requests: "v2.0"
    6044: 08:45:44.601 - About to load version: "v2.0"
    6044: 08:45:44.602 - Loaded version: "v2.0.50727"
    6044: 08:45:45.157 - Photon host runtime loaded
    6044: 08:45:46.806 - License is valid.
    6044: 08:45:46.806 - Licensed for unlimited concurrent connections.
    6044: 08:45:46.806 - Max Reliable Data In Transit (awaiting ACKs) per peer : 16384 bytes
    6044: 08:45:46.806 - Per peer bandwidth limit
    6044: 08:45:46.806 - Transmit Rate Limit: 128 KB/Sec
    6044: 08:45:46.806 - Limit period: 250ms
    6044: 08:45:46.806 - Limit per period: 32768 bytes
    6044: 08:45:46.806 - Max queued data for transmission per peer: 65536 bytes
    6044: 08:45:46.806 - Minimum retransmit timeout: 200
    6044: 08:45:46.806 - Minimum ENet timeout: 5000ms
    6044: 08:45:46.806 - Maximum ENet timeout: 30000ms
    6044: 08:45:46.807 - ENetHost: Using Timer Wheel
    6044: 08:45:46.807 - About to load application: Lite from Lite
    6044: 08:45:46.807 - Auto restart is enabled for application
    6044: 08:45:46.807 - Application will restart 10000ms after the last change detected
    6044: 08:45:46.807 - Application will restart if files matching the following are changed: "dll;config"
    6044: 08:45:46.807 - Application will NOT restart if files matching the following are changed: "log4net.config"
    6044: 08:45:47.657 - Application: "Lite" started in app domain: 2
    6044: 08:45:47.657 - About to load application: LiteLobby from LiteLobby
    6044: 08:45:47.657 - Auto restart is enabled for application
    6044: 08:45:47.657 - Application will restart 10000ms after the last change detected
    6044: 08:45:47.657 - Application will restart if files matching the following are changed: "dll;config"
    6044: 08:45:47.657 - Application will NOT restart if files matching the following are changed: "log4net.config"
    6044: 08:45:48.485 - Application: "LiteLobby" started in app domain: 3
    6044: 08:45:48.485 - About to load application: MmoDemo from Photon.MmoDemo.Server
    6044: 08:45:48.485 - Auto restart is enabled for application
    6044: 08:45:48.485 - Application will restart 10000ms after the last change detected
    6044: 08:45:48.485 - Application will restart if files matching the following are changed: "dll;config"
    6044: 08:45:48.485 - Application will NOT restart if files matching the following are changed: "log4net.config"
    6044: 08:45:49.656 - Application: "MmoDemo" started in app domain: 4
    6044: 08:45:49.656 - About to load application: GameLogicServer from GameLogicServer
    6044: 08:45:49.656 - Auto restart is enabled for application
    6044: 08:45:49.656 - Application will restart 10000ms after the last change detected
    6044: 08:45:49.656 - Application will restart if files matching the following are changed: "dll;config"
    6044: 08:45:49.656 - Application will NOT restart if files matching the following are changed: "log4net.config"
    6044: 08:45:50.944 - Application: "GameLogicServer" started in app domain: 5
    6044: 08:45:50.944 - About to load application: LiteWebSockets from Lite
    6044: 08:45:51.801 - Application: "LiteWebSockets" started in app domain: 6
    6044: 08:45:51.801 - About to load application: CounterPublisher from CounterPublisher
    6044: 08:45:51.801 - Auto restart is enabled for application
    6044: 08:45:51.801 - Application will restart 10000ms after the last change detected
    6044: 08:45:51.801 - Application will restart if files matching the following are changed: "dll;config"
    6044: 08:45:51.801 - Application will NOT restart if files matching the following are changed: "log4net.config"
    6044: 08:45:52.832 - Application: "CounterPublisher" started in app domain: 7
    6044: 08:45:52.832 - About to load application: Policy from Policy.Application
    6044: 08:45:53.626 - Application: "Policy" started in app domain: 8
    6044: 08:45:53.634 - Adding TCP listener on :0.0.0.0: 4530 with a listen backlog of: 150
    6044: 08:45:53.634 - Nagle disabled
    6044: 08:45:53.638 - TCP inactivity timeout: 5000ms
    6044: 08:45:53.665 - UDP address specified as:0.0.0.0 adding listener to each available IPv4 address
    6044: 08:45:53.667 - Adding UDP listener on :192.168.1.88: 5055 with a listen backlog of: 500
    6044: 08:45:53.667 - Adding UDP listener on :127.0.0.1: 5055 with a listen backlog of: 500
    6044: 08:45:53.668 - Adding TCP Policy listener on :0.0.0.0: 843 with a listen backlog of: 150 and routing to application: "Policy"
    6044: 08:45:53.668 - TCP inactivity timeout: 5000ms
    6044: 08:45:53.668 - Adding TCP Policy listener on :0.0.0.0: 943 with a listen backlog of: 150 and routing to application: "Policy"
    6044: 08:45:53.668 - TCP inactivity timeout: 5000ms
    6044: 08:45:53.668 - Adding WebSocket TCP listener on :0.0.0.0: 9090 with a listen backlog of: 150
    6044: 08:45:53.668 - Nagle disabled
    6044: 08:45:53.668 - TCP inactivity timeout: 100000ms
    6044: 08:45:53.668 - Forcing all applications ids to: "LiteWebSockets"
    6044: 08:46:00.622 - Service is running...
    3696: 08:46:01.966 - Did not create crash dump. Already created: 1
    3696: 08:46:01.993 - Did not create crash dump. Already created: 1
    3696: 08:46:01.993 - CENetThreadPool::Process - Exception - CBuffer::Release() - m_ref is already 0
    1396: 08:46:03.821 - Did not create crash dump. Already created: 1
    1396: 08:46:05.922 - Did not create crash dump. Already created: 1
    3696: 08:46:10.083 - Did not create crash dump. Already created: 1
    3696: 08:46:10.098 - Did not create crash dump. Already created: 1
    3696: 08:46:10.098 - Did not create crash dump. Already created: 1
    3696: 08:46:10.098 - Did not create crash dump. Already created: 1
    3696: 08:46:10.098 - CENetThreadPool::Process - SEHException - 0x006e191c - ACCESS_VIOLATION
    3696: 08:46:10.697 - 006E191C (PhotonSocketServer): (filename not available): (function-name not available)
    005677FC (PhotonSocketServer): (filename not available): (function-name not available)
    00567237 (PhotonSocketServer): (filename not available): (function-name not available)
    005670A8 (PhotonSocketServer): (filename not available): (function-name not available)
    00565A5E (PhotonSocketServer): (filename not available): (function-name not available)
    00560E76 (PhotonSocketServer): (filename not available): (function-name not available)
    0040F03D (PhotonSocketServer): (filename not available): (function-name not available)
    004EE6F0 (PhotonSocketServer): (filename not available): (function-name not available)
    004EA348 (PhotonSocketServer): (filename not available): (function-name not available)
    005C2799 (PhotonSocketServer): (filename not available): (function-name not available)
    005C2823 (PhotonSocketServer): (filename not available): (function-name not available)
    76E11114 (kernel32): (filename not available): BaseThreadInitThunk
    7712B299 (ntdll): (filename not available): RtlInitializeExceptionChain
    7712B26C (ntdll): (filename not available): RtlInitializeExceptionChain
  • Tobias
    Tobias admin
    Options
    "License is valid."
    "Licensed for unlimited concurrent connections."
    ...
    "Service is running..."

    The license is not a problem.

    This is the problem:
    "CENetThreadPool::Process - Exception - CBuffer::Release() - m_ref is already 0"

    That error message is something that should be solved in the recent server SDKs. Yours is at least not the latest (see "Photon Version: 3.0.7.825").

    a) Please update to the latest Photon 3 RC SDK
    b) Re-build your application with the latest SDKs libs referenced (if you modified Lite or any application of ours)
    c) Remove old logs
    d) Start the new server and check the logs for "Exception" or anything

Cookies,
anyone?

We use cookies and related technologies to enhance your experience, show you personalised content and analyze performance and traffic on our website. By clicking on the „Accept All“ button you consent to the use of non-functional cookies and the subsequent processing of personal data to optimize our website and services as described in more detail in our Privacy and Cookie Policy.

By clicking on the „Customize or Deny all“ button you can decide otherwise. Clicking on the „Customize“ button will take you to a page where you can configure the usage of non-functional cookies (and related technologies) or deny all of them. You can access these settings at any time and also subsequently deselect cookies at any time in the footer area of our website.

ACCEPT ALL

Cookie Overview

We use the following categories of cookies and related technologies to enhance your experience, show you personalized content, and analyze performance and traffic on our website. We respect your right to privacy and accordingly you can chose to not allow some types of cookies (and related technologies). Click on the different category sliders and change our default settings to manage your cookie settings.

For more information on the specific cookies/related technologies we use and on how we use these, please see section 15 E. of our Privacy and Cookie Policy.

ABSOLUTELY NECESSARY

Authentication cookies we use are required to run our services … Cookies are required: Link

FUNCTIONAL AND MARKETING COOKIES

These cookies collect anonymous data and allow us to optimize our website and user experience. These cookies are listed here:

ANALYTICS

Help us to understand how visitors interact with our services, enables us to analyze and improve our services (also through third party analytics).