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

SQL Query error since update

  • Filter
  • Time
  • Show
Clear All
new posts

  • SQL Query error since update

    Good morning all -

    We use MSSQL filestream FileTables as part of a document management application. This has been up and running for several years. A hiearchyID type field 'Path_Locator' is the primary key field. Since updating to version 5487 the query returns an error that the data type cannot be converted. I've tried re-working it to expressly convert it to text but still no go. I don't know if this is a bug with the new version or if this is a change in the method to be used to send queries - in which case I'll have to convert all of my functions to use an intermediate table to pass processing back to SQL server. Anyone have any suggestions? Thanks


  • #2
    Re: SQL Query error since update

    Are you running the web server on same computer as before? Is the database server same server as before?

    I think I recall some Alpha installs try to install sql client drivers. I would suspect something has changed with the sql data drivers.

    Usually the solution to data type compatibility issues is to download the "Native Client Drivers for SQL" from Microsoft and install them - probably on the web server and the database server.
    MS has been making it difficult to find those drivers. They have not been updating them, but last time I looked the support pages said to use them anyway on the newer versions of sql server.


    • #3
      Re: SQL Query error since update


      Thanks for responding. At first I thought the same thing. We did just replace one of our servers. When I switched over the application server, I did a full install of the latest version of Alpha and at the same time updated all of our workstations so that they were running the same version. The old server was using an older version as we don't update that unless there is a compelling reason to do so. So, when this problem developed, I assumed that it was the new server configuration, drivers, etc.

      However, It seems to be the current build of Alpha. I tested it on my laptop - publishing to the local web-root - with the 'new' build and the same result(i.e. error). I then uninstalled and reinstalled with the old version and it works fine. I then installed the patch on the old server (which worked fine before) to the current build and the error was reproduced. I've also tried to use native SQL but still the same problem. I can run the select statement using SSMS even remotely and it returns the records as it should. So it seems to be a data conversion problem with Alpha. I guess I will work on a stored procedure over the weekend to replace the query. Have a nice weekend.



      • #4
        Re: SQL Query error since update

        Unless you actually try installing the MS SQL Server Native Client 2012 (regardless of having a new version of SQL) AFTER you have installed (patched, or updated) Alpha then you cannot really be sure it is an Alpha bug.

        Get the driver from here and install on the machine that is trying to talk to sql engine:

        If you have installed "sqlncli.msi" (after having installed or updated Alpha Developer and/or Server) and you get the error then please submit the issue to alpha.


        • #5
          Re: SQL Query error since update


          I will give it a try. Thanks for the link.



          • #6
            Re: SQL Query error since update


            I updated the SQL native drivers as well as the SQL ODBC client drivers (actually I'm using SQL 2014) but still no go. Alpha reports an un-handled exception error and the log shows that "data error.. path_locator could not be converted". It seems that SQL FileTables and Filestream are not widely used so probably (and understandably) not a priory for Alpha. I have since converted my functions to use a stored procedure that does not require the return of the path_locator column and it seems to be working okay.

            However, it turns out that it was worthwhile updating the drivers because it eliminated another error message in the SQL logs on a separate process that I had been ignoring - as it was still 'working'. Thanks again for your suggestion.