Server Side ScriptMaster Crashing FMS 10

[yaacovCR]

Hi,

I am curious as to why the log file for ScriptMaster's installation on the server seems to be placed in one of my users' My Documents360 Plugin Logs folder instead of in the FileMaker ServerLogs folder. Is this possibly because I have both FileMaker Pro and FileMaker Server installed on the same machine? Could this be a cause of random crashes of 360Works's ScriptMaster, which happens on my machine, if the user's My Documents folder was unexpectedly deleted, which happens on my machine with Citrix Users?

Warm regards,

Yaacov

Please help!

[Jesse Barnum]

Yaacov, the current version of ScriptMaster will crash if it cannot write log files. We've fixed that in our development build, and should be releasing an update shortly.

As to writing to the user's documents directory instead of the FileMaker Server log file, the reason for this is because I don't currently know of any way to get a path to the server log directory from the registry, environment variable, or any other language-independent way on Windows. If I can find an answer to this, we will move the log files into the FileMaker Server logs directory.

[yaacovCR]

Hi Jesse, thanks for the reply!

Just looking at my registry using FileMaker Server 10.0.2.206, I see within the following key:

HKEY_LOCAL_MACHINESOFTWAREFileMakerFileMaker Server10.0Services

a name/value pair of "InstallLocation" and "C:Program FilesFileMakerFileMaker Server"

The logs directory is just this path with "Logs" appended to it.

Alternatively, there is another key for your plugin:

HKEY_LOCAL_MACHINESOFTWAREFileMakerFileMaker Server10.0Plug-ins2

With name/value pairs:

"Name" and "360Works ScriptMaster" and

"Filename" and "filewin:/C:/Program Files/FileMaker/FileMaker Server/Database Server/Extensions/360Works_ScriptMaster.fmx"

Perhaps you could put the log file in a subdirectory of the Extensions directory, parallel to what the xDBC plugin does - it seems to put the logging files in this subdirectory:

"C:Program FilesFileMakerFileMaker ServerDatabase ServerExtensionsxDBC Supportlogging"

Thanks so much for your help! I will check back with the next release of your wonderful product!

C:Program FilesFileMakerFileMaker Server

[Jesse Barnum]

Yaacov, that looks very promising. I'll look into implementing that in an upcoming build of our products. Thanks for the research!

[yaacovCR]

Hi Jesse!

Has this been implemented in any of the new releases? I am eagerly awaiting being able to use ScriptMaster from the server!

Warm regards,

Yaacov

[Jesse Barnum]

Hi Yaacov - we have not implemented your suggestion (yet) about reading the location from the registry, although it's a great solution and I plan on doing that.

We have, however, fixed the issue of crashing if it can't write the logs.

So to summarize, you should now be able to use ScriptMaster 3.22 on the server, although it may not write a server log file.

[yaacovCR]

Hi Jesse!

I have upgraded Java on our Server to Update 20, and now 3.22 and 3.33 versions of the plugin no longer load unless the "username/My Documents" folder exists. As a workaround, I created the folder where ScriptMaster expects it to be, and thankfully 3.33 now loads, but this is actually an unstable situation, as I believe the directory could get wiped at any time.

Are there plans to change the log file directory for the server version based on my earlier suggestion? Or, another workaround would be to allow the user to select a directory for the log files. Or, can you put back the ability not to crash when ScriptMaster cannot write the log file?

Warmest, warmest regards and many thanks,

Yaacov