I have a spotfire dashboard that is published to a development and a production server. I have an updated version that was created in the development server and need to open it to be able to publish it in the production server. However, when I try and open this version in the production server via portable spotfire it gets most of the way through loading and then produces this error:
`InvalidOperationException at Spotfire.Dxp.Data:
Data should have been pushed. (HRESULT: 80131509)
Stack Trace:
...`
And I now get the same error when opening previous development versions in production that opened fine before. Others can open these .dxp files in both servers without issue.
Does anyone know what is causing this issue?
I have tried deleting portable spotfire and redownloading twice, however the same error is produced.
---- SOLVED ----
I had to upgrade my build version of spotfire analyst and now it works.
Related
I have used the TFS to Excel functionality for several years. Last Friday it suddenly stopped working. I get the error TF84021 Can't create the work item list. If I try again it will spin and then bring up the same error. This usually happens 2 or 3 times then Excel will open as a read-only which removes the link to TFS. I have tried to configure the server connection and get error TF400324. Services not available from server. The underlying connection was closed.
This is impacting a small group of people with the same job function (Scrum Masters and BAs). Management and developers can use it just fine.
My help desk remoted into my machine and tried it with his creds and it didn't work. We ran it through Fiddler and the log showed an error but it didn't have any information.
I am using TFS2017 Version 15.117.27414.0 which I believe is update 3, Visual Studio 2017 and Excel 2016. As well as ADO in the cloud (not on prem).
I have gone into Excel to verify the com add-in is present and checked. I have reinstalled the add-in just in case it was corrupted. I have tried to remove my TFS server and re-add although I knew that couldn't be the problem as it occurs on ADO as well.
I'm at a loss. Any thoughts as to what to try next?
So I'm getting a blue screen of death whenever I have "npm start" running for a reactjs app. It's an intermittent crash, i.e. it doesn't happen every time I run it nor are there any exact steps to duplicate the crash, but I'll try to explain below under what circumstances it happens.
Create a reactjs app using create-react-app npm module.
Start the app using npm start. Chrome window opens, webpack is listening to changes I make to the source files.
Change any source file, and save it. NPM compiles it, Chrome page refreshes, and I can see my changes.
The above things work fine as expected "normally", but once in a while, right after I save a file, the system crashes with a BSOD saying DRIVER_IRQL_NOT_EQUAL_TO_OR_GREATER_THAN (NETIO.SYS) There is no definite "step" or action other than saving the file, or refreshing Chrome that would cause this to happen, and it also doesn't happen every single time.
Here are the steps I took to find out/eliminate the root cause of this issue:
Disabled by AV (Symantec Endpoint Protection).
Use a different browser (Mozilla, hell, even IE).
Changed the system (used a different laptop, although the same type - Microsoft Surface on Windows 10)
Updated all drivers, etc. (Verified by my organization admins)
Closing all other programs, etc. that might potentially be interfering (Atom IDE, Eclipse, etc.)
The necessary conditions for the crash to happen are:
npm start must be running (webpack server on localhost:3000)
A browser window must be open connected to localhost:3000 (if no browser is connected, it doesn't crash even if you change and save the file 200 times - I checked). Also, doesn't matter which browser (Checked with Mozilla/Edge/Chrome)
I believe the crash happens when NPM is recompiling the files and serving it to the browser (asking it to refresh using some websockets), but I'm not an expert on NodeJS/NPM so I'm not sure.
I've been stuck on this issue for more than 2 weeks now. Any help would be really appreciated. Kindly let me know if more information is needed.
The issue was with Symantec DLP (Data Loss Prevention) that was also installed on all our systems. The issue resolved itself after the admins added application exceptions for Nodejs, NPM, my reactjs project workspace paths.
Just posting this so that in case someone has a similar issue they can try this or remove Symantec DLP altogether.
I'm working in a project to load data from sqls erver into an excel file.
When working in my local machine, the package I'm working on is working perfectly.
However when I do a deployment I'm getting the error : failed validation and returned validation status "vs_neednewmetadata"
I'm using SSIS 2012 and Excel 2016
Any help will be appreciated
Thank you
This issues is always very complex to figure out.
Still when you have like this issue try to find if your sources or destinations have changed but not your deployed package. Indeed, when you update your connection tables DB or files please be sure that you deploy again
Also, you have to be carefull when you work with script component do not copy/past this component from others packages otherwise you will get the metadata error and you cannot resolve it.
In my case, the issue I had was related to destination Excel file. I have changed this file like erasing some lines, but I do not change its structure and I missed to copie this one in the server.
That mean event the changes are minor and do not affect the structure of the destination file, you have to update your server version file with the one you use in dev.
Crystal report is working fine in local. But when i deployed it in IIS, its displaying a blank page. I have tried the following one. But this is not working for me.
"Downloading and installing runtime for Crystal Reports 13 for Visual Studio 2010. (You might want to skip this step if you already did this before and your application is working locally).
"Once the runtime is installed. Crystal Reports will install the required support files in the location of your local computer: C:\inetpub\wwwroot\aspnet_client\system_web\4_0_30319\crystalreportviewers13
Copy the entire Crystal Report Support folder C:\inetpub\wwwroot\aspnet_client\system_web\4_0_30319\crystalreportviewers13 to your Website's SITE_ROOT\aspnet_client\system_web\4_0_30319 folder.
4) If you do not have a \aspnet_client\system_web\4_0_30319 folders in your website's root. Please create them manually and then copy the crystalreportviewers13 into it."
Please give me a solution.
Thanks in advance.
In addition to that make sure your report files are being published when you publish your project with the option 'Only files needed to run this application'. This resource might help
I have faced the same problem and resolved it by following these these steps:
At first, you have to debug your application javascript, let us say on Chrome (I prefer chrome debugging tool). It will show you exactly what errors your crystal report is generating.
In my case, my Jquery.js library had to be included before bootstrap.js library like this:
<script src="js/jquery-2.1.4.min.js"></script>
<script src="js/bootstrap.min.js"></script>
<script src="js/npm.js"></script>
Secondly, the report was unable to connect to my ODBC driver to load data, that was because of ODBC permission problem. Again I had to fix this one.
These errors were all shown in the debugging console, so concentrate on it.
I have a 2013 SharePoint hosted app. I made some changes and went through the update process (changed the app version, kept the id the same, uploaded the package to the app catalog and updated the app immediately through the site contents of the site collection). Everything worked fine. However, when I go through the same process again with an even higher version, the app says that it's updating and after completion everything is the same. In fact, the app even shows that a new version is available. If I click "Get It", it says that it's updating for about 5 to 10 minutes and then nothing changes, same old app, same old files, same old version number, still says that a newer version is available. I get no error messages.
Any help or pointers are greatly appreciated, of course. Thank you.
UPDATE: In Central Admin. I started to monitor the app and found that there were failed upgrades with an error message of "There was a problem accessing the file system on the server."