I have written on premise share point code (to insert the values into the sharepoint list) in with the sharepoint server machine,Its executing with in the server am able to insert the data into the list, same i made as a EXE file.
Same EXE file am running in my local machine(out side the server machine), It not working showing as mentioned below error.
"Could not load file or assembly 'Microsoft.SharePoint.Library, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified"
Can any body will help on this.
Thanks,
Nagendra.
You can't run it local it needs Sharepoint so you have to run this on Sharepoint server itself. You can work with websservices to do this "remote".
https://learn.microsoft.com/en-us/previous-versions/office/developer/sharepoint-2010/ms458094(v%3Doffice.14)
When I want to edit connection properties on SSAS for some tabular database (Impersonalisation Info: ImpersonateServiceAccount) when I click OK I got following error:
Could not load file or assembly 'Microsoft.SqlServer.Configuration.SString, Version=14.0.0.0, Culture=neutral,
PublicKeyToken='numberhere'' or one of its dependencies. The system cannot find the file specified
I don't now what is the problem. I tried to google but I didn't find anything about this error. From my solution in VS I can deploy tabular model but it seems that data are not processed.
-----------------IMAGE OF ERROR
I updated my SSMS to latest version and now everything is OK.
I did an application in VS2015 and Crystal Report, I can run it in the development machine (32bits) with no problem, I can load the forms where is CrystalReportViewer and print, all works fine but when I install it in another PC (32bits) and I try to load the form that have the CrystalReportViewer I get: "System.IO.FileLoadException: Could not load file or assembly 'log4net, Version=1.2.10.0 , Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies"
This is all I did:
I confirmed that log4net.dll exist in my debug folder
I saw the version (1.2.13.0) and change it for 1.2.10.0
I tested with a lot of configurations in app.config
I tried this official wiki:
https://wiki.scn.sap.com/wiki/display/BOBJ/Using+Crystal+Reports+for+Visual+Studio+2010+Merge+Modules+(MSM)+to+create+a+Setup+project
(I can´t find any CRRuntime_13_x.msm file)
But the error still showing up
Please can you help me?
I found a quick solution installing CRRuntime_32bit_13_0_16.msi in the new PC, it is not a good solution and I must say that from now I prefer to do the reports with VB Net entirely.
I wrote a simple VB.NET application which works fine on the development machine.
However on another machine, even though the .NET Framework is installed, it crashes on startup with System.InvalidOperationException.
There seems to be a problem with it finding the Visual Basic assemblies.
Here is one of the fails (I replaced sensitive information with three dots):
*** Assembly Binder Log Entry (16/06/2013 # 15:45:12) ***
The operation failed.
Bind result: hr = 0x80070002. The system cannot find the file specified.
Assembly manager loaded from: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Running under executable C:\Users\....
--- A detailed error log follows.
=== Pre-bind state information ===
LOG: User = ...
LOG: DisplayName = Microsoft.VisualBasic.PowerPacks.Vs, Version=10.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a
(Fully-specified)
LOG: Appbase = file:///C:/Users/......
LOG: Initial PrivatePath = NULL
LOG: Dynamic Base = NULL
LOG: Cache Base = NULL
LOG: AppName = MSystemAdmin.exe
Calling assembly : MSystemAdmin, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null.
===
LOG: This bind starts in default load context.
LOG: No application configuration file found.
LOG: Using host configuration file:
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.
LOG: Post-policy reference: Microsoft.VisualBasic.PowerPacks.Vs, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
LOG: GAC Lookup was unsuccessful.
LOG: Attempting download of new URL file:///C:/.../Desktop/Microsoft.VisualBasic.PowerPacks.Vs.DLL.
LOG: Attempting download of new URL file:///C:/.../Desktop/Microsoft.VisualBasic.PowerPacks.Vs/Microsoft.VisualBasic.PowerPacks.Vs.DLL.
LOG: Attempting download of new URL file:///C:/.../Desktop/Microsoft.VisualBasic.PowerPacks.Vs.EXE.
LOG: Attempting download of new URL file:///C:/.../Desktop/Microsoft.VisualBasic.PowerPacks.Vs/Microsoft.VisualBasic.PowerPacks.Vs.EXE.
LOG: All probing URLs attempted and failed.
It isn't that clear why PowerPacks is missing, the .NET 4 Client Profile could be an issue. There have been multiple versions of PowerPacks around and the version numbering got to be a mess. On my machine, that same version is reported as v2.0.50727, even though it is stored in the GAC as version 10.0
Best thing to do is to go back to your project. Click the "Show All Files" icon on the toolbar in the Solution Explorer window. That now shows the References node. Expand it and select the PowerPacks reference. In the Properties window, change the Copy Local property to True.
Rebuild and your build directory now will have a copy of the DLL. Copy it along with the EXE onto the target machine.
Here is the URL to download Microsoft Visual Basic Power Packs 10.0
http://go.microsoft.com/fwlink/?LinkID=145727&clcid=0x804
Apparently, it seems to be a problem with the "PowerPacks"; these are additional controls to the ones given by default in Visual Studio (in the form design part, under "Toolbox"). If you install the required package on the target computer, everything should be fine.
I had this problem in the past and my recommendation is not relying on these elements: they include nice-to-have features (in my case, it was an elliptic shape) but might be replaced with a bit of work and simpler objects. If you want to sell your program to a more or less wide audience, relying on this might become a problem: this package is not installed by default on virtually any computer and thus you would have to ask your clients to go ahead with the installation. Locating these specific controls is straightforward: on the "Toolbox" they should be listed under "PowerPacks" or similar.
After reading the Hans Passant's comment, I do recall that a .dll file has to be put in the same directory than the executable, but I am under the impression that the PowerPacks package from the provided link has to be installed anyway (at least, on computers not having Visual Studio).
I was upgrading Visual Studio from Visual Studio 2013 to Visual Studio 2015 on a new Windows 10 machine. In doing so I copied my Projects folder from a Windows 7 machine to the same path on the Windows 10 machine.
When I opened a project which used MS.VB.PowerPacks.VS I was informed the file could not be found. I downloaded the newest install for MS.VB.PowerPacks.VS Version 12.0.0.0. Visual Studio 2015 blanked out my form pages which used the PrintForm and informed me:
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualBasic.PowerPacks.VS, Version 10.0.0.0.
I changed the reference to vcersion 12.0.0.0, but it was still not recognized.
My fix: I copied the the C:\Program Files(x86)\Reference Assemblies\Microsoft\VBPowerPacks\v10.0 folder from my Windows 7 machine to my Windows 10 machine, and then removed the v12.0.0.0 reference and added the v10.0.0.0 reference to the program. I then exited the project and opened it again, and all was well, the forms were displayed in their original beauty.
we made one application to read the pdf file and write in Excel.We used iTextSharp.dll.
Application works fine here with windows XP as well as WIndows7.We created this using applicaiton in VB.net in VS2008 version.we have Adobe ReaderX.
But for our customer its not working and it shows error as Unhandled Exception and shows error as
filename.pdf not found as file or resource.
Whats reason for this error message.Customer PC is Windows7 and AdobeReaderX is installed there.
Pls kindly help me.
Random guess? Some directory or filename information is hard-coded into your application. Or the customer is trying to open an incompatible file. Like trying to open a text file with the paint application.