I am using power shell scripts to create...
an automation account named "my account"
i add 3 variables to "my account"
i then via the portal delete the 3 variables. Then the automation account.
i then run the scripts for steps 1 and 2 above again but get a conflict error on the variables as they exist after step-1.
Not sure why the delete variables is not working, maybe there's a reason?
Related
Does anyone have solution steps, where I can see how to work on multi user workspace which was created by another user in Tricentis Tosca.
Note: The workspace is stored in MS sql DB by another user, I want to work on same workspace.
I search a lot but not getting details steps.
Before you can work on an object in a multi-user workspace it must be checked out. You might look into taking the Automation Specialist 1 training class as I believe it has a section that covers checkin/checkout.
We are currently using MTM (application, not web) to house our test cases. We are moving to Azure Devops >Test Plans. We would like to export from MTM and import into ADO. Is there an easy way of doing this? I can not find a lot of info on this subject any help would be greatly appreciated.
If you want to move all the test cases from MTM to ADO then you can make use of Excel sheet for this bulk update.
In Excel sheet
-->Team tab
-->New List
-->Click on Servers
-->Add Your organization URL.
Select the project and add all your test cases to given table .
After adding all the test cases save it and again go to team tab .
Click on publish and in your ADO you can refresh and see the new test cases added over there .
For more details see this youtube video Click Here
I am running SQL Server Management Studio v17.6.
The online tutorials for creating a new Login show a dialog that comes up when your right-click on Logins and select New Login.
I don't see this dialog; instead I get a script to CREATE LOGIN which is OK but I would prefer the dialog.
I don't see an option to switch from getting a script to getting the dialog. I don't know if this version does not have the dialog or if I am just not finding the option.
Currently this is an Azure SQL limitation.
More information can be found here on azure.microsoft.com or here on Microsoft docs.
When creating a new login with the following SSMS menu item:
this is what appears with an Azure SQL database:
instead a dialog window appears when using a local database:
I also found a helpful post that explains the limitations at the time of this post.
Azure SQL limitations
What I did was inside SSMS, while connected to your Azure SQL instance, make sure you are first connected to the master database as shown:
Then run this script with your values against the master DB.
CREATE LOGIN WorldCitiesLogin
WITH PASSWORD = N'<your_password>'
GO
Next, switch your instance in SSMS to the database you want to map your login:
Then, run this script with your user name that maps to the newly created login above:
CREATE USER WorldCitiesUser
FOR LOGIN WorldCitiesLogin
WITH DEFAULT_SCHEMA = [dbo]
GO
I have an office 365 account who's directory I want to attach as a new Tennant (probably wrong terminology there) in my Azure account. I'm trying to use the new Office 365 API preview against my existing Office 365 account. So I'm trying to link these two accounts via the Active Directory in Azure.
I log in to my Azure account, go to the Active Directory Node, And select custom create. Nowhere is there an option to "Use existing directory" that I can point to my 365 subscription.
I keep reading documentation that says there should be a dropdown to let me choose that. But I'm not seeing it. All I see are text boxes for "Name", "Domain Name" and Country or region.
Below are two links that mention being able to select "existing" but I'm not seeing it. Has there been a new way to implement this? Or perhaps its some kind of permissions issue. I'm not being given the option to do so because I have insufficient rights.
http://msdn.microsoft.com/en-us/library/office/dn605899(v=office.15).aspx
http://www.clemensreijnen.nl/post/2014/07/11/Add-an-existing-Office-365-Azure-Active-Directory-to-your-Azure-Subscription.aspx
I am new to SSRS and have deployed several reports. When I force windows authentication, everything works fine, but when I do this:
I am getting this error:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'DataSet1'.
(rsErrorExecutingCommand) Login failed for user 'DWH_Reporting_User'.
I've configured the DWH_Reporting_User like this:
here are the details on DWH_Reporting_User for the ReportServer database:
here is the security on the server:
when i try to set security for that specific folder:
i am getting this error msg:
is there something obviously wrong with the way I've configured things?
The answer to this question was a series of comments. I went ahead and put it in the chat as well as an answer.
Go to the security of the server not the database and map the user to that database.
Can you recycle the application pool on the server where reporting services is running? Or reboot the IIS server if possible.
Another thing that comes to mind, when you launch this report it goes into the report server "Portal". Does this user have access to the actual report to view it? Click the details section of this "Portal" and assign this user as a content manager role.
DWH_REPORTING_USER is this an admin account on your domain?
Local admin on the server, so did you grant \COMPUTER_NAME\DWH_Reporting_User rights as a content manager in the roles section? Why dont you use a domain admin account?
So how do you access the actual report - that is your issue.
Do me a favor aprem, write up a stored procedure or sql query in the first tab of reporting services and run it using that user. Meaning in the shared data source it should be using this user DWH_Reporting_user. Test the connection then write a small sql statement to retrieve some data. Run the SQL script from within RS do you see any data?
#Aprem look at the three tabs at the top of rs, its the first tab to define datasets, this is where you can create an SQL query (and run it using the red exclamation mark). – JonH 20 mins ago
i defined a new dataset as "select top 1000 * from mytable", i rebuilt the project, deployed it, and now what do id o? – Артём Царионов 16 mins ago
In the "Shared Datasets" you have a dataset right? Double click on it and go to "Query Designer" it is a button on this form. Click on it and "Execute" the query (red exclamation mark). You dont need to deploy it right now, just do it on a test machine.ago
You specify the user in the datasource section "Shared Data Sources", that account is the account being used to "pull" the data. You really need to experiement with RS some more or read some material on it. This is as basic as it gets.
*Ok aprem do you understand your issue now, the user you are using to get the data has no issues, in addition, it is functioning correctly. Now you have to view the report. To view the report is to view the webpage, and to view a web page means you need to either use "Anon" access or windows authentication. So you need a domain or local WINDOWS account to view the report. This account needs to be setup on the RS portal as a content manager role. *
You are dealing with two beasts, one is the database (db server) and one is IIS (web server) each serve a specific purpose. The database serves to allow you to pull data while the web server hosts the pages.
The reportserver database is very important, it keeps a listing of all your reports and the meta data associated with your reports in the database. It also stores job ids and subscriptions associated with your reports. Basically it is the backend database for all reporting services stuff like reports, datasets, and datasources. Think of it this way when you create a new "Report Project" you are allowed to create reports, datasets, and datasources. Without the reportserver database how would the system remember your datasets, datasources, and report names? It is the heart of rs.
your data set is not used to connect to the reporting services databse, it is used to connect to the database you are getting the data to display on your report.
Does that user exist on the database the report is accessing?