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

IIS: There was an error publishing users and/or roles:

  • Filter
  • Time
  • Show
Clear All
new posts

  • IIS: There was an error publishing users and/or roles:

    I've been maintaining some web applications (all used with desktop browsers) for a client using his own standard Application Server. He asked me to host the applications on MY IIS server (he no longer has the staff to maintain his server). I gladly agreed. To test the move, I copied his SQL Server Database to my SQL Server; I created the Site and Application Pool on my IIS Server; I published all of his files to MY server (created an IIS Profile, of course); and I his URL to my IIS server. Everything worked great until I tried to log on to the application: I got a "log in information incorrect" error.

    OK, so I decided to republish the "Security Data/Files" (when I published the application, originally, I selected "Ignore Users and Roles," since the current User/Security files were part of the SQL Server Database I transferred from his server). When I try to "Replace", "Merge" or "Preserve" User data, I get this error: "There was an error publishing users and/or roles". The error directs me to view the publishing log, but all the log says is: "There was an error publishing users and/or roles:"

    When I tried to go to the "Web Security" option in Alpha Anywhere and simply "Publish Security Files," I got this mess:
    Alpha Error.jpg

    I've tried everything in my arsenal, but I'm exhausted and need to get some help. If you have any suggestions about how I can recreate the security system, so I can log on, I'd appreciate any help you can offer.

    With appreciation,

  • #2
    You need to contact Alpha, the security files are no longer in SQL for IIS from what I understand (as a result of Alpha Cloud) but an Internal MYSQL database. I might be wrong but just ask them.
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)


    • #3
      The security info is most definitely in my MS SQL database tables for IIS. But Pete is right, you should contact Alpha. Terry is the Alpha IIS guru.

      When I moved my IIS Server to a new server a while back I had some questions regarding the process of ensuring proper transfer of security. Here are a few comments from Terry ..

      "If the security database is located on a separate server, you do not have to do anything and you would use "Ignore" or "Preserve". Preserve would find the security tables and do nothing. Ignore won't even try to find the security tables.

      If the security database is located on the same machine as the old IIS server (i.e. the connection string for the membership provider and role provider uses "localhost"), then you would need to move the database to the new server so that the same localhost connection string will still work. Alternatively, you could keep the security database on the old server or move it to some server other than the new IIS server and then change the membership/role provider connection string in the publish profile so that the connection string points to the database location (the connection string no longer would use localhost). You would still use "Ignore" or "Preserve" when publishing."
      Last edited by iRadiate; 11-02-2020, 01:42 PM.
      Alpha Anywhere v12. Build 8245-5650 IIS v10.0 on Windows Server 2019 Std in Hyper-V


      • #4
        Thanks Pete and Stephen... I appreciate your help. I've contacted Terry. Hopefully, he'll be able to tell me what I'm doing wrong.


        • #5
          I reported this earlier this week. Maybe now that there is a second report it will get some more traction.


          • #6
            You need to delete the application on the server completely and recreate it. Then use "Replace" the very first time you publish your security settings. This was the fix for us, under very similar circumstances. Good luck.