I have an MVC3 C#.Net web app. I am using the Aspose library to read an Excel file using the WorkBook.LoadData() method. I am able to Load a file from my local machine when running in Visual Studio. I am able to load a file from the web server when running the web site. However, when running the website, I cannot load an Excel file from my local machine. I get the following error
"Unable to open specified Excel Workbook: Could not find a part of the path"
When I grab the path it says it can't fins and use my "Run" command...it finds the file. So, it must be a permissions issue. I am sure there is a simple fix but I don't know what it would be. Any Ideas?
As I suspected, it was a permissions issue. It was not an Aspose issue. I used the MS Interop library to run ImpersonateUser() using a service account that has access to the external machines
Related
I am very new for MS Add-in. I followed the instruction to build my first Excel React add-in (ttps://learn.microsoft.com/en-us/office/dev/add-ins/quickstarts/excel-quickstart-react). I used Yo generator. I only have Office 365 online. I used "npm run start:web". I didn't make any other changes, except I added the document in config. However, an error showed that "Cannot access manifest ulr at https://127.0.0.1:3000/manifest.xml. Please ensure the url is accessible." I don't know what's wrong. I also tried a Word add-in and same error. Hope somebody can help.
It seems the problem is with your local server if the file can't be accessed directly in any web browser. It is clearly visible the manifest file is not accessible. As soon as you make the file public and reachable in a web browser you may try sideloading your add-in in the Office application.
My VB.Net application is using a data bound MS Access database. This app is going to distributed to multiple co-workers so according to almost every article I've read, I need to include the database in my project so that it will get deployed (copied to the user's local directory) when the Setup.exe is run. When I publish the project, I see both the Database.employ and the DataSet.xsd.employ files in my Application Files that gets created. Yet when I run the Setup.exe I get an error message telling me that it can't find the file. I manually check the Data folder where it's looking and there is nothing in it. It seems that the files I need to get deployed are not getting so.
Everything I've read so far explains how to deploy the database but I haven't been able to find anything about this error I'm receiving or why the files aren't getting copied to the Data folder.
When using ClickOnce to deploy, in order for files to be deployed into the Data directory the Publish Status for the file should be set to Data File on the project properties Publish tab -> Application Files...
I am facing a few problems when trying to integrate the force.com ide with salesforce.com.
Currently i am using eclipse(4.22 Juno) and have installed the plugin Force.com IDE(2.9) and have a developers version in salesforce.com. I was able to successfully connect to salesforce without any errors thru force.com ide, by creating a new application with the name of the application that i have created in the web version.
Right now the application is created with the sub folders classes, triggers etc... but they are empty. I also tried setting the proxy in the connections of eclipse. But even that does not seem to work.
Does anybody have any idea what could be wrong.
Thanks--
Can you post the content of your package.xml file? It's kind of project definition, it contains info which files (objects, classes, pages, reports, profiles...) you want to download & push changes to.
Check http://wiki.developerforce.com/page/An_Introduction_to_Force.com_Metadata for example - have you skipped step similar to this?
we are working on a WPF application which we want to publish as a click once smart client application.
We are able to publish the application on local machine using Visual Studio 2012 and configured it in IIS.
Now we want to upload the published smart client installer to windows Azure Virtual Machine with Windows Server 2012 and IIS 8. We cannot upload the locally published components as the URL configuration in the manifest and deployment file is that of local server. We tried to edit the entries using text editor but once we do the editing the files become unused and it shows xml parsing error when we try to install from the location.
we tried to publish the application direct to the Virtual Machine but it shows an error as Front Page Extension is needed in IIS. We tried to find Front Page extension but couldn't find an version for IIS 8 in Windows Server 2012.
Can any one help us to publish the application in Azure Virtual Machine.
The problem you are having has nothing to do with Azure per se.
In the first case (of editing the XML files), you can do that but it's best to use MageUI to do the edit, because you can then re-sign the manifests. If you just edit the files, it messes up the security on them, and they will not work (as you have found). If you want to edit them with a text editor, you can do that, but then you must re-sign them (using mage); you can create a script to change the installation URL.
Or you can use MageUI. You need to do it in this order:
Open the application manifest in the versioned folder and then save it, re-signing it with your signing certificate.
Open the deployment manifest (yourapp.application) in the top deployment folder. Change the Start Folder to be the right Installation URL. Go to the "Application Reference" tab and re-select the application manifest in the versioned folder. (I know, it hasn't changed, but trust me, you have to do this.) Save this manifest and sign it with your signing certificate.
Copy the deployment manifest from the top folder to the versioned folder. It's always good to keep a copy, so you can go backwards a version if you need to.
NOW you can copy the files to your VM and they will work fine.
In the second case, the Front Page Extensions are required if you are using HTTP to publish the application, yet they are no longer available past about Windows Server 2008(?). So don't use HTTP. Use FTP. Set the publish file location using FTP, like ftp://myserver.mycompany.com/myfolder and set the Installation URL to the HTTP equivalent of it. Then publish it. It will put the files on your VM (assuming FTP is enabled on both sides), and the HTTP link should work.
By the way, you can also host your deployment in Azure blob storage. It is dirt cheap, and you can use something like Cerebrata Cloud Storage Studio or even write your own code to publish it (which I did). This article explains how to put the files out there, what the MIME types need to be, etc. If you do this, then it will work even if you need to replace your VM or redeploy it or the VM becomes unavailable for some reason.
here is a reference to Avkash Chauhan's blog post explaining in detail How to deploy ClickOnce Application using Windows Azure Storage in very simple steps?
http://blogs.msdn.com/b/avkashchauhan/archive/2011/05/09/how-to-deploy-clickonce-application-using-windows-azure-storage-in-very-simple-steps.aspx
He also gives an code example of a windows form (using Wpf) that he shows how to deploy on azure using one click deployment.
hope this helps
I've found a very small sample showing Silverlight SQL connection (http://www.codeproject.com/KB/silverlight/CntDbSlght.aspx), I've tested it and it works fine on local system, also I've changed its connection string so that it shows data from my remote database, but when I upload files to my host, I cannot see any SQL data, it seems that something is broken, how should I configure my web.config?
What are CrossDomain.XML and ClientAccessPolicy.XML files? should I upload them? If so, where should they be? How should I bind my service? what am I doing wrong? I click on VS2010 publish (in build menu) and select file system, then I upload all files existing in this folder, I use C#.
If you are trying to access an external Silverlight web service from your local dev environment you certainly need a ClientAccessPolicy.XML file on the website. This tells the site services where requests can come from (normally only from the same site the SL app was run from).
Your ClientAccessPolicy.XML file needs to go into the actual root of your website i.e. 'mydomain.com/ClientAccessPolicy.XML.
*Note: You do not also need a CrossDomain.XML if you have ClientAccessPolicy (which is the SL specific one). CrossDomain.xml is an older flash compatibility file that sometimes exists on sites.