error while processing warehousecontrolwebservice using TFS web URL (TFS-2018) - reporting-services

i am getting below error when invoking GetProcessingStatus, any help to get this working will be appreciated
Actually we never used TFS analysis for providing reports, now i am trying to exploring that options too.
I used below url to process the cube of analysis services
URL : http://localhost:8080/tfs/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx
After browsing that url we get below services
BringAnalysisProcessingOnline,
BringWarehouseProcessingOnline,
ChangeSetting,
GetJobProperties,
GetProcessingStatus,
GetSettings,
ProcessAnalysisDatabase,
ProcessDimensionForExpandedCapacity,
ProcessWarehouse,
SetAnalysisJobEnabledState,
SetWarehouseJobEnabledState,
TakeAnalysisProcessingOffline,
TakeWarehouseProcessingOffline,
Selecting "GetProcessingStatus" and invoking it with includeOnlineHostsOnly = True
Reporting configuration on TFS Console
Error
[Full Analysis Database Sync]: --->
AnalysisDatabaseProcessingType=Full, needCubeSchemaUpdate=True. --->
Microsoft.TeamFoundation.Warehouse.WarehouseException: TF221122: An
error occurred running job Full Analysis Database Sync for team
project collection or Team Foundation server TEAM FOUNDATION. --->
Microsoft.TeamFoundation.Warehouse.WarehouseException: Failed to
Process Analysis Database 'Tfs_Analysis'. --->
Microsoft.TeamFoundation.Warehouse.WarehouseException: Internal error:
The operation terminated unsuccessfully. Errors in the high-level
relational engine. . The exception was raised by the IDbConnection
interface. Errors in the high-level relational engine. A connection
could not be made to the data source with the DataSourceID of
'Tfs_AnalysisDataSource', Name of 'Tfs_AnalysisDataSource'. Errors in
the OLAP storage engine: An error occurred while the dimension, with
the ID of 'Dim Changeset', Name of 'Version Control Changeset' was
being processed. Errors in the OLAP storage engine: An error occurred
while the 'Changeset Title' attribute of the 'Version Control
Changeset' dimension from the 'Tfs_Analysis' database was being
processed. Server: The current operation was cancelled because another
operation in the transaction failed. Errors in the high-level
relational engine. . The exception was raised by the IDbConnection
interface. Errors in the high-level relational engine. A connection
could not be made to the data source with the DataSourceID of
'Tfs_AnalysisDataSource', Name of 'Tfs_AnalysisDataSource'. Errors in
the OLAP storage engine: An error occurred while the dimension, with
the ID of 'Assembly', Name of 'Assembly' was being processed. Errors
in the OLAP storage engine: An error occurred while the 'Assembly'
attribute of the 'Assembly' dimension from the 'Tfs_Analysis' database
was being processed. Errors in the high-level relational engine. . The
exception was raised by the IDbConnection interface. Errors in the
high-level relational engine. A connection could not be made to the
data source with the DataSourceID of 'Tfs_AnalysisDataSource', Name of
'Tfs_AnalysisDataSource'. Errors in the OLAP storage engine: An error
occurred while the dimension, with the ID of 'Dim Changeset', Name of
'Version Control Changeset' was being processed. Errors in the OLAP
storage engine: An error occurred while the 'Changeset ID' attribute
of the 'Version Control Changeset' dimension from the 'Tfs_Analysis'
database was being processed. Errors in the high-level relational
engine. . The exception was raised by the IDbConnection interface.
Errors in the high-level relational engine. A connection could not be
made to the data source with the DataSourceID of
'Tfs_AnalysisDataSource', Name of 'Tfs_AnalysisDataSource'. Errors in
the OLAP storage engine: An error occurred while the dimension, with
the ID of 'Dim Changeset', Name of 'Version Control Changeset' was
being processed. Errors in the OLAP storage engine: An error occurred
while the 'Checked In By' attribute of the 'Version Control Changeset'
dimension from the 'Tfs_Analysis' database was being processed. Errors
in the high-level relational engine. . The exception was raised by the
IDbConnection interface. Errors in the high-level relational engine. A
connection could not be made to the data source with the DataSourceID
of 'Tfs_AnalysisDataSource', Name of 'Tfs_AnalysisDataSource'. Errors
in the OLAP storage engine: An error occurred while the dimension,
with the ID of 'Dim Changeset', Name of 'Version Control Changeset'
was being processed. Errors in the OLAP storage engine: An error
occurred while the 'Policy Override Comment' attribute of the 'Version
Control Changeset' dimension from the 'Tfs_Analysis' database was
being processed. Warning: Parser: Out of line object 'Binding',
referring to ID(s) 'Tfs_Analysis, Team System, FactCurrentWorkItem',
has been specified but has not been used. Warning: Parser: Out of line
object 'Binding', referring to ID(s) 'Tfs_Analysis, Team System,
FactWorkItemHistory', has been specified but has not been used.
Warning: Parser: Out of line object 'Binding', referring to ID(s)
'Tfs_Analysis, Team System, v Fact WorkItem To Tree', has been
specified but has not been used. Warning: Parser: Out of line object
'Binding', referring to ID(s) 'Tfs_Analysis, Team System, v Fact
Linked Current WorkItem', has been specified but has not been used.
Warning: Parser: Out of line object 'Binding', referring to ID(s)
'Tfs_Analysis, Team System, Fact WorkItem To Category', has been
specified but has not been used. Warning: Parser: Out of line object
'Binding', referring to ID(s) 'Tfs_Analysis, Team System, v Fact
WorkItem Changeset', has been specified but has not been used.
Warning: Parser: Out of line object 'Binding', referring to ID(s)
'Tfs_Analysis, Team System, Fact Build Project', has been specified
but has not been used. Warning: Parser: Out of line object 'Binding',
referring to ID(s) 'Tfs_Analysis, Team System, Fact Build Details',
has been specified but has not been used. Warning: Parser: Out of line
object 'Binding', referring to ID(s) 'Tfs_Analysis, Team System, Fact
Code Churn', has been specified but has not been used. Warning:
Parser: Out of line object 'Binding', referring to ID(s)
'Tfs_Analysis, Team System, v Fact Test Result Overlay', has been
specified but has not been used. Warning: Parser: Out of line object
'Binding', referring to ID(s) 'Tfs_Analysis, Team System, Fact Build
Changeset', has been specified but has not been used. Warning: Parser:
Out of line object 'Binding', referring to ID(s) 'Tfs_Analysis, Team
System, Fact Build Coverage', has been specified but has not been
used. Warning: Parser: Out of line object 'Binding', referring to
ID(s) 'Tfs_Analysis, Team System, v Fact WorkItem Test Result', has
been specified but has not been used. Warning: Parser: Out of line
object 'Binding', referring to ID(s) 'Tfs_Analysis, Team System, v
Fact Linked Current Work Item Test Case', has been specified but has
not been used. Warning: Parser: Out of line object 'Binding',
referring to ID(s) 'Tfs_Analysis, Team System, Fact Run Coverage', has
been specified but has not been used. at
Microsoft.TeamFoundation.Warehouse.TFSOlapProcessComponent.ExecuteXmla(String
finalXmla) at
Microsoft.TeamFoundation.Warehouse.TFSOlapProcessComponent.ProcessOlap(AnalysisDatabaseProcessingType
processingType, WarehouseChanges warehouseChanges, Boolean
lastProcessingFailed, Boolean cubeSchemaUpdateNeeded) --- End of inner
exception stack trace --- at
Microsoft.TeamFoundation.Warehouse.TFSOlapProcessComponent.ProcessOlap(AnalysisDatabaseProcessingType
processingType, WarehouseChanges warehouseChanges, Boolean
lastProcessingFailed, Boolean cubeSchemaUpdateNeeded) at
Microsoft.TeamFoundation.Warehouse.AnalysisDatabaseSyncJobExtension.RunInternalCore(IVssRequestContext
requestContext, TeamFoundationJobDefinition jobDefinition, DateTime
queueTime, String& resultMessage) at
Microsoft.TeamFoundation.Warehouse.AnalysisDatabaseSyncJobExtension.RunInternal(IVssRequestContext
requestContext, TeamFoundationJobDefinition jobDefinition, DateTime
queueTime, String& resultMessage) at
Microsoft.TeamFoundation.Warehouse.WarehouseJobExtension.RunCore(IVssRequestContext
requestContext, TeamFoundationJobDefinition jobDefinition, DateTime
queueTime, String& resultMessage) --- End of inner exception stack
trace ---

