Invalid SQL Information: Access to the Authorization Manager store was denied.

  • Invalid SQL Information: Access to the Authorization Manager store was denied.

    Posted by DSC Communities on January 26, 2017 at 5:11 pm
    • Jason Headrick

      Member

      January 26, 2017 at 5:11 PM

      I am in the process of upgrading to GP 2016R2 on new servers.  Web Services is giving me a hard time.  I haven’t been able to find any good documentation but here is what I’m trying:

      1.) Install Web Services.  My domain account is a local admin to the server and also a sysadmin in SQL.  
      2.) I’m selecting to store the security data on SQL Server (Recommended).  
      3.) Database name i’m specifying is ‘DynamicsGPSecurity’. 
      4.) I get the error:  Invalid SQL Information: Access to the Authorization Manager store was denied.

      Any ideas?  I’ve tried copying my GP2015 ‘DynamicsGPSecurity’ db but this didn’t help…..not sure if this is to be upgraded or just recreated.  I don’t think there is any data I need in that db so a recreated/refreshed db would work.  Thanks in advance.

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————

    • Rob Klaproth

      Member

      January 26, 2017 at 5:18 PM

      Did you select “windows” authentication or SQL auth?  Usually it’s best to select SQL auth and enter the sa user name and password.  I do not recommend copying the old database unless you have a ton of security already setup, it can create a new one during install for the security.

      ——Original Message——

      I am in the process of upgrading to GP 2016R2 on new servers.  Web Services is giving me a hard time.  I haven’t been able to find any good documentation but here is what I’m trying:

      1.) Install Web Services.  My domain account is a local admin to the server and also a sysadmin in SQL.  
      2.) I’m selecting to store the security data on SQL Server (Recommended).  
      3.) Database name i’m specifying is ‘DynamicsGPSecurity’. 
      4.) I get the error:  Invalid SQL Information: Access to the Authorization Manager store was denied.

      Any ideas?  I’ve tried copying my GP2015 ‘DynamicsGPSecurity’ db but this didn’t help…..not sure if this is to be upgraded or just recreated.  I don’t think there is any data I need in that db so a recreated/refreshed db would work.  Thanks in advance.

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————

    • Jason Headrick

      Member

      January 26, 2017 at 5:22 PM

      I’ve tried it both ways…..same error.  With SQL auth I am using ‘sa’ and confirmed the password i’m using is correct.

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————
      ——————————————-

    • Rob Klaproth

      Member

      January 26, 2017 at 5:47 PM

      Try giving the windows user you are logged into the server installing web services the sysadmin fixed server role in SQL and install.  You can revoke the permissions after install.

      ——Original Message——

      I’ve tried it both ways…..same error.  With SQL auth I am using ‘sa’ and confirmed the password i’m using is correct.

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————

    • Jason Headrick

      Member

      January 26, 2017 at 5:51 PM

      already been done.  this is crazy.  no luck.

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————
      ——————————————-

    • Rob Klaproth

      Member

      January 26, 2017 at 5:53 PM

      When are you getting the error, when you run the web services utility to deploy it to a company, or you’re not even getting past the install wizard?

      ——Original Message——

      already been done.  this is crazy.  no luck.

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————

    • Jason Headrick

      Member

      January 26, 2017 at 5:57 PM

      can’t get past the install process

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————
      ——————————————-

    • Ken Allgood

      Member

      January 27, 2017 at 8:09 AM

      You’re absolutely sure that you have the instance name correct?  Might this be a cloned server? 
      Log into sql mgmt studio and run the following query:

      select @@servername

      show us the results here

      ——————————
      Ken Allgood
      Saratoga Technologies, Inc.
      Johnson City TN
      ——————————
      ——————————————-

    • Ken Allgood

      Member

      January 27, 2017 at 8:11 AM

      Oh, and are you a local admin and are you running the install “As Administrator” ?

      ——————————
      Ken Allgood
      Saratoga Technologies, Inc.
      Johnson City TN
      ——————————
      ——————————————-

    • Jason Headrick

      Member

      January 27, 2017 at 9:44 AM


      I am a local admin on the box and doing ‘run as administrator’.

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————
      ——————————————-

    • Beat Bucher

      Member

      January 27, 2017 at 9:58 AM

      Jason,
      For what it’s worth.. have you tried to append MSSQLSERVER in the back of your SQL server name ? when installing your GP SQL server without specifying an instance name, SQL will use a default name, but some installation software actually need to have that instance name specified.. (check for the proper instance name in the windows services).

      ——————————
      Beat Bucher
      Business Analyst, Dynamics GP MVP
      Ultra-Electronics Forensic Technology Inc.
      Montreal QC/Canada
      +1-514-489-4267
      @GP_Beat http://dyngpbeat.wordpress.com/
      Montreal QC GPUG Chapter Leader
      GP2013R2 / MR2012 CU14
      ——————————
      ——————————————-

    • Jason Headrick

      Member

      January 27, 2017 at 10:23 AM

      I personally don’t think this is a sql issue.  I think it has something to do with ‘authorization manager store’ but not sure exactly what.

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————
      ——————————————-

    • Jeff Pfershy

      Member

      January 27, 2017 at 10:26 AM

      You may want to make sure you can actually contact the server using the TELNET command.
      Open a CMD window from the machine where you’re installing the web services and type TELNET VDC-DEVSQL6GP01 [port number].
      You will need to replace [port number] with the port SQL listens on – if SQL was configured for the default port then use 1433.
      IF the telnet connection is successful, you should be presented with a blank screen.

      Also – check the windows firewall setting on the SQL server. Make sure it is configured correctly. I can provide more assistance on that if needed.

      PS – Tell Rajeev I said hi!

      ——————————
      Jeff Pfershy
      Solution Consultant
      248-489-0707
      The TM Group, Inc.
      Farmington Hills MI
      ——————————
      ——————————————-

    • Jason Headrick

      Member

      January 27, 2017 at 10:38 AM

      Hey Jeff….I’ll tell him hi for you when he gets back from his Vacation in Hawaii. I’d rather be there today!  No telnet issues.  I have GP and MR running on this box without any issue.  The only port it needs on the sql box is 1433

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————
      ——————————————-

    • Rob Klaproth

      Member

      January 27, 2017 at 12:54 PM

      Jason,
      What version of GP are you installing this on?  Are you installing from the RTM DVD download from Microsoft (the link inside the DVD installer)?  You may want to check if there is a service pack for web services.
        

      ——Original Message——

      can’t get past the install process

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————

    • Ken Allgood

      Member

      January 27, 2017 at 10:23 AM

      From what I’m seeing, it looks like you have Authorization Manager for Window Server set up.  I have to admit, I’m not familiar with this.  Do this to see if you have an Authorization Store configured or not

      To start Authorization Manager

      1. Click Start , type azman.msc in the Start Search box, and then press ENTER.

      Click on Authorization Store on the left.   Mine says No Authorization Stores on the right/main window on any of our servers…

      If it gives you a login challenge, and you cannot get past it, then I think you found your problem.

      Here’s some more info on Authorization Manager –
      https://technet.microsoft.com/en-us/library/cc726036(v=ws.11).aspx

      I might be barking up the wrong tree here, but based on your error, seems like a possible route to look into….

      ——————————
      Ken Allgood
      Saratoga Technologies, Inc.
      Johnson City TN
      ——————————
      ——————————————-

    • Jason Headrick

      Member

      January 27, 2017 at 10:26 AM

      I get the same thing.  I compared this to our GP2015 environment (current Prod that works – and i did the install) and it is the same, i can’t find any difference.

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————
      ——————————————-

    • Jason Headrick

      Member

      January 27, 2017 at 11:16 AM

      If I point WebServices to a SQL2014 machine I can get past the step.  Is WebServices supported on SQL2016?  This is really the only viable culprit IMO.

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————
      ——————————————-

    • Rob Klaproth

      Member

      January 27, 2017 at 1:03 PM

      Technically GP 2015 was never “certified” for SQL 2016, another wards the official “system requirements” document does not show SQL 2016.  On the other hand in my testing it does work with the latest service pack, however I have not tested web services, so that may be possible that SQL 2016 is not supported for the GP 2015 web services.

      ——Original Message——

      If I point WebServices to a SQL2014 machine I can get past the step.  Is WebServices supported on SQL2016?  This is really the only viable culprit IMO.

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————

    • Jason Headrick

      Member

      January 27, 2017 at 1:08 PM

      Installing from MDGP2016_R2_DVD_ENUS.  GP2016 R2 on SQL 2016

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————
      ——————————————-

    • Rob Klaproth

      Member

      January 27, 2017 at 1:24 PM

      That should be supported.  I don’t know where I was getting 2015 from.    I have installed web services from that DVD on SQL 2016 w/ GP 2016R2.
      So, at this point I would recommend you submit a ticket to Microsoft for review.   They are very good about determining if it’s a bug in the product, or an issue with your environment, if it is a bug they will not charge you for a support case.

      ——Original Message——

      Installing from MDGP2016_R2_DVD_ENUS.  GP2016 R2 on SQL 2016

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————

    • Rob Klaproth

      Member

      January 27, 2017 at 1:34 PM

      Jason,
      What is your sort order in SQL?

      ——Original Message——

      Installing from MDGP2016_R2_DVD_ENUS.  GP2016 R2 on SQL 2016

      ——————————
      Jason Headrick
      Progressive Leasing
      Draper UT
      ——————————

    • Rob Klaproth

      Member

      January 27, 2017 at 1:44 PM

      One thing you could also try is to cancel install, and blow out the web services tables from your existing DYNAMICS and company databases and then try installing again.  Unfortunately, this script I have is the last one microsoft posted and may not be correct for your current GP version:
      Against DYNAMICS DB :

      drop view ReqCurrency
      drop view ReqCurrencyAccess
      drop table WSErrorProperties
      drop table WSExceptionLog
      drop table WSInstallStatus
      drop table WSInstallSteps
      drop procedure ws_delete_WSExceptionLog
      drop procedure ws_deleteall_WSExceptionLog
      drop procedure ws_get_MC40200
      drop procedure ws_get_SY01500
      drop procedure ws_get_WSErrorProperties
      drop procedure ws_get_WSExceptionLog
      drop procedure ws_get_WSExceptionLog_Summary
      drop procedure ws_get_WSExceptionLog_ValidationException
      drop procedure ws_get_WSInstallStatus
      drop procedure ws_getall_WSInstallStatus
      drop procedure ws_insert_WSExceptionLog
      delete eConnect_Out_Setup where DOCTYPE in(‘WSCompany’, ‘WSCurrency’, ‘WSCurrencyAccess’)

      Run following sql script against all Company Database

      drop view ReqCurrencyPostingAccountView
      drop view ReqGLAcct
      drop view ReqGLFixedAllocAcct
      drop view ReqGLFixedAllocDistAcct
      drop view ReqGLHeaderView
      drop view ReqGLLineView
      drop view ReqGLPostingAcct
      drop view ReqGLPostingAcctCurrencies
      drop view ReqGLUnitAcct
      drop view ReqGLVarAllocAcct
      drop view ReqGLVarAllocDistAcct
      drop view ReqGLVarAllocDistBreakAcct
      drop view ReqIVFee
      drop view ReqIVHeaderView
      drop view ReqIVItemCurrency
      drop view ReqIVItemHeader
      drop view ReqIVItemQuantity
      drop view ReqIVItemQuantityBinDetail
      drop view ReqIVItemVendor
      drop view ReqIVItemWarehouse
      drop view ReqIVKit
      drop view ReqIVKitComponent
      drop view ReqIVLineBinDetailView
      drop view ReqIVLineLotDetailView
      drop view ReqIVLineSerialDetailView
      drop view ReqIVLineView
      drop view ReqIVPricing
      drop view ReqIVPricingDetail
      drop view ReqIVSalesItem
      drop view ReqIVService
      drop view ReqPAAccounts
      drop view ReqPAChangeOrderHeader
      drop view ReqPAContractHeader
      drop view ReqPAEmpExpDist
      drop view ReqPAEmpExpHeader
      drop view ReqPAEmpExpLine
      drop view ReqPAEmpExpLineTax
      drop view ReqPAMiscLog
      drop view ReqPAMiscLogDist
      drop view ReqPAMiscLogLines
      drop view ReqPAProjectBudgetHeader
      drop view ReqPAProjectHeader
      drop view ReqPATimesheetDist
      drop view ReqPATimesheetHeader
      drop view ReqPATimesheetLine
      drop view ReqPaymentCard
      drop view ReqPMHeaderDistView
      drop view ReqPMHeaderTaxView
      drop view ReqPMHeaderView
      drop view ReqPMVendor
      drop view ReqPMVendorInetAddress
      drop view ReqPMVendorPAOptions
      drop view ReqPOHeaderFreightTaxView
      drop view ReqPOHeaderMiscTaxView
      drop view ReqPOHeaderTaxView
      drop view ReqPOHeaderView
      drop view ReqPOLineTaxView
      drop view ReqPOLineView
      drop view ReqPurInvDistView
      drop view ReqPurInvHeaderFreightTaxView
      drop view ReqPurInvHeaderMiscTaxView
      drop view ReqPurInvHeaderTaxView
      drop view ReqPurInvHeaderView
      drop view ReqPurInvLineApplyRecptView
      drop view ReqPurInvLineTaxView
      drop view ReqPurInvLineView
      drop view ReqPurRecptDist
      drop view ReqPurRecptHeader
      drop view ReqPurRecptLine
      drop view ReqPurRecptLineBin
      drop view ReqPurRecptLineLotNum
      drop view ReqPurRecptLineSerNum
      drop view ReqRecvDocComm
      drop view ReqRecvDocDist
      drop view ReqRecvDocHeader
      drop view ReqRecvDocTax
      drop view ReqRMCashReceiptDist
      drop view ReqRMCashReceiptHeader
      drop view ReqRMCorporateAccount
      drop view ReqRMCustomer
      drop view ReqRMCustomerAddress
      drop view ReqRMCustomerInetAddress
      drop view ReqRMSalesPersonCommisionsView
      drop view ReqRMSalespersonInetAddress
      drop view ReqSODistributionView
      drop view ReqSOHeaderFreightTaxView
      drop view ReqSOHeaderMiscTaxView
      drop view ReqSOHeaderTaxView
      drop view ReqSOHeaderView
      drop view ReqSOLineComponentView
      drop view ReqSOLineTaxView
      drop view ReqSOLineView
      drop view ReqSOLotDetailView
      drop view ReqSOSerialDetailView
      drop table WSPolicyBehaviorSelectionParameter
      drop table WSPolicyBehaviorSelection
      drop table WSPolicyBehavior
      drop table WSPolicy
      drop table WSParameter
      drop table WSBehaviorOption
      drop table WSBehavior
      drop procedure ws_delete_WSBehavior
      drop procedure ws_delete_WSBehaviorOption
      drop procedure ws_delete_WSParameter
      drop procedure ws_delete_WSPolicy
      drop procedure ws_delete_WSPolicyBehavior
      drop procedure ws_delete_WSPolicyBehaviorSelection
      drop procedure ws_delete_WSPolicyBehaviorSelectionParameter
      drop procedure ws_get_Behavior
      drop procedure ws_get_MC40000
      drop procedure ws_get_Policy
      drop procedure ws_get_PolicyByOperation
      drop procedure ws_get_PolicyNoDefaulting
      drop procedure ws_get_SY00300
      drop procedure ws_insert_WSBehavior
      drop procedure ws_insert_WSBehaviorOption
      drop procedure ws_insert_WSParameter
      drop procedure ws_insert_WSPolicy
      drop procedure ws_insert_WSPolicyBehavior
      drop procedure ws_insert_WSPolicyBehaviorSelection
      drop procedure ws_insert_WSPolicyBehaviorSelectionParameter
      drop procedure ws_update_WSPolicyBehaviorSelection
      drop procedure ws_update_WSPolicyBehaviorSelectionParameter
      delete eConnect_Out_Setup where DOCTYPE = ‘WSBank’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSCashReceipt’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSCompanyAddress’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSCorporateAccount’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSCountryRegionCode’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSCurrencyPostingAccount’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSCustomer’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSCustomerAddress’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSFee’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSGLAccount’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSGLAccountCategory’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSGLAccountFormat’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSGLFixedAllocationAccount’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSGLPostingAccount’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSGLTransaction’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSGLUnitAccount’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSGLVariableAllocationAccount’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSInventoriedItem’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSInventoryAdjustment’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSInventoryTransfer’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSInventoryVariance’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSItem’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSItemClass’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSItemCurrency’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSItemVendor’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSItemWarehouse’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSKit’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSMulticurrencySetup’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSPayablesCreditMemo’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSPayablesDocument’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSPayablesFinanceCharge’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSPayablesInvoice’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSPayablesMiscellaneousCharge’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSPayablesReturn’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSPaymentCardType’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSPaymentTerms’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSPriceLevel’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSPricing’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSProject’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSProjectBudget’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSProjectChangeOrder’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSProjectContract’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSProjectEmployeeExpense’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSProjectMiscellaneousLog’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSProjectTimesheet’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSPurchaseInvoice’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSPurchaseOrder’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSPurchaseReceipt’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesCreditMemo’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesDebitMemo’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesDocument’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesFinanceCharge’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesInvoice’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesReturn’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesServiceRepair’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSReceivablesWarranty’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesBackorder’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesDocument’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesDocumentTypeSetup’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesFulfillmentOrder’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesInvoice’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesItem’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesOrder’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesperson’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalespersonCommissions’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesProcessHoldSetup’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesQuote’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesReturn’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesSetup’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSSalesTerritory’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSService’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSShippingMethod’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSUofMSchedule’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSVendor’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSVendorAddress’
      delete eConnect_Out_Setup where DOCTYPE = ‘WSWarehouse’

      ——Original Message——

      Jason,
      What is your sort order in SQL?

    • Terry Angel

      Member

      February 14, 2018 at 4:37 PM

      Hello,
      I see this discussion was from just a few weeks ago.Ā  I’m getting the same errors as you…Ā 

      “Access to the Authorization Manager store was denied”

      When I try to connect using the suggested “servernameMSSQLSERVER”, I get the same error as well:

      “A network related or instance-specific error occurred….. etc etc…
      …. etc etc…Ā  Verify that the instance name is correct … etc etc…
      …. and that SQL Server is configured to allow remote connections… etc etc “

      I’ve had my network guy watch the firewall logs as I was attempting to install, there were no firewall blocks… bunch of traffic flowing through 1433.Ā 

      did you ever get through this? Thanks!

      ——————————
      Terry Angel
      Indianapolis Motor Speedway
      ——————————
      ——————————————-

    • Terry Angel

      Member

      February 15, 2018 at 11:16 AM

      FYI – for anyone reading this in the future, I opened a Premier ticket with Microsoft, this solution worked for me:

      —————————————-

      Hi Terry,

      Ā 

      I’m pretty sure I know what the issue is here. Can you confirm for me whether or not TLS 1.0 has been disabled on these machines? I’ve recently been doing internal testing regarding GP compatibility with TLS 1.0 disabled, and I get this exact error message when installing Web Services where TLS 1.0 is disabled. Currently I don’t have any workarounds except to activate TLS 1.0 to get Web Services installed.

      Ā 

      I’m not sure if you can enable TLS 1.0, install WS, then disable it again, I haven’t gotten to that phase of my testing, but I’m pretty confident that this is what you’re running into.

      Ā 

      You can use a tool like IISCrypto to see what’s disabled or enabled on the servers.

      https://www.nartac.com/Products/IISCrypto/

      Ā 

      Thanks,

      ——————————
      Terry Angel
      Indianapolis Motor Speedway
      Indianapolis IN
      ——————————
      ——————————————-

    • Dan Peltier

      Member

      February 15, 2018 at 12:33 PM

      Hello all, sorry to bump an older thread, but I have information that may be relevant to a resolution. With the PCI Compliancy changes due this summer regarding TLS 1.0 deprecation, we’ve been doing internal testing on GP when TLS 1.0 is disabled.Ā 

      If you try to install Web Services with TLS 1.0 disabled, you’ll receive the following error:

      “Access to the Authorization Manager store was denied.”

      Currently, the only workaround I’ve been able to find is to enable TLS 1.0 again, and perform the install . TLS 1.0 appears to be required for the Security Console as well, so for now I’d say TLS 1.0 is a requirement for Web Services until we find out where that error is coming from.Ā 

      Otherwise as long as you’re connecting to a SQL instance that supports TLS 1.0 being disabled, there aren’t any other issues we’ve identified so far with running GP on a machine where TLS 1.0 has been disabled. See the following links for more information, including configuration and update information for TLS 1.0 disable compatibility against SQL. The updated SQL components are required for GP connectivity against the versions stated in the first link. The instructions are for SharePoint, but that’s the guide I followed to get my environments connected.
      https://technet.microsoft.com/en-us/library/mt773993(v=office.16).aspx
      https://www.microsoft.com/en-us/download/details.aspx?id=36434
      https://www.microsoft.com/en-us/download/details.aspx?id=50402

      I’ll be publishing a blog soon that covers this in more detail.

      ——————————
      Dan Peltier
      Sr. Support Engineer
      Microsoft
      Fargo ND
      ——————————
      ——————————————-

    • Tanya Henderson

      Member

      September 10, 2018 at 5:05 PM

      I am responding to an older thread as well.Ā  I uninstalled and reinstalled and that fixed my issue thanks for the thoughts.
      Tanya

      ——————————
      Tanya Henderson
      Senior Consultant
      S2 Technology
      Park City UT
      ——————————
      ——————————————-

    DSC Communities replied 8 years, 8 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘Invalid SQL Information: Access to the Authorization Manager store was denied.’ is closed to new replies.

Start of Discussion
0 of 0 replies June 2018
Now

Welcome to our new site!

Here you will find a wealth of information created for peopleĀ  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!