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



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

SQLReporting 9 error SOLVED

  • Filter
  • Time
  • Show
Clear All
new posts

  • SQLReporting 9 error SOLVED

    SQLReporting 9 error SOLVED:

    After I worked on this more than a week without coming close to a solution, Jerry Brightbill stepped up and figured it out. Thank you Jerry!!

    Security was not set on the project reports. Security had been set on the workspace reports, but was not for the project reports (oversight by me). The error only occurred with the report server running. When the server rejected the report request with a 403 security error, somehow the request was still passed to the report server. But since the values passed were invalid, the report server reported the error before the 403 was sent, and that caused the SQLReporting 9 error.

    I made the changes Jerry mentioned and now all the reports work great. There is no way I would have figured this out without Alpha and Jerry stepping in to help. Hopefully this will help someone else that is at their wits end like I was. I would also like to thank Clive and Jason at ZebraHost for doing everything they could possibly do to help me figure this out.
    Epigate Software, LLC.

    [email protected]

  • #2
    Re: SQLReporting 9 error SOLVED

    I spoke too soon. This has reoccurred about 4-5 time since the last post. Customers are getting angry about it and I guess I cannot blame them. I have tried everything again, and nothing seems to work. It looks like there are many others with the same problem. Has anyone found a solution to this?
    Epigate Software, LLC.

    [email protected]


    • #3
      Re: SQLReporting 9 error SOLVED

      Have you tried turning off the report server?


      • #4
        Re: SQLReporting 9 error SOLVED

        are session variables involved to determine users? I just posted about an unusual situation I have concerning when to use an equals sign and when not to. Now truth be told I know nothing about your problem nor have I used reports yet so my journey there is ahead of me. I do however know that the equals sign in front of a session variable in a grid threw off the actual value of it being inserted vs referenced VS recommended in a UX and if you are using that for security perhaps there is a problem there...just a guess - good luck and I hope it works out for you -
        Energy and persistence conquer all things.
        Benjamin Franklin
        NWCOPRO: Nuisance Wildlife Control Software My Application: "Without forgetting, we would have no memory at what was I saying?"


        • #5
          Re: SQLReporting 9 error SOLVED

          Thanks Jim, but yes I tried it off and on many times. still no luck.

          Charles, I do use session variables, but even on reports that have no filters and use no variables, it still does the same error.

          I was informed that this has been corrected in the next build but that is only in prerelease, so I am hesitant in using it, but I may not have a choice.
          Epigate Software, LLC.

          [email protected]



          • #6
            Re: SQLReporting 9 error SOLVED

            Sounds like they understand your problem and have corrected it. It has been MY experience that you can revert back to the original version if the pre-release doesn't work out with NO problems. I am sure there would be a voice in opposition but again I have had zero problems going from version to version and quite honestly feel the pre-releases are usually very well thought out with no problems at all only enhancements. Read ALL of the changes and breaking changes to decide what you want to do.
            Anyways, just make a full backup and go for it - thats my advice.

            Worst case scenario you have people upset that the app isnt working but isnt that where your at now?
            If you can test it yourself first - do that in a seperate environment but I think we can all attest to the fact that nothing ever prepares you for day one of a new roll out...
            NWCOPRO: Nuisance Wildlife Control Software My Application: "Without forgetting, we would have no memory at what was I saying?"


            • #7
              Re: SQLReporting 9 error SOLVED

              JR, I've loaded many of the pre-releases trying to solve our reporting issues including the latest and have rolled back without issue.
              The sql9 issue and other reporting problems started for me after this release. 1794-4227.