Error: User with Owner access at subscription level getting a failed error while opening Synapse Studio, and not able to see any pipelines, linked service etc
Failed to load one or more resources due to no access, error code 403
Root Cause: Even if you have owner level privileges at the subscription level, you still have to assign rights inside Synapse Studio.
Fix: Go to Synapse Studio > Manage tab
Go to Access Control > Click on Add
Add the user you want to give Administrator access to
Issue description: New user not able to create an Azure Data Factory instance despite having owner or contributor group access at resource group level.
Error - The client '' with object id '' does not have authorization to perform action '' over scope '/subscriptions/' or the scope is invalid. If access was recently granted, please refresh your credentials. (Code: AuthorizationFailed) (Code: AuthorizationFailed)
Root Cause - The root cause of this issue is that, when you setup a subscription, only a default set of Microsoft Providers are by default registered.
Fix: Go to Subscriptions > Resource Providers and add/register the 'Microsoft.DataFactory' provider.
Issue: PowerBI was not able to refresh the underlying dataset from Azure Synapse in a higher environment in Import mode.
Sample error screenshot is below,
Cause : The issue was caused when in the higher environment, the schema name was created in upper case letters where as in the lower environment it was in lower case letters.
Resolution: The fix in this case is to move objects from the existing uppercase schema to lower case, this will incur some effort if you are doing it, since first you will have to move it to a temporary schema name, then drop the uppercase schema name, create lowercase schema name and then move from the temporary schema to lowercase schema name.
Another option is to parameterize the schema in PowerBI and change at one place when you migrate to higher environment.
Guidewire Datahub is a P&C enterprise data warehouse solution built on top of the three key Guidewire Insurance Suite systems namely Guidewire Policycenter, Billingcenter and Claimcenter. It is a ETL framework that has been built using SAP BODS ETL tool and a java framework named DIAL for SCD Type 1 and Type 2 implementation.
Focused on Property and Insurance clients, Datahub provides an operational datastore which provides a single version of truth and enabling clients to execute cross analytical queries across systems. The system also provides you capability to source data from external data systems. The layers of the architecture enables data quality and auditing to make sure that the data you have in target is clean and audited.
 |
| Guidewire Datahub Basic Architecture |
The first layer in the architecture are the sources, which can be either one of the three sources from PC, BC or CC, it can even be an external source or a legacy system. In this layer the data from the sources are loaded into a ftp source and from the ftp source to the relational database where Guidewire Datahub resides.
The second layer is the Guidewire Datahub layer which is a relational dbms and can be in either Oracle Database or a SQL Server database. In this layer data is captured at an entity level in both Type 1 and Type 2. All the data cleansing, quality checks, balancing an auditing happens at this layer. This layer is loaded and managed using the SAP BODS or SAP Data Services tool.
The next layer is where you built out your star schema diagrams based on your reporting needs, this layer will have your facts and dimensions and will be used by IBM Congnos Analytics to cater to your reporting needs.
This forms the basic architecture of the Guidewire Datahub suite. Please do let me know if you would like me to cover more topics on the Guidewire Datahub suite.
Issue: Restarting a terminated cluster gives the below error message
Cluster terminated.Reason:Cloud Provider Launch Failure
A cloud provider error was encountered while launching worker nodes. See the Databricks guide for more information.
Azure error code: AllocationFailed
Azure error message: Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance
Cause: Allocation of resources failing as Azure cloud doesn't have requested VM size in the region. This is a region specific error when the requested resources are too much for the region and doesn't have additional resources to get the cluster running.
Resolution: Microsoft has documented the resolutions here in this article.
Update:- After waiting a while and a couple of restarts later, it started running again for us.
