I have installed and configured the Lync Server 2010. When I run the example to Lync Server SDK (SipSnoop) and press the button Connect, I get an error:
- EXCEPTION (2:23:20 PM) -
Application not authorized.
Queue could not be created.
Access denied.
All services of Lync Server running normally, messages and phone calls are sent without any problems. SipSnoop run on Front-end server.
Script-only exampels from this SDK runs correctly.
What i need to do to run SipSnoop correctly?
Check the readme
If you see the "Queue could not be opened Access Denied" error message, check whether
the logged on user is part of the "RTC Server Applications" local group. If not, add it, logout and login and retry
Where is the "RTC Server Applications" local group?
On the server which you run your application on. click:
Control pannel-->change account type --> Advanced --> Advanced -->group -->Groups
check the uri
The appUri in SIPSnoop.am should be same as the the uri you supplied by this command "new-csserverapplication"
You should started with elevated privileges ("run as administrator")
To run The Visual Studio with administrator privileges:
Run the *.exe of the application from the bin folder by "run as administrator"
Start to attach the *.exe to the debugger from "Debug ==> Attach to process"
the visual studio will ask you to start with the administrator previlege
Related
I run SQL Server 2014 locally. My old windows account has been corrupted. I created a new windows account, gave myself sysadmin permissions on SSMS and I can log onto the database fine. I also logged on Reporting Services Configuration Manager and changed the Service Account to the new user account. However I can not access localhost/reportserver on internet explorer. It's saying I don't have sufficient permissions.
Ah I just found the answer. It's a Trusted Site issue:
To Configure Local Report Server and Report Manager Administration
Complete the configuration steps in this section if you are browsing to a local report server and you see errors similar to the following:
User 'Domain[user name]' does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed.
Trusted Site Settings in the Browser:
Open a browser window with Run as administrator permissions. From the Start menu, click All Programs, right-click Internet Explorer, and select Run as administrator.
Click Allow to continue.
In the URL address, enter the Report Manager URL. For instructions, see Report Manager (SSRS Native Mode) in SQL Server Books Online.
Click Tools.
Click Internet Options.
Click Security.
Click Trusted Sites.
Click Sites.
Add https://[your-server-name]
Clear the check box Require server certification (https:) for all sites in this zone if you are not using HTTPS for the default site.
Click Add.
Click OK.
https://learn.microsoft.com/en-us/sql/reporting-services/report-server/configure-a-native-mode-report-server-for-local-administration-ssrs?view=sql-server-2017
I have a simple EF Code First project that has to create a database in my local SQL server if it doesn't exist. However, when I try to debug my application I get the error:
Cannot open database "<Database>" requested by the login. The login failed.
Login failed for user 'MicrosoftAccount\someone#me.com'.'
I somewhat understand that because I login to Windows with my Microsoft account.
So I changed my connection string from using integrated security to username and password.
I made sure the user is created on the SQL server (Login & sysadmin rights) but it still fails when I debug in Visual Studio.
So..... I build the project and ran the application directly via the exe file and everything works. But I want to understand why it doesn't work with the debugger.
Have I missed something obvious here?
So I found the problem.
My local Windows account was paired with my Microsoft account. For some reason Visual Studio sends my Microsoft account to the SQL server to authenticate even when run under specific local credentials.
My solution was to create anew local user on my workstation with NO assosiated MS account.
I made the account member of Administrators and gave it permission to the SQL server then everything was fine...
Please ensure the server and database name are specified correctly in connection string. I had a typo, and got the error.
I guess that the debugger runs with different credentials (or could be set to do so). Especially if your account is not admin.
Maybe this helps: https://blogs.msdn.microsoft.com/greggm/2008/05/15/visual-studio-remote-debugger-service-user-account-requirements/
Having all sorts of problems after publishing website from VS2015.
My Site has been working fine when run from within VS2015. However, I followed some instructions to Publish the website to my IIS and now the site Login page comes up but after entering user/password the application fails to make connection to the database and shows the error:
Failed to generate a user instance of SQL Server due to a failure in impersonating the client. The connection will be closed.
I am running Windows 8.1, SQL Server 2008/R2, Visual Studio 2015 and the Database connect string is:
I do NOT currently have Database User I am simply connecting using Windows Integrated authentication.
I think it's some kind of permissions error, can someone please assist ?
The website is using the AppPool identity to connect to the SQL database. By default the AppPool uses a Built-in Account.
You can change the AppPool to use a custom domain account which as rights to the database.
I don't think this question has been answered, apologies if I've missed a thread.
In short, I've performed a vanilla install of a SQL 2012 and SSIS on my local machine.
I've configured SSIS to run with the NT AUTHORITY\Local Service account (also tried my local login), and am running SSMS under my local login (I'm a local admin).
SQL instance is running as NT Service\MSSQLSERVER.
I can access Integration Services in the object explorer and run packages using the GUI. However, when calling from code, I get the following:
Could not load package "\MSDB\FileLoad\CustomerMaster_Customer"
because of error 0xC00160AE. Description: Connecting to the
Integration Services service on the computer "UKLT-RHE-1" failed with
the following error: "Access is denied."
By default, only administrators have access to the Integration
Services service. On Windows Vista and later, the process must be
running with administrative privileges in order to connect to the
Integration Services service. See the help topic for information on
how to configure access to the service.
Any help is muchly appreciated!!
Thanks in advance,
Rich
Fixed it..!
http://msdn.microsoft.com/en-us/library/hh213130.aspx
N.B. Step 6 - Repeat steps 4 - 5 for Access Permissions.
HTH someone!
Just in case the page indicated by #richhemmings is not available.
To grant access to the Integration Services service
1.Run Dcomcnfg.exe. Dcomcnfg.exe provides a user interface for modifying certain settings in the registry.
2.In the Component Services dialog, expand the Component Services > Computers > My Computer > DCOM Config node.
3.Right-click Microsoft SQL Server Integration Services 11.0, and then click Properties.
4.On the Security tab, click Edit in the Launch and Activation Permissions area.
5.Add users and assign appropriate permissions, and then click Ok.
6.Repeat steps 4 - 5 for Access Permissions.
7.Restart SQL Server Management Studio.
8.Restart the Integration Services Service.
The error message says "By default, only administrators have access to the Integration Services service."
Therefore you run SQL Server Management Studio as administrator.
https://youtu.be/WyKHStfz0uk
I had recently installed SQL server 2012 and I used mostly the default settings. Database works fine and I can happily connect using SSMS (SQL Server Management Studio) but when I connect to the Integration Services Server I get this message
Connecting to the Integration Services service on the computer
"localhost" failed with the following error: "Access is denied."
By default, only administrators have access to the Integration
Services service. On Windows Vista and later, the process must be
running with administrative privileges in order to connect to the
Integration Services service. See the help topic for information on
how to configure access to the service.
here is the screenshot
I am not sure why but I am the domain admin and have full rights over the server. Also why when I connect from my Desktop it can successfully connect, only if I connect from the server itself which gives me this issues. How do I fix this so that I can make SSMS on the server connect to its Integration Services instance.
As I understand it, User Access Control, or UAC, can basically intercept requests for your group membership so in this case, it appears it was preventing your membership getting passed to SQL Server.
Others have noted in their comments that you may still need to right click and run SSMS as an Administrator.
As noted by an astute observer "This is a quick-fix, not a real solution. People shouldn't just be running stuff as administrator. These security walls are in place for a reason" And I agree. UAC is designed to get Windows users into a Principle of least privilege mindset - only escalate to a powerful account when required. The issue is that SSMS is known to not "play well" with UAC. As I see it, this leaves you with three options
You can turn off UAC and get your work done
Leave UAC on and tell your boss you are unable to work
Write your own query tool that is not affected by UAC
Go to all programs Click on Microsoft SQL Server 2012 folder Right click on SQL Server Management Studio Click on Run as Administrator
This should take care of problem for now. (With this you need to always repeat the same process). To avoid this every time and for a more persistent solution you need to get permission(s). Please do the following process and you should be good.
In previous versions of SQL Server, by default when you installed SQL Server all users in the Users group had access to the Integration Services service. When you install the current release of SQL Server, users do not have access to the Integration Services service. The service is secure by default. After SQL Server is installed, the administrator must grant access to the service.
To grant access to the Integration Services service
Run Dcomcnfg.exe. Dcomcnfg.exe provides a user interface for modifying certain settings in the registry.
In the Component Services dialog, expand the Component Services > Computers > My Computer > DCOM Config node.
Right-click Microsoft SQL Server Integration Services 11.0, and then click Properties.
On the Security tab, click Edit in the Launch and Activation Permissions area.
Add users and assign appropriate permissions, and then click Ok.
Repeat steps 4 - 5 for Access Permissions.
Restart SQL Server Management Studio.
Restart the Integration Services Service.
(Source MSDN)
I hope this will help
Right Click on the Sql Server Management Studio and select Run as Administrator and try to connect
if it is installed on the local instance
You should check to see what user the SSIS Service is running under. Go to Start > Run > Type "services.msc" and scroll down to the SQL Server Integration Services 11.0 entry. Right click and check the properties to find out what user it's running under. The second tab should be the LogOn tab. Since you're just running on a local instance, you can set your user as the LogOn User account and SSIS will have the same permissions that you do.
Lost a day of work on that problem. My package has a .NET script task to copy file from a shared network folder to a local folder and I was stuck with the "access denied" exception every time I tried to execute the package from the server (Through SQL Studio). The package works fine when running locally.
Tried many things picked up here and there and at the end of the day what worked is to create a Job (owner is sa) which execute the package as SSISExecutor.
I have to mention that the file on the network has read access for everyone, and that I still don't understand what was wrong.