The following warnings occurred:
Warning [2] Use of undefined constant SAPI_NAME - assumed 'SAPI_NAME' (this will throw an Error in a future version of PHP) - Line: 3388 - File: inc/functions.php PHP 7.4.33-nmm6 (Linux)
File Line Function
/inc/functions.php 3388 errorHandler->error
/showthread.php 116 build_archive_link
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm6 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/inc/functions.php 3324 build_forum_breadcrumb
/showthread.php 195 build_forum_breadcrumb
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm6 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/showthread.php 195 build_forum_breadcrumb




SphereCommunity / General Discussion / UO/Sphere Discussion v / Sphere Errors


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Sphere Errors
Author Message
dagger4k
Journeyman
*

Posts: 194
Likes Given: 1
Likes Received: 12 in 12 posts
Joined: Mar 2012
Reputation: 0



Post: #1
Sphere Errors
Hey firstly, do you guys still use the bug tracker? If so ill start posting issues on there again.

I just found out then why sphere shows this error.

Code:
21:27:DEBUG:__ thread (5292) __ |  # | _____ function _____________ | ticks passed from previous function start ______
21:27:DEBUG:>>         5292     |  0 | NetworkManager::processAllInput | +0
21:27:DEBUG:>>         5292     |  1 |   NetworkInput::processInput | +0
21:27:CRITICAL:"Access Violation" (0xfffd5ba9), in Sphere::Tick() #3 "network-in"

This error is the result of the Ultima Online client being open when you start up sphere. I guess it cant access the right things or get the right permissions while UO is runnning.

Steps to re-create issue.
1) Open up sphere
2) Open up client and log in
3) Close sphere (or in some cases let it crash :] )
4) while the client is still hanging with the "connection lost gump" leave it be.
5) Open up sphere again (note. with the client still in the connection lost state)
6) this error will appear

Ps. I just found out if the client does not stay on the connection lost screen then the error does not appear.
(This post was last modified: 04-03-2012 09:34 PM by dagger4k.)
04-03-2012 09:33 PM
Find all posts by this user Like Post Quote this message in a reply
WRWR
Journeyman
*

Posts: 212
Likes Given: 30
Likes Received: 1 in 1 posts
Joined: Mar 2012
Reputation: 1



Post: #2
RE: Sphere Errors
Heh, i got it this morning )))
04-04-2012 02:39 AM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 2 Guest(s)

Contact Us | SphereCommunity | Return to Top | Return to Content | Mobile Version | RSS Syndication