Troubleshooting

Aestan Tray Menu built in service manager is not handled by Bearsampp in the Service menu  


You can take look to the Windows Event Log to find out where the error occurred or use the Debug menu of the service (like Apache, MySQL or MariaDB).

If you still can't solve it you can try creating an issue and perhaps the community can help you solve it.

Could not execute menu item (internal error)
[EAccessViolation] Access violation at address XXXXXXXX in module ‘neard.exe’. Read of address XXXXXXXX

Bearsampp tray icon is based on Aestan Tray Menu.

There are several cases to reproduce this error :

• Execute multiple actions at the same time.
• Do not wait for an action ends.
• A procedure error with Bearsampp based on bearsampp.ini file.

For the last case you will have to create an issue.

Services loaded with NSSM have the PATH environment variable rewritten.
Impacted services are : Apache, Mailpit, Xlight and Memcached.

As you can see you can add paths relative to the Bearsampp root folder (eg. www).

In the phpinfo the Apache environment will look like this :

And as you can see some paths are automatically added :

• %SystemRoot%\system32
• %SystemRoot%
• %SystemRoot%\system32\Wbem
• %SystemRoot%\system32\WindowsPowerShell\v1.0
• BEARSAMPP_PATH\bin\apache\apache*\bin
• BEARSAMPP_PATH\bin\php\php*
• BEARSAMPP_PATH\bin\php\php*\pear
• BEARSAMPP_PATH\bin\php\php*\imagick
• BEARSAMPP_PATH\bin\nodejs\nodejs*
• BEARSAMPP_PATH\bin\svn\svn*
• BEARSAMPP_PATH\tools\composer\composer*
• BEARSAMPP_PATH\tools\git\git*\bin
• BEARSAMPP_PATH\tools\imagemagick\imagemagick*
• BEARSAMPP_PATH\tools\python\python*\bin
• BEARSAMPP_PATH\tools\ruby\ruby*\bin

If you wish to use the terminal you can use php -m and this will give you a list of all loaded modules

When PostgreSQL is started as a service, you can have this error :

LOG:  database system was shut down at 2013-06-13 00:54:33 UTC
LOG:  autovacuum launcher started
LOG:  database system is ready to accept connections
FATAL:  role "John" does not exist
 done
server started

This happens when you run pg_ctl start with the -w (wait) option like Bearsampp, because it will try a test connection with a user that does not exist (in your case). But that’s not really a problem (except for the confusing error message), because that proves that the server is up.

According to VMWare Knowledge base article, connection to VMware Workstation Server (the shared virtual machines) is administered by the VMware Host Agent service. The service uses TCP ports 80 and 443. This service is also used by other VMware products, including VMware Server and vSphere, and provides additional capabilities.

This will block the execution of the Apache service on Bearsampp.

You can change the VMware Workstation Server ports when you install Workstation and after Workstation is installed.
To connect from a second instance of Workstation to Workstation Server:

• Go to File > Connect to Server.
• Enter the host name or IP address of the host machine running Workstation Server.
• When prompted, login with the username and password of a local administrator on the remote host.

Note: If the VMware Workstation Server service running on the remote server is not using the default port, you must specify the port number. For example, remotehost:444.

With the Shared VMs Workstation preferences, you can also disable the server. To access the Shared VMs Workstation preferences:

• Go to Edit > Preferences.
• Click the Shared VMs tab.

Bearsmapp icon has 3 states :

•  : All enabled services are started
•  : One or more enabled services are stopped
•  : All enabled services are stopped

To check from the Services Manager, click Start > Run and type services.msc and check the status of Bearsampp* services :
You can also see the state of services by going to http://localhost

Xdebug 3 completely changed how things are done.  You can find a document explaining those changs here.
The default port is now 9003 instead of 9000
Due to those changes we've changed the way all future php releases are configured.
the [xdebug] section in php.ini will be changed to this. 

[xdebug]
xdebug.mode = debug
xdebug.start_with_request = trigger
xdebug.output_name = cachegrind.out.%t.%p
xdebug.output_dir = "~BEARSAMPP_LIN_PATH~/tmp/cachegrind"
xdebug.var_display_max_children = "1024"
xdebug.var_display_max_depth = "8192"
xdebug.var_display_max_data = "32768"
xdebug.max_nesting_level = "250"