You need to check the link to the datawarehouse.
Is the datawarehouse OK?
Connect to the data analysis server.
Go to the data source of Tfs_AnalysisServices and open properties.
Check the connection string, check if the connection string is OK.
If the connection string is not OK, fix it on the TFS Console. If the link is OK, maybe there is some problem in the datawarehouse, and you need to rebuild it too.

Update
You should run the ProcessDimensionsForExpandedCapacity web service when you receive one of the following error messages:... For Version Control. Check if this do the trick.
More details please refer this link-- Process dimensions for expanded capacity
Besides, you should also check TFS Server Event View and go through if there is some useful information to help you narrow down the issue.
TF221122: An error occurred running job Full Analysis Database Sync
for team project collection or Team Foundation server TEAM FOUNDATION.
--->
According to the detail error info in your shared log part. I would suggest you first check if the account you used the data source TFS_ASDataSource has bad or expired password or that the account does not exist anymore.
If this is a new deployment it might also be possible that the account does not have access to the TFS_Warehouse database or Tfs_Analysis database or it is not a member of the tfswarehousedatareader role.
To better troubleshoot is to update account used to access the data sources in the Team Foundation Server Administration Console in the Reporting page.
Or you could directly use workaround deleted the whole Analysis Database, and run the “Rebuild” operation from the Application Tier following the steps below:
Open Team Foundation Server Administration console.
Go to Reporting and there is “Start Rebuild”.
Note that this action could be used to rebuild your data warehouse and analysis database for the cube. Once you start it, it will take offline, delete, and rebuild both your Warehouse and Analysis Services databases. Based on the amount of data you have in your TFS DB, it could take significant amount of time to complete these jobs. The reports will not show any data until the above databases are not rebuilt successfully. This may do the trick.

