powered by Jive Software

Installing Spark to Windows 2008 Terminal Server

Trying to install Spark on a Windows 2008 Terminal Server and not having much success. I’ve tried 2.5.8 and 2.6.0 exe and msi installers and all have the same result.

Spark will install fine and works for the administrative account it is installed with. It will not run for any other account. I have tried regular users, power users, and administrators with no success!

Can anyone provide some guidance on getting Spark to work on a Windows Terminal server? I see from other posts that it CAN work…

Cheers,

Robin

your best bet might be to get something like process monitor and see where it is failing.

http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

Have watched Spark through Process Monitor and after opening the jar files it starts trying to open and write files to the Administrator profile folders. Spark must be getting this location from somewhere…

If I re-run the installer from another admin account, that account can now use Spark until another admin account runs the installer.

Is there a shared install switch or something that I am missing?

what is it trying to access? I don’t have an 08 TS to play with right now.

CreateFile

C:\Users\administrator.CMEDGROUP\Spark\logs
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\spark.properties
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\spark.properties
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs\errors.log
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs\errors.log.lck
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs\errors.log.1.lck
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs\errors.log.2.lck
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs\errors.log.3.lck
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs\errors.log.4.lck
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs\errors.log.5.lck
ACCESS DENIED
.
.
.
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs\errors.log.95.lck
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs\errors.log.96.lck
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs\errors.log.97.lck
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs\errors.log.98.lck
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs\errors.log.99.lck
ACCESS DENIED
CreateFile
C:\Users\administrator.CMEDGROUP\Spark\logs\errors.log.100.lck
ACCESS DENIED
CreateFile
C:\Program Files\Spark\logs\error.log
ACCESS DENIED

I have attached a complete output from ProMon in CSV format as well.
Logfile.CSV.zip (33405 Bytes)

wow, that is kinda goofy. I just tried it on an 08 server (not specifically TS server) and didn’t get that problem. by the time its writing to those log files it should be writing to the user directory. can you check c:\program files\spark\starter.ini and/or spark.ini and make sure the output file and error file aren’t something goofy (like the admin profile)

If you do a run as under a limited user, does it write to those log files or does it write to its own user directory? if it writes to the admin log files what is it writing?

Maybe this is a clue… starter.ini and spark.ini do not exist in the c:\program files\spark folder…

Just reinstalled using the MSI rather than the EXE and the INI files now get created. However, the problem of trying to open the logs under the Administrator’s userprofile folder remains.

Found the problem!

Looks like the Administrator profile was copied over top of the default profile in order to create a new baseline. The Spark settings appear to get set into the HKU section which is a problem in this scenario.

Thanks for the help.

Cheers,

Robin

who ever copied over the Administrator profile should be flogged

glad you got it working.