I have tried to configure release management to work across different servers with untrusted domains using the steps described in the below article.
http://blogs.msdn.com/b/visualstudioalm/archive/2013/12/12/configuring-release-management-to-work-across-untrusted.aspx
But when I tried to configure RM agent with ghost account, it was throwing error mentioned in the title. Please see the error screen attached..!!
I am searching for a solution for last few days...!!! Experts please help me.
Finally the issue has been resolved by logging in as shadow account. Changed RM server name with IP in MS deployment agent....!!
Thank you very much #Daniel Mann for the tips you have provided.
write it down as
Correct way:-
http://(server):(port)
Incorrect way:-
http://(server):(port)/ReleaseManagement
Do not write "/ReleaseManagement/" or any other URL segments after .
This will solve your problem.
Logging in as the shadow account may not be possible depending on how you setup the service account. Release Management site uses windows authentication so if you setup your credentials in Credential Manager on the agent server that will work. Just specify the fully qualified domain name for your Release Management server and your domain credentials for the RM server's domain.
Related
The company requires we use SQL Server 2016 Reporting Services to generate reports. I attempted to restore a database from a backup, but have encountered permission errors when I go to the web portal URL.
I found some advice online about making sure I had the right permissions enabled, however despite making the http web portal url trusted, a domain account with sysadmin permissions, and running the browser as administrator I still encounter the same error - see images for what I'm dealing with.
I'm simply flummoxed as to what my next step should be.
web service
web portal
I've tried adding the permissions within SSMS and adding my domain account to the sysadmin level, but it hasn't changed anything. I think I must be missing some key setting or misunderstanding where I need to enable a permission.
It turned out to be some error in the registry, we did a full clean and reinstall and it worked.
Can someone let me know why I'm unable to access our Azure SQL Database using Tableau Desktop with our Active Directory account?
I have no problem gaining access using Username and Password, but can't access using AD account i.e. usernam#company.com
I'm getting the following errors
Check whether you have installed ODBC Driver or not. If that's the case, try installing it by following this Download link depending on the operating system you are using.
After installing it, configure the ODBC DSN that may help you to resolve the error.
If it's already installed and still you are getting error, try degrading/upgrading the version.
Take a look at this similar problem answered in below reference:
Error connecting to MySQL - Error Code: B19090E0
You need to configure the server to access using AD account https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-configure?view=azuresql&tabs=azure-powershell
We are working with SQL Server using Windows authentication and have found that we need to specify the SPN for the connection to work. Our application is partially using VB6 connecting via UDL files and partially a series of ad hoc scripts that we run through LinqPad.
Using the Server SPN feature of the UDL file we can get the connection to work but can not find the equivalent for LinqPad.
Does anyone know how to get this working? We have tried ServerSPN= as an additional connection string parameter on the Advanced settings but it is unrecognised.
Further details.
The client applications are on Windows 7 in domain A. All of the client connections are made from accounts in domain A.
The sql server is in domain B.
There is a selective one way trust between the domains and the server is added to the group that enables that trust.
The error from the linqpad connection is: "The target principal name is incorrect.Cannot generate SSPI context".
The UDL file allows the connection to work once it has the Server SPN = value set but otherwise gets the same error.
Update:
During testing we have found that specifying the SPN results in NTLM authentication to the server. Therefore if there is a way to force this from the client that would be a possible route for us.
Update + Workaround: We have stumbled across a workaround, adding the server into the hostfile with a different name seems to trigger the same fall back to NTLM authentication to work for the LinqPad connection. Would still appreciate if anyone understands how to fix this correctly but for now we are using the hostfile workaround.
Any help appreciated
I can think of several possible issues here:
Your one-way trust is set up the wrong way around;
It's too selective;
Incompatibility in AD versions between domains.
I would recommend trying Kerberos Configuration Manager for SQL Server, it might give you some insight into the root cause.
Also, I believe you might have better chances asking this on ServerFault rather than here. By the looks of it, it's a misconfiguration issue, and has nothing to do with programming.
I am not able to start sql server 2008 R2 service . I cross checked all answers given here for same problem without any success. I disabled VIA protocal, still it didnot start. I tried using all options(local system, local server, network service) for login, but still nothing happened. I have SQL Server 2008 also installed and that is working fine without any problems. R2 was working fine , but due to unknown reasons it is not.
I can't uninstall as I can't loose databases mounted in it.
Have you checked the credential used to start the service? You may have changed password or permissions for that specific user.
To check this settings, open the Service panel (services.msc), go to the SQL Server Service named as your Instance (ex. SQL Server (MSSQLSERVER) ), doubleclick and go to the Connection tab. Check the authentication you provided there is valid, and that the user has all the permissions needed to start and stop the instance, or try a different user.
If you are the administrator of the machine, "Local System Account" should be enough to start/stop the service.
Otherwise, please follow the link down here and check in the Event Viewer which error is provided there. If it's different from the one described in the article, give us yours. This could help us help you ;)
source:
http://blog.sqlauthority.com/2011/03/29/sql-server-fix-error-the-request-failed-or-the-service-did-not-respond-in-timely-fashion-consult-the-event-log-or-other-applicable-error-logs-for-details/
Step 1 - Check credentials for service
Step 2 - Check event viewer and look for error messages it sends. It should be found in Windows Logs -> Application
Once you see any log events with errors or warnings when trying to start the service, please update the question/thread so we can see and help you troubleshoot from that point.
Thanks,
Matt
I'm not sure why you can't uninstall and reinstall. You could detach the databases, uninstall, reinstall, and attach the databases. You won't lose the databases.
Try to identify the exact issue why service is failing. The possible reasons are logged in event logs. Have a look at the event logs and post what is printed there. Once the reason for failure is identified then probably we will be able to help you out.
Also, try installing service packs. Because in the past I had an issue with SQL Server 2008 R2 and I installed the service pack. That resolved the issue.
I'm trying to configure Team Foundation Reporting but without any success.
The App Tier and the Data Tier are in separate servers.
I guess it's not a port/firewall problem, because I opened port 135, and I can see the established connection by using TCPView (from Sysinternals) whenever I click "Populate URLs" in the Reports tab in TFS Administration Console. I can also telnet servername 135 without any problems.
I also checked if WMI service is started in the Data-Tier. And for SQL Server Reporting Services. Also checked for RPC and RPC Locator in both servers. They're all started and automatic.
I also set tfs app user as admin in sql reporting services. Added all kinds of permissions to the tfs user in the Data-Tier server.
I set all user permissions in dcomcnfg.
Allowed all WMI namespaces permissions to the user. (Computer Management -> WMI Control)
Deactivated Windows Firewall in both servers temporarily.
No luck.
However, in the app-tier, when I click Computer Management -> Connect to another computer, and type the data-tier IP, i can't connect. I get the message "Computer xxx cannot be managed. The network path was not found". How is that ? Tried IP, name, and FQDN. I also tried browsing and selecting the computer. Nothing changed.
I'm lost, what could possibly be happening ?
Thanks in Advance!
i'm betting that you're having the double-hop issue. try having your system admin set an spn for the website on the sql server.
you also need the AD permission 'trust for delegation' on the AD Service Account, right?
do that and SetSpn with the service account, that should help I think that the SPN option was spot on
See this answer:
IIS to SQL Server kerberos auth issues
which links to an old but user-friendly troubleshooting web app called DelegConfig. It can try to run the SetSpn commands for you, at least giving you an idea of what they need to be.
I ran into SPN issues when using an externally-accessible URL (+SSL) everywhere.