eric Posted October 26, 2015 Posted October 26, 2015 hello, i am trying to deploy my application in a standalone server. herebelow a sub-set of my servermodule. I ma working wih Delphi XE8 and unigui 0.99.50.1200 under Windows 10. The server stay in loading...... and when I activate the debugger under chrome, i get the fllowing error: error 404 ressource not found with the url --> http://localhost/ext-4.2.2.1144/examples/calendar/src/util/Date.js?_dc=1445870200183 I don't uderstand why it continues to access to /ext-4.2.2.1144 when I put in extroot : ext\. Of course I copied the ext-4.2.2.1144 and all the uni.... directory from C:\Program Files (x86)\FMSoft\Framework\uniGUI to my directory (same level as the server.exe) under ext/ and uni/ thanks for your answer. eric OldCreateOrder = False OnCreate = UniGUIServerModuleCreate AutoCoInitialize = True FilesFolder = 'files\' TempFolder = 'temp\' ExtRoot = 'ext\' UniRoot = 'uni\' SessionTimeout = 2400000 Title = 'Release Management Cassiopae' BGColor = 8404992 CharSet = 'utf-8' AjaxTimeout = 60000 DefaultImageFormat = cfJpeg ServerMessages.InvalidSessionMessage = 'Invalid session or session Timeout.' ServerMessages.TerminateMessage = 'Web session terminated.' ExtLocale = '[Auto]' Compression.MinTextSize = 512 ServerLimits.MaxSessions = 100000 ServerLimits.MaxRequests = 500 SSL.SSLOptions.RootCertFile = 'root.pem' SSL.SSLOptions.CertFile = 'cert.pem' SSL.SSLOptions.KeyFile = 'key.pem' SSL.SSLOptions.Method = sslvTLSv1_1 SSL.SSLOptions.SSLVersions = [sslvTLSv1_1] SSL.SSLOptions.Mode = sslmUnassigned SSL.SSLOptions.VerifyMode = [] SSL.SSLOptions.VerifyDepth = 0 Options = [soShowLicenseInfo, soAutoPlatformSwitch, soAllowSessionRecording] ConnectionFailureRecovery.ErrorMessage = 'Connection Error' ConnectionFailureRecovery.RetryMessage = 'Retrying...' UniMobileRoot = 'unim\' TouchRoot = 'touch\'
Administrators Farshad Mohajeri Posted October 26, 2015 Administrators Posted October 26, 2015 'ext\' is a predefined string and maps to 'ext-[your-extjs-version]\' I will fix it in next build. Workaround: Use something else such as 'ext1\' or 'myext\'
Recommended Posts