Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Running WAS as a service?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Running WAS as a service?

    Hello all:

    I have our web application running on a VPS at EasyCGI. I want to make sure that the application starts up automatically and immediately after a server reboot. I've read all that I could find on this forum, but so far nothing is working quite right for me.

    1. I tried putting a shortcut to the WAS in the startup folder, but it won't start after a reboot until I connect to the server using Remoted Desktop. As soon as I connect, the WAS starts, but not until then.

    2. I tried running it as a service using AlwaysUp. It would run my application, but as I clicked around in it, I would get errors quite often. If I would refresh the page that initially returned an error, it would usually show up fine. (If I remember correctly, they were connection errors. I already uninstalled it, because the performance was definitely unsatisfactory.)

    3. I tried running it as a service using FireDaemon. It runs my application fine, except for one critical part. The email_send2() function doesn't work. Or maybe it's the MailEnable server software that I'm using. I'm not sure which. If I run WAS directly, the email works fine.

    Are there any other options that someone is using successfully? Or does anyone have any ideas why any of the things I've tried so far don't work properly?

    Thanks!
    Nathan

    #2
    Re: Running WAS as a service?

    I have a VPS account with the same outfit. Your problems are probably not related to AlwaysUp or FD. Your option 1 will always work that way, so abandon it. I've used AlwaysUp and FD without any problem for over a year. You were kinda sketchy about what the problem was on #2.
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: Running WAS as a service?

      Thanks for your response, Steve.

      I reinstalled AlwaysUp, and I could not reproduce the errors I was getting earlier. That's the good news. The bad news is that I have the same issue with AlwaysUp that I had with FireDaemon. The email_send2() function does not work. I've attached a copy of a test page that works fine when running the WAS directly, but fails when running as a service under AlwaysUp or FireDaemon. (If anyone wants to test the code, replace the placeholders with valid email addresses.)

      Can anyone verify that email_send2() does not work when running the WAS as a service? I'm trying to determine if this is a WAS, AlwaysUp, or server problem.

      Thanks!
      Nathan

      Comment


        #4
        Re: Running WAS as a service?

        FWIW, I modified the code to use the email_send() function instead, and I get the same results.

        Nathan

        Comment


          #5
          Re: Running WAS as a service?

          I guess I posted too quickly. :o The problem was solved by changing the log on settings of the service to those that I use to log on to the server. Now the email_send2() function works fine.

          Nathan

          Comment


            #6
            Re: Running WAS as a service?

            Originally posted by Nathan Zeiset View Post
            I guess I posted too quickly. :o The problem was solved by changing the log on settings of the service to those that I use to log on to the server. Now the email_send2() function works fine.

            Nathan
            I was just about to post a message that the email profiles are stored in the registry under the windows username, so logging in under a different user will give you different profiles.(or none if the profiles haven't been set for that windows user).

            Glad you were able to work through it.
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.
            "Make it as simple as possible, but not simpler."
            Albert Einstein

            http://www.iadn.com/images/media/iadn_member.png

            Comment


              #7
              Re: Running WAS as a service?

              Glad you answered that because I was scratching my head - I use email_send() and email_send2() along with AlwaysUp with no issue.
              Steve Wood
              See my profile on IADN

              Comment


                #8
                Re: Running WAS as a service?

                Nathan,

                I could use some help with this. I am having the problem of not being able to send email from the app server, which is run as a service by AlwaysUp.

                I have looked through User Rights Assignment, Desktop Security Settings, the help file, and I can't see where to set the logon for the service to match my logon account.

                Bill.

                Comment


                  #9
                  Re: Running WAS as a service?

                  OK, I found the settings when I Edit the app server service. Email still not working, but I will poke around and probably figure it out.

                  Bill.

                  Comment


                    #10
                    Re: Running WAS as a service?

                    Test it from the server by right-clicking on teh Alpha icon, go to Email and your profile and test send. If that works, your send_email should work. Email configuration must be done on the server, the client computer you published from has NO bearing on the email settings on the server.
                    Steve Wood
                    See my profile on IADN

                    Comment


                      #11
                      Re: Running WAS as a service?

                      Oddly I had never noticed the Test button before. That made testing much easier!

                      The smpt server external to the server's network that I had been trying to use still does not want to work from the app server. It does work from a runtime copy on the server - I have triple checked that settings are the same between runtime and app server, but who knows.

                      On the app server I finally got an smpt server on their internal network to work, so I am declairing victory!

                      Bill.

                      Comment

                      Working...
                      X