|
From: Leif M. <le...@ta...> - 2006-02-23 14:31:51
|
Ajmal,
The machine that I had seen this issue on before was at a customer
and I couldn't play
around with it. I would like to document this a little bit however.
When you log in with the remote desktop, was a user logged in
locally? It appears
that on XP, locally at least, the first user to log in becomes the
interactive desktop that
services will connect to. There doesn't appear to be a way that I could
find to provide
access to the secondary desktops. I am wondering if it never works for
remote desktops
or if it only works if the service is started when nobody is logged in
locally.
Cheers,
Leif
Ajmal Abdool wrote:
> Hi Leif,
>
> Thanks for your support. I was working via remote
> desktop. I've just connected locally and the GUI is
> displayed. The issue must be with the remote desktop.
>
> Cheers,
>
> Ajmal
>
>
> --- Leif Mortenson <le...@ta...> wrote:
>
>
>> Ajmal,
>> Your configuration looks correct. Are you
>> connecting to this 2003
>> machine
>> locally? I have seen that on some systems, the
>> service is unable to
>> access the
>> desktop if you connect from a remote terminal.
>> On Windows XP, it is possible to have multiple
>> users logs in at the
>> same time.
>> Windows services only appear to "interact" with the
>> desktop of the first
>> user
>> that logs on after (or during) the service being
>> started.
>> I don't have access to a 2003 system to play
>> around with myself..
>> Does that
>> apply to you?
>>
>> Cheers,
>> Leif
>>
>> Ajmal Abdool wrote:
>>
>>> Hi,
>>>
>>> I have an encountered an issue displaying a GUI on
>>>
>> Win
>>
>>> Server 2003. The service seems to start normally
>>>
>> but
>>
>>> no GUI is visible.
>>>
>>> This issue does not occur on Win XP Pro though. Is
>>>
>> it
>>
>>> an OS specific error? Or is there some rights that
>>> needs to be granted on the Server OS...?
>>>
>>> In my example, I'm using the Tray Example from
>>>
>> JDIC
>>
>>> but I've tested other GUIs and it still doesnt
>>>
>> work...
>>
>>> Below is a snap shot of the logs file and wrapper
>>> conf:
>>>
>>> /* Log File */
>>> STATUS | wrapper | 2006/02/22 17:56:03 | Starting
>>>
>> the
>>
>>> Test Wrapper Sample Application service...
>>> STATUS | wrapper | 2006/02/22 17:56:03 | -->
>>>
>> Wrapper
>>
>>> Started as Service
>>> STATUS | wrapper | 2006/02/22 17:56:03 |
>>>
>> Launching a
>>
>>> JVM...
>>> INFO | jvm 1 | 2006/02/22 17:56:03 | Wrapper
>>> (Version 3.1.2) http://wrapper.tanukisoftware.org
>>> INFO | jvm 1 | 2006/02/22 17:56:03 |
>>> STATUS | wrapper | 2006/02/22 17:56:05 | Test
>>>
>> Wrapper
>>
>>> Sample Application started.
>>> /* End of Log File */
>>>
>>> /* Wrapper Conf */
>>>
>>>
> #********************************************************************
>
>>> # TestWrapper Properties
>>> #
>>> # NOTE - Please use src/conf/wrapper.conf.in as a
>>> template for your
>>> # own application rather than the values
>>>
>> used
>>
>>> for the
>>> # TestWrapper sample.
>>>
>>>
> #********************************************************************
>
>>> # Java Application
>>> wrapper.java.command=java
>>>
>>> # Java Main class. This class must implement the
>>> WrapperListener interface
>>> # or guarantee that the WrapperManager class is
>>> initialized. Helper
>>> # classes are provided to do this for you. See
>>>
>> the
>>
>>> Integration section
>>> # of the documentation for details.
>>>
>>>
> wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
>
>>> # Java Classpath (include wrapper.jar) Add class
>>>
>> path
>>
>>> elements as
>>> # needed starting from 1
>>> wrapper.java.classpath.1=../lib/wrapper.jar
>>> wrapper.java.classpath.2=C:\Program
>>> Files\Java\jdic-bin\demo\Tray
>>> wrapper.java.classpath.3=C:\Program
>>> Files\Java\jdic-bin\jdic.jar
>>>
>>>
>>>
>>> # Java Library Path (location of Wrapper.DLL or
>>> libwrapper.so)
>>> wrapper.java.library.path.1=../lib
>>>
>>>
>>> # Java Additional Parameters
>>> #wrapper.java.additional.1=
>>>
>>> # Initial Java Heap Size (in MB)
>>> #wrapper.java.initmemory=3
>>>
>>> # Maximum Java Heap Size (in MB)
>>> #wrapper.java.maxmemory=64
>>>
>>> # Application parameters. Add parameters as
>>>
>> needed
>>
>>> starting from 1
>>> wrapper.app.parameter.1=Tray
>>>
>>>
>>>
>>>
> #********************************************************************
>
>>> # Wrapper Logging Properties
>>>
>>>
> #********************************************************************
>
>>> # Format of output for the console. (See docs for
>>> formats)
>>> wrapper.console.format=PM
>>>
>>> # Log Level for console output. (See docs for log
>>> levels)
>>> wrapper.console.loglevel=INFO
>>>
>>> # Log file to use for wrapper output logging.
>>> wrapper.logfile=../logs/wrapper.log
>>>
>>> # Format of output for the log file. (See docs
>>>
>> for
>>
>>> formats)
>>> wrapper.logfile.format=LPTM
>>>
>>> # Log Level for log file output. (See docs for
>>>
>> log
>>
>>> levels)
>>> wrapper.logfile.loglevel=INFO
>>>
>>> # Maximum size that the log file will be allowed
>>>
>> to
>>
>>> grow to before
>>> # the log is rolled. Size is specified in bytes.
>>>
>> The
>>
>>> default value
>>> # of 0, disables log rolling. May abbreviate
>>>
>> with
>>
>>> the 'k' (kb) or
>>> # 'm' (mb) suffix. For example: 10m = 10
>>>
>> megabytes.
>>
>>> wrapper.logfile.maxsize=0
>>>
>>> # Maximum number of rolled log files which will be
>>> allowed before old
>>> # files are deleted. The default value of 0
>>>
>> implies
>>
>>> no limit.
>>> wrapper.logfile.maxfiles=0
>>>
>>> # Log Level for sys/event log output. (See docs
>>>
>> for
>>
>>> log levels)
>>> wrapper.syslog.loglevel=NONE
>>>
>>>
>>>
> #********************************************************************
>
>>> # Wrapper Windows Properties
>>>
>>>
> #********************************************************************
>
>>> # Title to use when running as a console
>>> wrapper.console.title=Test Wrapper Sample
>>>
>> Application
>>
>>>
> #********************************************************************
>
>>> # Wrapper Windows NT/2000/XP Service Properties
>>>
>>>
> #********************************************************************
>
>>> # WARNING - Do not modify any of these properties
>>>
>> when
>>
>>> an application
>>> # using this configuration file has been
>>>
>> installed as
>>
>>> a service.
>>> # Please uninstall the service before modifying
>>>
>> this
>>
>>> section. The
>>> # service can then be reinstalled.
>>>
>>> # Name of the service
>>> wrapper.ntservice.name=testwrapper
>>>
>>> # Display name of the service
>>> wrapper.ntservice.displayname=Test Wrapper Sample
>>> Application
>>>
>>> # Description of the service
>>> wrapper.ntservice.description=Test Wrapper Sample
>>> Application Description
>>>
>>> # Service dependencies. Add dependencies as
>>>
>> needed
>>
>>> starting from 1
>>> wrapper.ntservice.dependency.1=
>>>
>>> # Mode in which the service is installed.
>>>
>> AUTO_START
>>
>>> or DEMAND_START
>>> wrapper.ntservice.starttype=AUTO_START
>>>
>>> # Allow the service to interact with the desktop.
>>> wrapper.ntservice.interactive=true
>>>
>>> wrapper.ntservice.hide-console=false
>>> /* End of Conf File */
>>>
>>> Any help would be much appreciated.
>>>
>>> Thanks,
>>>
>>> Ajmal
>>>
>>>
>>
>>
>>
> -------------------------------------------------------
>
>> This SF.Net email is sponsored by xPML, a
>> groundbreaking scripting language
>> that extends applications into web and mobile media.
>> Attend the live webcast
>> and join the prime developer group breaking into
>> this new coding territory!
>>
>>
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>>
>>
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
|