I want to use Excel Power Query to import JSON data from web and transform the data afterwards. I have 2 versions of JSON Data, one development version and one live version. Both versions had no problem prior to last week and could connect without any issues.
Last week the live version stopped working and couldnt connect through Excel or PowerBI anymore. Curiously, nothing has been changed in both versions that could've contributed to this error happening, there were absolutely no hands in either versions during that time frame.
This is the dev connection string in PowerQuery thats working without problems.
Source=
Json.Document(Web.Contents("https://www.dev.com/dummy/YXC/JSONDATA")),
Now when I try to change it to this
Source=
Json.Document(Web.Contents("https://www.live.com/dummy/YXC/JSONDATA")),
the error message: "[DataFormatError] We found extra characters at the end of JSON input." arises
After this and some troubleshooting, I opened a new empty Excel file to put the link directly into the "from Web" tab. The connection fails and I get up to 2 Errors.
"[DataFormatError] We found extra characters at the end of JSON input."
"Details: The Ressource under "https://www.live.com/dummy/YXC/JSONDATA" cant be opened through Web.Page since its apparently no website"
Before the website can be openend one must have an authorized microsoft organisation account.
In Chrome the data shows up without any issues and there are no authorization issues, also when I download the JSON data and import it through a file directly there are no issues either. Same error occurs with other accounts.
Since it says DataFormatError, I started looking into the JSON Data. The JSON Data doesnt have any whitespace and is identical with the working dev version.
Does anybody encountered this or has a clue on how to fix this?
Related
I have created an .ade from an adp without problems.
When I try to open the .ade file I get the following error:
"Requested type library or wizard is not a VBA project"
The following files are my project:
Lib.ade (Version 1): external library
MainProgram.ade: compiled and made ade when the reference is to Version 1 and it works fine.
I sent these two file to client station without any problems but when I did some new changes and make new Lib.ade (Version 2) and sent to client environment, MainProgram (Version 1) gave the mentioned error.
Thanks for any help.
I got the same error message and it turned out to be a "Phantom Breakpoint" issue. See my posting here for more information:
https://stackoverflow.com/a/56565372/5795793
After several debug sessions in the original file (an ACCDB file in my case), it started breaking to a code line where I had previously, mistakenly left a breakpoint. Even though no breakpoint appeared, I had to duplicate the sub and comment out the original sub for it to work.
Sounds like there might be a phantom breakpoint in Version 2 of the Lib.ade. If so, copying the code elsewhere and commenting out the old code can work. Decompililng may also fix it.
Perhaps my experiences with the same problem will help someone.
Error "Requested type library or wizard is not a VBA project" occurred only in ACCDE, when trying to switch between tabs in level 2 navigation form. Explored all the options with references to library files, decompiling and recompiling, creating new DB and suppressing error message.
The only thing that worked for me is:
in ACCDB Remove all VBA code from the navigation form. Event Property Sheet sheet should be cleared of any events.
In the Other Property Sheet set "Has Module" to NO. (this should anyway delete the all code in the Navigation Form mentioned in step 1, so perhaps step 1 is not required, but better safe than sorry)
Save, Compact&Repair, Compile, Save as ACCDE
Enjoy.
I'm trying to transfer a ton of data from an old sharepoint platform through access to sharepoint 365.
When I do this, I get an error like this:
Picture of access
As far as I can tell, this means that theres either a server problem, or something was misspelled.
I can transfer several other views without any problems, so im hoping that someone out there can shed some light on this.
Cause of this problem can be in names of attachments. Just now I had the same problem importing the SP2007 list to Access and I find out, that I can import everything except two records with attachment, which name contained + symbol. I had to delete the attachment, then the import was OK.
Bigger problem was to find problematic records - I had to make special view filtered by date of last change and then tryied importing records from different time scopes, until I identified records causing the trouble.
I get errors on build stating 'The System cannot find the file specified' for each of the 3 metadata files 'CSDL, MSDL, SSDL'
Able to generate model from DB fine, connection string fine. Reinstalled the correct connector just fine and MYSQL as a provider appears fine in VS2012.
The 'Metadata Artifact Processing' propery on the model is set to 'Embed in Output Assembly' as instructed.
Out of ideas and hours to keep hunting, would really appreciate a fix here.
This was happening as I had a build script that deleted these metadata files as a result.
Sorry, my bad.
During packaging the Windows Store application, I get an unspecified error [APPX1204]:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\AppxPackage\Microsoft.AppXPackage.Targets(1139,9): error APPX1204: Failed to sign 'D:\Projects\VS2012\Stroik\Stroik\AppPackages\Stroik_1.0.0.11_AnyCPU_Test\Stroik_1.0.0.11_AnyCPU.appx'. SignTool Error: An unexpected internal error has occurred.
Build output refers to the part of a file generated by VS2012:
<SignAppxPackage AppxPackageToSign="#(FinalAppxPackageItem)"
CertificateThumbprint="$(PackageCertificateThumbprint)"
CertificateFile="$(PackageCertificateKeyFile)"
HashUri="$(_HashUri)"
EnableSigningChecks="$(EnableSigningChecks)"
>
<Output TaskParameter="ResolvedThumbprint" PropertyName="ResolvedThumbPrint"/>
<Output TaskParameter="AppxPackagePublicKeyFile" PropertyName="AppxPackagePublicKeyFile" />
</SignAppxPackage>
Yesterday packaging proceeded successfully. Today I added aditional logic to my app and changed some data in manifest. Since then I'm reciving presented error. I tried to regenerate Certificate in Packaging menu, delete Store/Temporary Keys (then regenerate), ... much more but nothing helps.
Now I have no idea how to handle it. Furthermore packaging a new project (as it is provided by vs2012) results in the same error.
Have you got any suggestions how to solve it.
If it helps anyone else, I was trying to make the build on a network share (virtualizing windows). Creating it on the Windows partition solved the issue.
I was developing on a Virtual Machine in VirtualBox and tryed to publish to the shared folder.
Change the output folder to a local folder on the virtual maschine solved it.
Granted this is older - see if you can try it with a different live id
You could also try to generate a new app, and diff the manifests between the apps.
Now according to:
http://social.msdn.microsoft.com/Forums/en-US/toolsforwinapps/thread/f25939fb-c48c-4bd0-938e-6a0afbd2dca0/
you may want to sign out, use IE 'in safe private browsing' and create a new one.
Also ensure that IE is set in "Browsing History->Settings" to get a new version of the page every time.
Login with the new one and give it a try.
I'm not sure if this error is related here or not, but it's a starting point based on the prior feedback on the above post.
This japanese site lists the same error code and seems to have the same resolution as well
http://coelacanth.heteml.jp/blog/windows-8signtool-error-an-unexpected-internal-error-has-occurred/
Its worth a shot, but I'll admit on this one not being 100% sure, just trying to help out : )
I have started a new Lightswitch project using a SQL database that was created with Lightswitch. When I publish and install the new Desktop project everything goes fine with no errors in publishing, installing or loading the new application. The first and only screen appears. I can click on different records and the data shows up and I can edit the data. However, if I use the list search function all of the fields get Red x'd.
The original application works the way it supposed to work.
I have tried with and without IIS: Published with (local) and (IIS) and get the same results with both methods.
The connecection string options for the new app are not the same as the original in that System Admin and Sytem user connecection strings are not offered so it is difficult to know if I replicating a working setup or not.
In Mananagement Studio I am awash in security, permissions, roles, and login selecitons. It seems clear that this is permission level problem but I have no idea on where to start trouble shooting.
see:
Diagnosing Problems in a Deployed 3-Tier LightSwitch Application
http://blogs.msdn.com/b/lightswitch/archive/2011/09/20/diagnosing-problems-in-a-deployed-lightswitch-application-eric-erhardt.aspx
How many string properties are in the table that you're displaying? Is there a large number of properties that don't need to be included in the search?
This forum post discusses the same issue as you're encountering: Search returns error "Unable to load data" with a Red X
Have you checked your connection string setup? I do have those issues back when I was using SQL Express on development and using SQL Server Enterprise as my target database server.