Related

SSIS Chunk Timeout Errors exporting data using CData Snowflake Source

Anyone run into this error? How do I resolve, not getting much guidance from cdata or snowflake.
Error: 0x0 at ADI_PRODUCT, CData Snowflake Source: Get data error: Retrieved Chunk#0 Timeout.
Error: 0xC0047062 at ADI_PRODUCT, CData Snowflake Source [279]: System.Exception: Get data error: Retrieved Chunk#0 Timeout.
at CData.SSIS.Snowflake.SSISSourceComponent.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper100 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer100[] buffers, IntPtr ppBufferWirePacket)
Error: 0xC0047038 at ADI_PRODUCT, SSIS.Pipeline: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on CData Snowflake Source returned error code 0x80131500. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
I am not sure about this, but given the fact that there appears to be a timeout retrieving data (presumably from Azure's cloud storage), it might be worthwhile to verify that you are not encountering a networking issue (eg. firewall) by verifying connectivity via Snowflake's SnowCD utility. Just a thought.

SSIS Issue Pulling Data From Snowflake - [CData Snowflake Source] Error: Get data error: Received metadata with an incompatible version number

I'm trying to run a simple data flow task in SSIS pulling data from Snowflake to SQL Server using a component from CDATA called Snowflake Source.
Connection works and I can also see a preview of the data but when actually running the package I get the following error message:
[CData Snowflake Source [2]] Error: System.Exception: Get data error: Received metadata with an incompatible version number
at CData.SSIS.Snowflake.SSISSourceComponent.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper100 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer100[] buffers, IntPtr ppBufferWirePacket)
Has anyone experienced this before or know what to do in order to fix it?
Hi I faced this error many time , when i use some custom script component or third party component.
Issue : We do remove or delete some component but some of the reference is not removed from package (it is very tough to debug )
Create fresh package it will work .

SSRS Migration from 2008R2 to 2017 Error RSPortal

