I am trying to get rid of
Warning CS0618: 'IDtsClipboardService' is obsolete: Use 'Microsoft.SqlServer.IntegrationServices.Designer.Model.IClipboardService' instead. I am trying to locate Microsoft.SqlServer.IntegrationServices.Designer.Model assembly to no avail. Anybody aware what installs it?
I have got SQL Server 2014 installed with Integration Services, SSDTS for VS2017 installed, up to date VS2017 and build tools version 15.
Any clues are warmly welcomed! Thanks
Miraculously I have found where Microsoft.SqlServer.IntegrationServices.Designer.Model.IClipboardService is!
According to Microsoft https://learn.microsoft.com/en-us/previous-versions/sql/sql-server-2012/ms211237(v%3Dsql.110) - it sits nowhere..
Using ILDASM.EXE from Dev CMD I started opening every assembly related to IntegrationServices and found out that the inteface I am after sits here:
Microsoft.SqlServer.IntegrationServices.Graph.dll
Related
I am attempting to install the Master Data Services Plugin for Excel, but can't get the install to actually process due to it saying the prerequisites are not installed:
I have made sure I have the right version (32 bit) to match my version of excel (2010), and have the full version of .net 4.5 installed. If I try to install the full version of .net 4.0, I am told that the newer (4.5) version already is installed.
Here are some links with similar issues, but no response:
Microsoft Answers; Microsoft Connect;
Has anyone else faced this issue and got around it?
So, this looks to be a simple fix. The installer needs to be run as administrator, but in order to do that you have to run it through the command prompt as administrator. After doing this, it installed ok.
I'm not sure why the installer didn't request elevated privileges, but I'm guessing it couldn't properly query the system to verify the necessary prerequisites were installed.
Hopefully this helps someone else in the future!
Running Windows 8.1 Pro x64 (upgraded from 8.0) with all updates installed. I'm trying to install SQL Server Management Studio 2012 using SQLManagementStudio_x64_ENU.exe. When the setup is initializing, I get this error:
ScenarioEngine.exe - Configuration parser error
-----------------------------------------------
Error parsing C:\Windows\Microsoft.NET\Framework64\v2.0.50727\config\machine.config
Parser returned error 0xC00CE556
I tried replacing machine.config with machine.config.default but with no success. Google has no more information regarding this, as far as I can see.
Has anybody seen this error before? How do you solve it?
It can be solved by installing dotnet framework 4.0 on your system.
Replacing machine.config with machine.config.default for both the 32-bit and 64-bit versions did the trick.
I am trying to install PETSc library on Windows 7 to be used with Visual Studio Express 2008, but I didn't succeed so far.
I installed cygwin (default installation) with python, make, diff.
Then I clicked on
VS2008Exp->Tools->VSCommand Prompt
I went to the Petsc directory
cygdrive/d/Workspace/PETSc/petsc-2.3.3-p13
From there I tried
an official suggestion
installing first the "Microsoft HPC Pack 2008 R2" and "Microsoft HPC Pack 2008 R2 SDK"
but I had an error "Unable to configure with given options" referring to
--with-mpi-include="/cygdrive/c/Program\ Files/Microsoft\ HPC\ Pack\ 2008\ SDK/Include"
--with-mpi-lib="/cygdrive/c/Program\ Files/Microsoft\ HPC\ Pack\ 2008\ SDK/Lib/amd64/msmpi.lib"
Afterwords I tried
config/config.py -with-cc="win32fe cl" --with-fc=0 --download-c-blas-lapack=1 --download-mpich=1
and now the error complains about the path for MPI (that I asked to be installed ..).
Can anybody help me?
Error you described here is about the MSMPI installation path. Since it has space chars configuration utility fails. So you have two options you may install MSMPI on a simple path like C:\MSMPI or use following syntax
--with-mpi-include='[my msmpi path]'
I am using this for MSMPI;
--with-mpi-include=/cygdrive/c/MSMPI/Inc/ --with-mpi-lib='[/cygdrive/c/MSMPI/Lib/amd64/msmpi.lib,/cygdrive/c/MSMPI/Lib/amd64/msmpifec.lib]'
For further info you may see this link
I just upgraded my machine to Silverlight version 4.0.60831.0 to see if it would help with some Memory leaking issues that I'm seeing.
Now when I try to use WinDbg and attempt to load the SOS.dll I realize that there is no SOS.dll for the .60831 version. I loaded the previous 4.0.60531.0 version, but when I attempt to dumpheap, I get the following error:
The version of SOS does not match the version of CLR you are debugging. Please
load the matching version of SOS for the version of CLR you are debugging.
CLR Version: 4.0.60831.0
SOS Version: 4.0.60531.0
I tried the .loadby command and that was unsuccessful as well
0:028> .loadby sos coreclr
The call to LoadLibrary(c:\Program Files (x86)\Microsoft Silverlight\4.0.60831.0\sos) failed, Win32 error 0n126
"The specified module could not be found."
Please check your debugger configuration and/or network access.
This makes sense because there is no SOS.dll file in that directory.
Is there something I missed somewhere?
Thanks in advance
sos.dll for Silverlight 4 comes with Silverlight 4 Developer Runtime.
http://go.microsoft.com/fwlink/?LinkID=146060
It will download Silverlight_Developer.exe which will contain sos.dll 4.0.60831.0
which is the corresponding developer runtime for Silverlight.
When installing DNN 04.09.02 upgrade (from DNN 4.8.4) I receive System.IndexOutOfRangeException: PermanentRedirect error and cannot install the upgrade. How do I get around this so I can install the upgrade?
This thread might help you:
It looks like you have to update it manually... steps are described there.
Also check this thread, might be due to AD if AD is used.
I've re-posted the following from the thread provided by kitsune. Source
First try the following in your browser. Replace "www.yourdomain.com" with your domain:
http://www.yourdomain.com/install/install.aspx?mode=install
If that doesn't work (which it didn't for me) then try the following steps (copied from Chris on that thread).
To manually run the SQL portion of the upgrade you'll need to run each upgrade script between your version and 4.9.2. I upgraded from 4.9.0 to 4.9.2 so I performed the following:
On the web server open the directory: \Providers\DataProviders\SqlDataProvider
Determine which files need to be run. Basically, all of the versions after your old version. In my case I needed to run the files 04.09.00.SqlDataProvider, 04.09.01.SqlDataProvider and 04.09.02.SqlDataProvider.
Open the SQL files in a text editor and replace "{databaseOwner}" (usually with "dbo.") and "{objectQualifier}" (usually with "", but sometimes "DNN4" or some other object prefix)
Run those SQL files in version order using SQL Management Studio.
Assuming those scripts ran without an error then the site should be ready to use.