Anonymous

My feedback

  1. 5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 8 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 86

    <=-=Dec 27 2010 12:13PM=-=>

    Hello Russell

    Thank you for proposing a new DCR for SQL Agent. We are always looking forward for the customer feedback. We will consider your proposal in one of our future releases.

    Thank you
    Alex Grach

    <=-=Jan 25 2011 5:04PM=-=>

    This functionality seems essential. Why won’t there be a SQL Agent Proxy? In many scenarios there is a Service Account under which all things run and that service account is normally a domain account – which may or may not have permissions to run SQLCMD or Powershell etc.

    <=-=Jan 25 2011 5:08PM=-=>

    Besides, if we run SQLCMD and the Sproc or Query errors out, the job agent steps still are marked successful. There is not robust error handling mechanism using SQLCMD from the Job Agent

    <=-=Mar 23 2011 1:23PM=-=>

    Although it is possible to “simulate a proxy” by granting impersonation rights to a proxy…

    Anonymous supported this idea  · 
  3. 45 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    34 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    I’m looking into this issue.

    In the meanwhile, could you take a look at the SSMS setup logs (%TEMP%\SSMSSetup\SSMS-Setup-ENU_20190430231104.log). I’m interested in the lines in the range 133-216. Could you share those (tip: have a look at the lines and sanitize them, if you think they may contain sensible information?

    Also, if you could share the output of:
    reg query “HKLM\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio” /reg:32 /s

    And, finally, to unblock yourself:
    1) Make sure you don’t have any previous version (RC, Preview) of SSMS 18.0 installed (check Add/Remove programs; if you do, uninstall it)
    2) Make sure “C:\Program Files (x86)\Microsoft SQL Server Management Studio 18” does not exist (if it does, the delete it)
    3) Delete the mentioned registry key (e.g. by running from an elevated cmd prompt:
    reg DELETE “HKLM\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio” /reg:32)
    4) Retry setup
    Please, let…

    An error occurred while saving the comment
    Anonymous commented  · 

    tried 18.2 after reg and folders cleanup and reboot, still the same "side-by-side configuration is incorrect" error when launching.
    Running sxstrace shows Cannot resolve reference Automation,processorArchitecture="X86",type="win32",version="1.0.0.0" error with references to C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Automation.DLL file, etc.

    as someone below, i could not find such directory or file in my PC.
    Maybe, i can download it aside from somewhere?
    Or, what should i do to make it work finally?

    An error occurred while saving the comment
    Anonymous commented  · 

    i did all the suggested manipulations, got SSMS re-installed, but still when launching it, i get
    "The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail."

    Tried with the latest version.

    An error occurred while saving the comment
    Anonymous commented  · 

    the registry key deletion helped to install SSMS 18, but now, when launching it i have following error:

    The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.

    where do i see the log?

    Anonymous supported this idea  · 
  4. 763 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    57 comments  ·  Azure Analysis Services  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 

Feedback and Knowledge Base