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

A couple reports throwing SQLReporting 9 error

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

    A couple reports throwing SQLReporting 9 error

    One report is a pdf from a Tabbedui and the other is a html from the same Tabbedui
    Both reports work fine from preview on the developer. Using latest v12 official build.
    Report server on.
    Sql statement works fine at the database level.

    Any ideas would be appreciated.

    Jim


    Report did not print. Error reported was:


    Layout name: I:\A5Webroot\po.a5rpt
    Layout type: report

    SQLReporting 9 - Could not create ResultSet from DataSource definition. Could not connect to Database. Error reported was: Invalid syntax for connection string. Must be formatted in one of the following ways: name1 + chr(9) + value1 + crlf() + name2 + chr(9) + value2 + crlf() ... or {name1='value1',name2='value2'...nameN='valueN'}

    #2
    Re: A couple reports throwing SQLReporting 9 error

    I got this once, I re did the connection string in the publish setting, re published and everything worked fine.
    Have no idea what caused it though.

    Comment


      #3
      Re: A couple reports throwing SQLReporting 9 error

      Tried re-publishing and other things.
      It's just two reports and they're both pdf, because of the non-column type layout. One is a purchase order and the other packing list. All our other reports are HTML and display fine.

      Tested the html reports and they return data, but when clicking pdf, off the right it says working, but no file. Excel, Word, Text and Print work.

      Also found this in the Error Stack where my HTML report displayed, but failed as PDF download.

      Basically found any report using PDF fails at this point.


      Code:
       Fri Jan 17 11:53:06 2014
       <br>Amyuni Low Level Print:<br>Layout name: I:\A5Webroot\inv_forecast.a5rpt<br>Layout type: report<br><br>SQLReporting 9 - Could not create ResultSet from DataSource definition. 
      
      Could not connect to Database. Error reported was: 
      
      Invalid syntax for connection string.
      Must be formatted in one of the following ways:
      
      	name1 + chr(9) + value1 + crlf() + name2 + chr(9) + value2 + crlf() ... or 
      
      	{name1='value1',name2='value2'...nameN='valueN'}
      <br>
      Execution Stack:
      0#1 evaluate_shared_private(           
      0#37 OOhttpdServerClientMIME(ptemp,"AppServerMain")
      0#2 A5WCallResult = evaluate_a5w_to_response(page_contents,Response,quote(" " + eval_settings.global.Request.ScriptName),eval_settings,EVALUATE_A5W_TIMEOUT,RequestBundle.RequestInfo.Filename.Path)
      0#461 a5w_report_saveAs(reportName,saveAs,filter,order,filename,global_variables(),printOptions,args,options)

      Comment


        #4
        Re: A couple reports throwing SQLReporting 9 error

        Follow up on latest post. Under Web Project Properties/PDF printing Options, turned on use microsoft xps to print pdf. No change, but now the excel, word and text downloads on html reports don't work.

        Same properties area, now also turned on Convert xps files to pdf before sending to client and all the download links work including pdf.

        The two reports that are direct PDF now error to screen with a different message.
        There's no xbasic error being reported now.

        Report did not print. Error reported was:
        Could not convert XPS to PDF. Error reported was: OLE Automation Error. Source is CDINTF~1." Error opening PDF document"

        Comment


          #5
          Re: A couple reports throwing SQLReporting 9 error

          Just a quick side note: I ran into this issue when my application server and development systems were out of sync. I made sure to have the same version for both and then saved/re-pulbished the reports. That resolved the issue.

          Comment


            #6
            Re: A couple reports throwing SQLReporting 9 error

            For what it is worth, I encountered the same problem tonight. It seemed to appear out of nowhere. I went back to build 1794-4227 and the problem is fixed. I was on 1839-4235 when it happened. I upgraded to 1856-4237, and when that did not fix the problem, I went back.
            Jay
            Last edited by Jay Talbott; 02-07-2014, 10:55 AM.
            Jay Talbott
            Lexington, KY

            Comment


              #7
              Re: A couple reports throwing SQLReporting 9 error

              Turning off the report server seems to fix it on the newer releases. My testing showed everything worked fine upto -4234.
              Per Alpha, expecting a fix for this soon.

              Comment


                #8
                Re: A couple reports throwing SQLReporting 9 error

                Jim, Let us know when the fix is successful and you have tried it. I'm going to wait to install any of the latest releases until then. Thanks!
                Carol King
                Developer of Custom Homebuilders' Solutions (CHS)
                http://www.CHSBuilderSoftware.com

                Comment


                  #9
                  Re: A couple reports throwing SQLReporting 9 error

                  A new pre-release has been posted (1958-4255) that has a fix for the connection issue. It only occurred under specific conditions that were not present in most applications. Preliminary testing has shown the fix works as expected and the report server is now working correctly.

                  Comment


                    #10
                    Re: A couple reports throwing SQLReporting 9 error

                    Jerry, where are these pre-releases located? I found v4269 below, but no links to any other versions. I'll try the 4269 for now since it's the weekend. I have plenty of time to fix things that explode.

                    Also, can you shed any light on what the specific condition was that caused the printing problem? Or perhaps it's a moot point.

                    http://downloads.alphasoftware.com/A...easenotes.html

                    Comment


                      #11
                      Re: A couple reports throwing SQLReporting 9 error

                      Actually, when I try to download the pre-release versions, it says page not found. Really need that link if anyone can help!

                      http://downloads.alphasoftware.com/a...full_patch.exe

                      returns this:

                      The page cannot be found

                      The page you are looking for might have been removed, had its name changed, or is temporarily unavailable...

                      Comment


                        #12
                        Re: A couple reports throwing SQLReporting 9 error

                        http://downloads.alphasoftware.com/A...easenotes.html
                        Carol King
                        Developer of Custom Homebuilders' Solutions (CHS)
                        http://www.CHSBuilderSoftware.com

                        Comment


                          #13
                          Re: A couple reports throwing SQLReporting 9 error

                          Derek, I just realized that I put the same link as you had above. For some reason, Alpha does not always update that page to show the latest build numbers, but if you download you get the latest one. Makes it a bit confusing, right?
                          Carol King
                          Developer of Custom Homebuilders' Solutions (CHS)
                          http://www.CHSBuilderSoftware.com

                          Comment


                            #14
                            Re: A couple reports throwing SQLReporting 9 error

                            Thanks Carol! It seemed to be a Chrome profile issue for me. When I finally tried the link in IE or Firefox, or even Chrome without my profile, it works.

                            Also as a followup, the latest pre-release 4270 fixed my pdf printing issue (report server couldn't connect to database). Thank goodness!

                            Comment


                              #15
                              Re: A couple reports throwing SQLReporting 9 error

                              Downloaded 2030-4270 and from what i've tested it has fixed all the reporting issues I was incurring. This included not being able to run report a second time(html only) and Server crashing on a blank return of a free form type report.
                              All my stuff runs within the tabbedui
                              I'm very happy at this point.

                              Comment

                              Working...
                              X