"Could not copy file" error preventing build in VB 2019 - vb.net

I'm getting an error, "Could not copy the file [file name in app folder] because it was not found." This is giving me a build error, not a runtime error. There is no path or file given. I am using filecopy commands, but not even on the main form. I have searched the entire solution for "FileCopy," and the only 2 are in a form not yet loaded, within a try-catch-end try. How can I find the source of this error?

Related

SonarQube failing on files filled only with comments

I'm trying to analyze the code of a vb application in TFS.
I'm using SonarQube, with the TFS extension.
My issue is that, whenever SonarQube encounters a file which only has comments in it, it will fail with this message :
ERROR: Error during SonarQube Scanner execution
ERROR: Unable to register token in file the [filepath].vb
ERROR: Caused by: 21 is not a valid line offset for pointer. File [filepath].vb has 20 character(s) at line 1
All the files have the .vb extension.
I would just remove these useless files from the repository but the code is not mine and there are over 15K files.
Is there a way to avoid crashing on this type of files ?
Or avoid analysing files filled with comments and empty lines ?

Excel VBA CreateObject: Run-time error '432': File name or class not found during Automation operation

How do I fix the error "Run-time error '432': File name or class not found during Automation operation" I get when calling "CreateObject("Scripting.FileSystemObject")" in Excel VBA?
I have a spreadsheet with a macro that works on two other computers and used to work on my computer before I factory restored it and reinstalled Office.
I am on Windows 7 64-bit, running Office Home and Student 2010.
I traced the error down and created a new spreadsheet with a macro that runs a single line:
Set objFSO = CreateObject("Scripting.FileSystemObject")
This macro runs fine on 2 other computers, so there's something in my PC environment that's screwing me up. I get the error:
Run-time error '432': File name or class name not found during
Automation operation
I've tried repairing the Office installation and completely uninstalling and reinstalling Office.
From what I can find on the internet, I might need a reference to "Microsoft Scripting Runtime". I believe this is the file scrrun.dll.
When I go to add this reference to my project, it shows me that the location of "Microsoft Scripting Runtime" is "C:\Users\\Documents". You can see this in the attached image full of errors.
That doesn't seem like the correct location, and there are no dlls there.
If I check that reference to include it and hit OK, I get the error:
Error in loading DLL
scrrun.dll is found in "C:\Windows\System32"
I tried registering the dll and it worked fine. Unregistering gives me the error:
The module "scrrun.dll was loaded but the call to DLLUnregisterServer
failed with error code 0x800300002.
I made sure the Administrators group owns that file in case it was a permissions issue. I also tried unregistering while running in Safe Mode.
I may be off on a total tangent looking at the "Microsoft Scripting Runtime" reference and/or scrrun.dll.
Thanks for any advice!
It works with me as below. Hope it helps
- I find scrrun.dll in C:\Windows\SysWOW64. I register it in this location successfully
- Recheck in VBA Reference, it shows location of Microsoft Scripting Runtime as C:\Windows\SysWOW64\scrrun.dll
Then i have no below error anymore
"Run-time error '432': File name or class not found during Automation operation" I get when calling "CreateObject("Scripting.FileSystemObject")" in Excel VBA"

unable to install Visual Basic ()

I am trying to install Visual Basic 6 Enterprise Edition on Windows 8 Server (64-bit) , but I got the errors, saying "Setup could not remove the file: C:\Windows\system32\DBNMPNTW.DLL". So, I used "LockHunter" to lock the file and continue, but it does not proceed (see attached). So, I chose "ignore" button to proceed(assumed that the file is the only problem). However, I got the following two files that give me the error, saying "Setup could not remove the file"
(1). C:\Windows\system32\DBNMPNTW.DLL
(2). C:\Program Files(x86)\Common Files\system\oledb\SQLOLEDB.DLL
Setup could not remove the file http://www.dreamincode.net/forums/topic/96146-javasigndll-error/
So, I clicked "ignored" for both errors, and then I got different error type, saying "..was unable to register itself in the system registry."(see attached). See below for the lists of the file names.
So, I copy fresh dll files from online, and try to register all dll files(found on this site), and I got the error below (see pic).
Thanks in advance,

SmartCard reader: Building libccid

I am trying to build libccid, pcsclite and libusb together on a fedora 20. I have been able to compile and build libusb and pcsclite. However, while building libccid, I get the following error in the build log:
copy the src/92_pcscd_ccid.rules file in udev directory (/etc/udev/rules.d/)
I did copy the file to the specified location and then ran the makefile. However, I have not had any success.
Did anyone come across this error message?
Thanks
When you check the libccid source code you will find out that it is not an error message. It is just an informational message that you should manually copy file 92_pcscd_ccid.rules from src directory to /etc/udev/rules.d/ directory.

The type library importer encountered an error during type verification

I am writing a C# application which has several COM references. When I attempt to build it I get the following error for some of them:
c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(1418,9): error MSB3303: Could not resolve COM reference "70850f66-869f-44a0-88e7-b0460a7e3bf3" version 0.1. The type library importer encountered an error during type verification. Try importing without class members.
The application is still built and runs successfully.
What does this error message mean, and how can I fix it?
By running TlbImp myself on the offending files I was able to determine the cause of the error. TlbImp is located somewhere like:
C:\Program Files\Microsoft SDKs\Windows\v6.1\TlbImp.exe
I ran it against the TLB file that was generated when I compiled my COM DLL, and I received a more detailed error message than what Visual Studio had told me.
Run command line from which you execute tblimp tool in Admin mode - it helped me