I was migrating our reporting services from the version 2008R2 to the version 2017 restoring the db and all seems to work fine unless for some report for which I cannot open the subscriptions page.
For those report every time I enter in the report subscriptions page from the web view I get this error
"Something went wrong. Please try again later. "
If I go in the log from the RSPortal File I see this error:
ERROR: OData exception occurred: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.FormatException: The string was not recognized as a valid DateTime. There is an unknown word starting at index 18.
at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
at Microsoft.ReportingServices.Portal.Services.ODataExtensions.ParameterValueExtensions.FormatAsISO8601Date(String date, String culture)
at Microsoft.ReportingServices.Portal.Services.ODataExtensions.ParameterValueExtensions.ToWebApiReportParameterValue(ParameterValue parameterValue, ReportParameterType reportParameterType, String culture)
at Microsoft.ReportingServices.Portal.Services.ODataExtensions.SubscriptionExtensions.ToReportPameterList(SubscriptionImpl librarySubscription, Dictionary`2 parameterTypes, String culture)
at Microsoft.ReportingServices.Portal.Services.ODataExtensions.SubscriptionExtensions.ToWebApiModel(SubscriptionImpl librarySubscription, Dictionary`2 parameterTypes, SubscriptionProperties properties)
at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
Does anyone have a suggestion on how to solve it? I thought was something related to the CultureInfo value but I am not sure.
Thanks
Probably could be helpful for someone in the future so I will indicate the steps I took to solve this issue:
This issue was due to a data type mismatching on one parameter for a few subscriptions.
Seems that the error handling has changed in the time with Microsoft in fact, after I found the subscriptions that were having problems I tried to open them in the old environment and I have got this error:
“The Value provided for the report parameter “YourDate’ is not valid for it is type (rsReportParameterTypeMismatch)”
What I did so was to delete these subscriptions with the error in the new Reporting Server environment and finally the web view worked fine

Oracle SOA BPEL calling a MySQL Procedure - parameter number 2 is not an out parameter

Currently I have a use case where I need to invoke a Mysql Procedure thorough Oracle BPEL. The adapter configuration is fine and shows me the available In/Out parameters during the configuration and the composite is deployed successfully. However the invocation is failed during the webs service call.
Any idea about the issue particularly in SOA. The weblogic version is 12c & I am using jDev 11g for the composite development.
Below is the error message received during the web service call-
The selected operation process could not be invoked.
A fault occurred while invoking the webservice operation. The fault is : <env:Fault xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>env:Server</faultcode>
<faultstring>Exception occurred when binding was invoked.
Exception occurred during invocation of JCA binding: "JCA Binding execute of Reference operation 'getUserFirstName' failed due to: Register out parameter error.
Error registering parameter First_Name as an out parameter.
An error occurred when registering parameter First_Name as an out parameter of the getUserName API. Cause: java.sql.SQLException: Parameter number 2 is not an OUT parameter
Check to ensure that the parameter is a valid IN/OUT or OUT parameter of the API. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
".
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</faultstring>
<faultactor/>
<detail>
<exception>Parameter number 2 is not an OUT parameter</exception>
</detail>
</env:Fault>
oracle.sysman.emInternalSDK.webservices.util.SoapTestException: Client received SOAP Fault from server : Exception occurred when binding was invoked.
Exception occurred during invocation of JCA binding: "JCA Binding execute of Reference operation 'getUserFirstName' failed due to: Register out parameter error.
Error registering parameter First_Name as an out parameter.
An error occurred when registering parameter First_Name as an out parameter of the getUserName API. Cause: java.sql.SQLException: Parameter number 2 is not an OUT parameter
Check to ensure that the parameter is a valid IN/OUT or OUT parameter of the API. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
".
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
Step wise DB Adapter configuration is here-
https://drive.google.com/open?id=1cei0OFje1dmefDn7PfBIjxW4vb81Ngez
I think you made a mistake while you are selecting in and out parameters, probably you have added more variable than your database are expecting. Please look at the following and if possible send more details like screenshots of your db adapter configurations and db table
java.sql.SQLException: Parameter number 2 is not an OUT parameter

Transferring SBEE configuration - Error: Entity of type Dimension does not provide field DimensionLinkDimensionID

We are trying to transfer a SAP Smart Business, executive edition 1.0 1509 (SBEE) configuration from one system to another (Importing and Exporting Dashboard Definitions)
During the Import we get the error message: The following error occurred: Entity of type Dimension does not provide field DimensionLinkDimensionID
We did not find the error message using a search engine :/
Any ideas how to fix this?
I guess this must be a bug with the application. Talk to SAP, it would be fixed ASAP :-)