I have just recently started using SSIS and it's been a great ride so far. I get an error message when attempting to add an existing package. My guess is that packages that were created on an original computer cannot be globally accessed even if you have the .dtsx file?
Below, is a link of the image of the error I am getting.
http://imgur.com/B95pVg5
Please give me any help!
Related
I wanted to learn SQL to create my own database to serve for my future project but things seem not to be smooth as expected from the first step. I struggled with installing the SQL Server for days with different times of uninstalling and reinstalling. The installation Progress has just constantly thrown me warning window with the content was:
The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
I believed that the old SQL Server was completely uninstalled by deleting anything related thing include files in Program Files, Program Files(x86), and its registry.
I searched and followed many threads with the same issue on some forums but still got no result.
After skipping that warning by canceling it, the installation completed with failure shown in the picture below. Your help would be much appreciated.
I’m fairly new to Verdaccio. Been familiar with the tool for quite some time, but this is my first time trying to use it. I’ve installed it locally for the purpose of trying to figure out the right syntax for handling versioning, tagging and publishing a shared component library for work, but I’m having trouble getting this package published to my locally running instance of Verdaccio, and I’m struggling to understand why the publish command is failing. Was hoping someone here might be able to help.
First off, I should say that I have it installed and running locally, I can browse to http://localhost:7890 and see the Verdaccio web UI, and it says that I have “No package published yet.” That makes sense, because I haven’t been able to successfully publish anything yet. I’ve created a user with the npm adduser —registry http://localhost:7890 command, and then after that I ran the following command to attempt to publish to it: npm publish —access public —registry http://localhost:7890. When I run this command, I get the following error: “EPUBLISHCONFLICT … Cannot publish over existing version.”
Now, I can in fact see, when I look in .local/share/verdaccio/storage that there is a folder for the scope that I published with, and in that folder, there is a folder for the package that I apparently published, and it only has a package.json file in it. I’ve attempted to wipe this all clean, reinstall Verdaccio, etc, etc, nothing seems to fix the issue. I can’t seem to make this package go away, OR to get it to display in the UI either. After publishing (unsuccessfully), and despite the face that it says this version of the package exists, I still see nothing in the UI. It still just says “No package published yet”, which I still don’t really understand.
Any ideas would be appreciated. This has me pretty stumped. Thanks.
Add your package.json name as npm registry (it needs the same one you published the last time).
I was getting this issue:
The following works for me:
npm publish --registry=http://yourhost:yourport
We have a task where we need to automatically convert an excel file to a csv to prep it for loading into a SQL database. The developers built this process into a SSIS package. For the conversion, they initially tried to have a task in the SSIS package execute a VBscript to convert the file. When they were running this on there local machines, this worked correctly. When they ran the package manually through VS on the server, it ran correctly. When they ran the package manually via the Integration Catalog it ran correctly. We did this both as our accounts and as the service account and got the same results. However, when we scheduled it as a job it would hang on the part of the process that executed the VBScript. No errors, it would just hang until you killed the job.
The job was executing as the service account which has full admin access on the server, explicit full access to the share where the files are stored and converted (which is on the same server) and full admin access to SQL. The job owner is set to sa which uses the service account. And all the job does is execute the package from the integration catalog which works if you run it independently of a job. When we compared the ssisdb execution report for the manual run in the integration catalog using the service account to the job run they looked the same except the job hung on the conversion task and the other did not.
After spending some time trying to figure this out, the developers tried a different solution. They changed the conversion script from using VBScript to using C#. They ran the package from there local machine and once again the package worked. This time when they ran it manually on the server it failed. When we ran it from the integration catalog it failed and when we ran it from a job it failed.
The error we keep getting is "Create CSV file: Error: Exception has been thrown by the target of an invocation" After spending several hours looking into this error nothing suggested seems to be working.
We also tried these same solutions on a newly built server to make sure we weren't dealing with an odd configuration setting that could have been changed (It is a Dev server) and it still failed there.
At this point, we are pretty lost at what is happening. The first solution worked, but for some reason would never work as a job. The 2nd solution works everywhere except when ran on the server.
We are looking at some other solutions to try to get around this. The next thing may be trying to using powershell to convert the file, but not sure if that will bring us back to the same issue. Any suggestion you guys have will be greatly appreciated
Also, we are using SQL Server 2012 dev edition, VS 2012 pro, Windows Server 2012 R2
This might be because of a bug that Excel has when trying to run jobs (that use Excel) and no user is logged on a specific machine. This might affect also the excel library. The solution is to create the following 2 folders:
C:\Windows\SysWOW64\config\systemprofile\Desktop
C:\Windows\System32\config\systemprofile\Desktop
and then restart the machine. :)
(Edited to show that a restart is needed. thanks for Dustin for checking this)
How do I save/commit/push such that the network has the latest version?
I have never used version control before.
I am new to Visual Studio 2015 (I mainly used VS 2005).
I am a VB.net developer.
I am running Windows 10 and have a Windows 2008R2 Server (not AD).
I need to keep my code private and local (no cloud).
I will eventually need to have up to 3 developers collaborate with my code.
I am not a fan of using the command line unless I absolutely have to. (GUI for me).
I feel that version control should be integrated with Visual Studio.
I think the code should be stored on the server and a local (working) copy on my machine.
I believe I would benefit from using Git. (Not GitHub).
I may also check out Gogs or Bonobo. I hate Java so not (Gitblit)
I Installed Git on my server - although I'm not sure I needed to do this.
I have installed it on my local machine.
I mapped a shared directory (v:)
I have attempted (successfully - I think) to copy my code into a repository and make a few commits.
I thought I was having some success using the Visual Studio 2015 - Built-It / Extension
However, after attempting to use/create a local clone eg C:\Users\My User Name\Source\Repos
Making some changes, Commit All, Then attempting to Push I get the following Error:
"Failed to push to the remote repository. See the Output window for more details."
Output window says:
"Error encountered while pushing to the remote repository: Local push doesn't (yet) support pushing to non-bare repos."
I've read but not sure how to apply to VS Git push error '[remote rejected] master -> master (branch is currently checked out)'
PS. Because of my specific set-up/needs I’m struggling to find help. Any tutorial recommendations are welcome.
Sorry if this is too verbose.
I had many problems trying to solve this.
One of which was attempting to use the Network Drive as the Master when I Believe the local is the Master.
I am sure that I am to much of a noob with this (even now), however just because it may help someone try bonobo git server. This allowed me to create a LAN based Git repository on windows that I seem to have got to work.
I still think that my problem was trying to find good help that was relevant to what I was trying to do was lacking (or I was looking in the wrong places).
A colleague of mine is having problems building a Sql Server Database Project in visual-studio-2013. He shared his screen with me, hoping I could help him solve the following issues:
In case you can't see the image, there's a build error stating that "The comparison cannot continue until the build error is resolved" and a build warning that goes "Refactoring operations exist in the source, but will not be shown in the comparison.".
Not being too familiar with Sql Server DB projects, I tried searching the exact same messages on Google... only to find absolutely nothing.
Can anyone help? What does these messages means, why are they appearing and how can we expect to successfully build the project?
I had this same issue but it went away when I followed the instructions of the accepted answer of this post: VS2013 Database Project fails to build.
It turns out that the project was not building. The error described in this post was misleading and was probably only a symptom of the real error which was that the project could no build.
In case that link is no longer available, the solution was to install the Microsoft SQL Server Data Tools. You can do that by downloading the install package from here.