I'm having the following problem when trying to setup Substream Assembler filter with Substream Selector:
I have the following basic setup in the ADTF tool:
The input to Substream Assembly is simply a dummy filter, generating some random data and sending it to the output pin.
Substream assembly is supposed to take multiple inputs from the usual, non-substream returning filters and transform it into a substreams, if I understand it correctly, and then we can extract them with Substream Selector.
I cannot understand where this warning/error is coming from. Do you have any ideas? Thanks!
The warning seems to be just a bug, maybe based on initialization order issues (egg-chicken-issue).
As you can see above the Substream Selector, samples are processed. Just connect for example a Qt5 Media Description Display to the Substream Selector and you will see the values of P_tInt32.
If you use an invalid name, for example P_something, you will get the warning twice and no data. So yes, you can just ignore the warning during startup, everything is fine and will be fixed in upcoming releases.
The Repo is here:
https://github.com/Learn-NEAR/NCD.L1.sample--art-demo
I have set the environment variables as stated in the README.md
However as I tried calling the design() the following error occurred as shown:
Then I realised the contract might need to be deployed first, but there is no such command for deployment in package.json
Pls let me know how I could get it to work.
The error is because the seed value you are using in the payload should be either a number without trailing zeroes or a string (wrapped with quotes). Notice the error is that the json parser is failing to convert the input to a json object. From the README I think it should be a number.
Try with:
near call CONTRACT '{"seed": 1}' --accountId ACCOUNT
FYI: This is going to fail, but with a different error. Both CONTRACT and ACCOUNT are invalid account names, so they won't be recognised. This tutorial doesn't contain steps for deploying, but as you pointed out, that is required before you are able to run it by yourself.
When trying to generate a sitemap I keep getting this error and the job stalls out
I noticed this error in 8.4.3 so i updated to 8.4.4 and it still is present
Error:
Argument 2 passed to
Concrete\Core\Page\Sitemap\Element\SitemapPage::__construct() must
implement interface Concrete\Core\Url\UrlInterface, instance of
League\Url\Url given, called in
/home2/cedarcom/public_html/updates/concrete5-8.4.4_remote_updater/concrete/src/Page/Sitemap/SitemapGenerator.php
on line 316
If anyone has some insight on how this, it would be much appreciated!
This has been fixed by https://github.com/concrete5/concrete5/pull/7363, so the upcoming concrete5 8.5.0 won't suffer this problem.
If you want to fix your running installation, you can edit these two files:
/home2/cedarcom/public_html/updates/concrete5-8.4.4_remote_updater/concrete/src/Page/Sitemap/Element/SitemapPage.php
/home2/cedarcom/public_html/updates/concrete5-8.4.4_remote_updater/concrete/src/Page/Sitemap/Element/SitemapPageAlternativeLanguage.php
by replacing this line
use Concrete\Core\Url\UrlInterface;
with
use League\Url\UrlInterface;
A very common, error message in Apache Pig is:
ERROR 1066: Unable to open iterator for alias
There are several questions where this error is mentioned, but none of them give a generic approach for dealing with it. Hence this question:
What to do when you get an ERROR 1066: Unable to open iterator for alias ?
The message "ERROR 1066: Unable to open iterator for alias myAlias" suggests that there is something going wrong in the line where you use myAlias.
However, usually you will see this error if something went wrong BEFORE you are trying to use this alias. So the first thing to do is look up further along the error message, and see whether this is truely the first error that is thrown.
Here is what I found to be an efficient way to deal with this error when I did not easily spot an earlier error:
Run the code untill just before you first define the the alias.
Look carefully, whether you see any mention of ERROR (often it is in the last lines, but sometimes this can happen earlier)
By now you probably have an error, if so: deal with it and go to 1.
It is possible that you don't have an error before encountering the alias, in this case evaluate the line where the alias occurs.
If the error occurs: Deal with it and go to 4; If no error occurs run the code untill just before you use the alias for the second time, and go to 3.
Notes:
To easily run PIG code line by line: Open pig on the command line (Simply type pigor pig -useHCatalog for example)
If you get confused, make sure you only define the alias once. (I believe this is good practice in general)
I once received this error when using the SUM function. I was summing values that had nulls among them. After filtering out the null values in the prior lines, it worked properly.
simply try in another command window you will not get error
I understand that there is definitely something wrong with my report (e.g. columns missmatcch) and I need to correct it but what I see is the WCF error message that hides actual problem and exactly this hiding irritates me much more than original problem: columns missmatch.
I guess we need to adjust the WCF 'buffer size' and we will get original problem message. But where is the config file?
Text search of "system.serviceModel" in the C:\Program Files (x86)\Microsoft Visual Studio 10.0 doesn't bring good idea...
P.S. Since this is just preview of report I do not think that it is SSRS configuration problem. Problem localised somewhere in DevStudio process or int the DevStudio's internal web server process ...
P.P.S Please help me too improve the question. I see that responders doesn't understand what kind of help I need.
I have encountered multiple "flavors" of this bug in SSRS Preview. It seems the renderer for Preview mode is quite fragile.
There is a simple way to solve this. Ignore the error and attempt to upload the RDL file to your reporting server. The uploader will happily tell you exactly what is wrong with your file - it will tell you exactly what field has a problem and what that problem is. If there are multiple errors, you will get told each and every field and the error associated with each one.
I can create this bogus XML buffer error with any of the following:
Add a new Tablix, start to connect it to a dataset, then cancel out.
Copy/paste some text into a textbox from a MS Word document where one or more lines have a negative right indent (right column end is outside page margin).
Connect a dataset with a varchar(8000) returned value.
Please Check if any of your report items are referencing fields that are not in existing dataset scope.
This indeed worked for me.
See Below link for more information:
http://connect.microsoft.com/SQLServer/feedback/details/742913/ssdt-reporting-services-designer-error
I have seen this error when adding a new field to an existing dataset by clicking "Refresh Fields".
The dataset source was a stored procedure. The result was only a few of original fields showed up in the dataset field list and not the new field. If I tried to preview the report I get XML buffer error.
Workaround was to not refresh fields but hit add new field and type the new field name into the dataset properties field last.
Worked fine after that.
I got this error again today.
I had created a table to hold data to replace two slow queries. I changed some names to clean up the process.
I think the error actually means that there are so many problems with my report that the buffer holding the various error messages isn't large enough which leads to the error message.
The size necessary to buffer the XML content exceeded the buffer quota
Of course this should be an easy fix but Microsoft has said that they will not fix it.
https://connect.microsoft.com/SQLServer/feedback/details/742913/ssdt-reporting-services-designer-error
EDIT: I've updated my answer based on having fixed the issue.
I'm currently experiencing this problem after having changed multiple stored procedures and updating the dataset names in the SSRS report.
And when I try to run the preview I get the exact same error.
As it turns out, after investigating the issue, the problem was that I had changed the name property of my datasets.
There several places in my report where formulas or expressions use the old name properties of the datasets I renamed. After reverting the dataset names back, I managed to get the real errors like missing fields etc. atcual errors came back after I set my dataset name properties back to what they were.
I only changed the name property back to what it was, the stored procedure names were correctly referring to my renamed stored procedures.
I had this problem when after copying and pasting a tablix, it changed CDbl in a formula to Microsoft.ReportingServices.RdlObjectModel.ExpressionParser.VBFunctions.CDbl. I opened up the XML and removed all instances of "Microsoft.ReportingServices.RdlObjectModel.ExpressionParser.VBFunctions." and the report then worked.
For a working report, when I tried to add a column it gave me this error. I edited the .rdl file using notepad++. After SSRS prompt to reload the change from disk, it worked without issues.
I got this error after copying my Custom Code to Visual Studio for hightlighting the code for better readability. Well, Visual Studio added class definitions to the beginning and end of the file. After editing code, I pasted it back to report Custom Code, then got this error. Fix was just to remove class definitions (Public Class Class1 and End Class) from Custom Code. So, check your Custom Code also (if any).
I got this error after adding some new parameters to an existing report.
For some reason when I created the parameters first then modified the Dataset to use the new parameters I got the error, but when I modified the Dataset first then added the parameters second and I did not get the error.
This seemed like very strange behavior to me so I tested it by restoring the report from repository and repeating the process three times with each method, and had identical behavior every time.
I am also facing this problem. I solve this Find and replace
Microsoft.VisualBasic.Interaction.iif ==> iif
Microsoft.ReportingServices.RdlObjectModel.ExpressionParser.VBFunctions.cdbl
==> cdbl
I hope this may helps someone. Thanks
Possible root causes
Parameter name is incorrect(case/order)
Accessing non-existing property.
and many more...
Solution: To get the exact error message are
Deploy SSRS report and find the error : Suggested by "Kim Crosser" already
Remove the section(SSRS/Report content) temporarily you feel is error free to free space in buffer so that you can get actual error message. Later add sections back to the page(removed earlier).
I had the same error message and it was totally caused by my doing. It's a bit embarrassing, but if it helps someone out then great! I had accidentally copied my dataset query that included a small sub select statement within it, which I was using to check parameter/variable values.
Another solution is to open the .rdl file in Report Builder 3.0 (as opposed to Visual Studio) and try to preview it. I found this gave me the details of the error, although if more than one error is present it only shows the first.
I previously binded a TextBox to
Fields!FieldName
and fixed it with
Fields!FieldName.Value
With that said, and with the other answers posted as well, this error happens in different flavors. My issue was fixed after I had the field property "Value" included.