.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Use Visual SourceSafe 2005 via COM interface on Windows 2003 Server 64-bit

Posted By:      Posted Date: October 03, 2010    Points: 0   Category :.NET Framework


I'm trying to use Microsoft SourceSafe 2005 COM (published via ssapi.dll) in my 64-bit application running on Windows 2003 Server 64-bit. The attempt to get instance of the interface fails with "Class not registered" (REGDB_E_CLASSNOTREG) error. As many posts in other forums and MSDN documentation explain it is happening because of separation between 64-bit and 32-bit implementations. In other words the process in 64-bit doesn't see registry entries made for 32-bit applications. (I checked and see the registry entry under $/HKLM/SOFTWARE/Classes/Wow6432Nodes/CLSID/{Class ID}). However, I need my app. to use SourceSafe services.

Please, advise how I can invoke COM interface implemented in 32-bit from my 64-bit application. Since the 32-bit application isn't mine I can't recompile it with 64-bit... :(


Thank you.

Regards, Leo

View Complete Post

More Related Resource Links

Does SQL 2005 Enterprise Edition come preloaded on Windows Server 2003 Virtual Server.

Does SQL 2005 Enterprise Edition come preloaded on  Windows Server 2003 Virtual Server. I found this link http://www.microsoft.com/downloads/details.aspx?FamilyID=77f24c9d-b4b8-4f73-99e3-c66f80e415b6&displaylang=enMr Shaw

How should I configure Asp.NET on IIS 6, Sql Server 2005 and SSRS 2005 across 2 Windows Server 2003

I was running a MIS reporting solution on a single server running MS Windows 2003 Server and Sql Server 2005. The solution was built using ASP.NET 2.0 on IIS 6.0, Sql Server DB & SSRS. I now have purchased a 2nd server running MS Windows 2003 Server and Sql Server 2005. What is the best configuration to split the following application components across the 2 physical servers? ASP.NET web application SQL Server 2005 Datawarehouse SSRS Web Applications (Reports & ReportServer) SSRS Databases (ReportServer & ReportServerTempDB) The hardware configuration of the 2 servers are as follows Server 1 MS Windows Server 2003 Enterprise Edition SP2 Intel(R) Xeon(R) CPU 5150 @2.66GHz 16 GB RAM Sql Server 2005 SP3 Standard Edition Smart Array P400 in Slot 1 (SAS Array A with Spare / SAS Array B with Spare) Drive C: 68.33 GB | Drive D: 273.40 GB Server 2 MS Windows Server 2003 Standard Edition SP2 Intel(R) Xeon(R) CPU X5570 @2.93GHz 4 GB RAM Sql Server 2005 SP3 Standard Edition IBM ServeRAID-MR10i SAS/SATA Controller Drive C: 135GB | Drive D: 556 GB | Drive E: 271 GB Any suggestions would be of great help

SQL-Server 2005 x64 / windows server 2003 x64 crashes during file copy

Hi We are running: Microsoft SQL Server 2005 Standard - 9.00.4294.00 (X64) Microsoft Windows Server 2003 R2 Enterprise x64 We have gigabit interface. Today we copied a file (using robocopy) from our databaseserver to another server (backup-server). The copy was started from the backup-server and source were specified using UNC. The copy were using about 20% of the bandwith (about 200Mbit). During the copy, sql-server reported several errors, for example: AppDomain 15 (mp.dbo[runtime].14) is marked for unload due to memory pressure. The client was unable to reuse a session with SPID 75, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. ***Stack Dump being sent to [PATH\SQLDump0005.txt Resource Monitor (0x1384) Worker 0x000000008000C1C0 appears to be non-yielding on Node 0. Memory freed: 0 KB. Approx CPU Used: kernel 15 ms, user 218 ms, Interval: 428541. So to me it appears that sql-server crashed during a file copy. We have 27 GB ram. With 24.5 GB dedicated to SQL-Server. The files we copied were quite large, some over 50GB. I found a similar issue about this: http://support.microsoft.com/kb/920739/ Do you think the issue above could be the cause of the sql-server crash? ///Patrik

MS SQL Server 2005 and Windows server 2003 Environment




I wish to know how SQL Server 2005 is linked to Windows server 2003 Environment. I have knowledge about oracle databases. But Microsofet products are new to me.

To put it simple purpose of SQL Server 2005 and Windows server 2003. How both are linked ?




How to Install MSDTC on a multi Instance SQL Server Fail OverCluster (SQL 2005 & Windows 2003 R2 x64


I am installing 2 SQL instances on a fail over cluster.

Currently I have my Quorum and DTC resources on the default Group and the 2 sql instances on 2 other groups.

In this way would the DTC resource  be available for both the SQL groups or is there any other way i should go about doing this ?

crash seen in sql server 2005 on windows 2003 server in Itanium 64 bit

 Defaulted to export symbols for C:\Program Files\Common Files\System\Ole DB\sqloledb.dll -
function: sqloledb!SQLDebug
        000006fa`fa480538        nop.b  0 ;;

        000006fa`fa480540        ld8.a  r73=[r29]
        000006fa`fa480544        setf.sig f6=r27
        000006fa`fa480548        addl   r63=ffffffff`ffffffff, r0

        000006fa`fa480550        setf.sig f7=r28
        000006fa`fa480554        cmp.eq.unc p15, p14=r0, r36
        000006fa`fa480558 (p15)  br.cond.dpnt.many sqloledb!SQLDebug+23060 (000006fa`fa480570) ;;

FAULT ->000006fa`fa480560        st8    [r36]=r63
        000006fa`fa480564        nop.m  0
        000006fa`fa480568   &

SQL Compact Edition 3.5 and Visual Studio 2005, CE 2003 se, Windows Mobil 5.0




my big question is :

Is it possible to use SQL Compact Edition 3.5 with Visual Studio 2005 ?


We have one big .Net CF application which need to run on CE 2003 SE and Windows Mobil 5.0. It would be great if we only need one Package (CAB) for both types of devices.

Any hacks to get SQL Compact Edition 3.5 working with Visual Studio 2005 are welcome.





installing SQL Server 2005 on Windows 7 with Visual Studio 2010 already installed



Last year I had Vista on machine with Visual Studio 2008 and SQL Server 2005 running fine. Last week I decided to wipe the hard disk, install Windows 7 and make the move to Visual Studio 2010. I still need SQL Server 2005 to be able to test code for clients using this.

Anyway, Visual Studio 2010 Professional went on OK. This installed SQL Server 2008 Epxress.

I then try to install SQL Server 2005. I know that there is a compatibility problem, so following advice from other sources, I want to install it without running the server, then install SQL Server 2005 SP3. Then I should be up and running.


The problem is that even though I make sure the 'Start SQL Server' check box is UNchecked, part way through the installation it throws up an error saying it can't start the server and this part of the installation is unrolled.

I've tried running 'setup.exe SKUUPGRAGE=1' which gets rid of the only warning I was getting up to this point, but the setup seems to insist on running the server even though I tell it not to. So I don't get a chance to run SP3 on it.


I wonder if the problem is that SQL Server 2008 Epxress is already installed but can't see an easy way of uninstalling it. It doesn't appear as an uninstall option using the Visual Studio 2010 disk and if I look at uninstall programs I get the f

Compatibility issues between Microsoft Visual Studio 2005 and Windows Server 2008 R2


Dear sirs,

When I was installing SQL Server 2005 64 bit on Windows Server 2008 R2, I received a notice informing the software Microsoft Visual Studio 2005 has known compatibility issues with this version of Windows.

So how can I get around these problems?

I need to use Visual Studio 2005 to create the Integration Services packages.

Also, I need to migrate directories of Integration Services packages from a server with SQL Server 2005 32 bit on Windows Server 2003 32 bit for a server with SQL Server 2005 64 bit on Windows Server 2008 R2. How can I proceed to do this?

Thanks in advance.

Jose Luiz

Windows 7 connection to SQL Server Express 2005 on Windows Server 2003


I have SQL Server Express 2005 running on Windows Server 2003 R2.

I have several remote machines running Windows XP that connect to the database engine with no problem.  I'm using an Access adp to connect.

Just connected a Windows 7 machine and installed SQL Server Express 2005 on it and cannot connect to the db engine on the server. 

Error is:

Test connection failed because of an error in initializing provider. Login failed for user ''. The user is not associated with a trusted SQL Server connection. 


I am on the network and connected fine and can access files on the server.  I am using the same connection protocols in the Data Link Properties that the XP machines use.

Any ideas are greatly appreciated.



Advice on migrating from SQL Server 2005 Standard SP2 32-bit on Windows Server 2003 Standard SP2 32-


We are planning to migrate from SQL Server 2005 Standard SP2 32-bit on Windows Server 2003 Standard SP2 32-bit to SQL Server 2008 R2 Standard 64-bit on Windows Server 2008 R2 Standard SP1 64-bit. Would be grateful for any advice on making such a move.


SQL Servant

Use The Source, Luke: Source Server Helps You Kill Bugs Dead In Visual Studio 2005


The latest releases of WinDBG and Visual Studio know exactly how to use source server, so its benefits are available to both .NET and native C++ developers. See why this is so important in tracking down bugs.

John Robbins

MSDN Magazine August 2006

Windows Server 2003: Discover Improved System Info, New Kernel, Debugging, Security, and UI APIs


There's a lot to say about Windows Server 2003. First of all, it's the first operating system with built-in .NET Framework support, and it's the first 64-bit OS from Microsoft. But wait, there's more! There are lots of new features and APIs in this version as well. For instance, Windows Server 2003 features Hot Add Memory and a number of other arcane new tidbits. There are new APIs for handling threads, directories, and files, and new features like the low fragmentation heap for managing memory and system information. There's vectored exception handling and new UI APIs as well.OS internals expert Matt Pietrek takes a look at the additions he finds most interesting and useful so you'll have a good place to start when you dive into Windows Server 2003.

Matt Pietrek

MSDN Magazine June 2003

Security Briefs: Exploring S4U Kerberos Extensions in Windows Server 2003


Building Web sites that provide services external to the corporate firewall is tricky. Usually it's not desirable to grant corporate domain accounts to external clients, and from a purely practical standpoint Kerberos does not work well over the Internet due to the typical configuration of client-side firewalls.

Keith Brown

MSDN Magazine April 2003

SQL express 2008 r2 on windows server 2003

install ends with the following error : "MsiEnumRelatedProducts failed to enumerate products with UpgradeCode='{1B117BA7-5BC1-419E-820E-7D4F3F412C7B}'. Error code: 1610."

SQl server 2005 install failed on Windows XP pro sp3 due to msxml 6 sp2

Summary log: Microsoft SQL Server 2005 9.00.4035.00 ============================== OS Version      : Microsoft Windows XP Professional Service Pack 3 (Build 2600) Time            : Tue Aug 24 20:16:01 2010   Machine         : D3F2LN81 Product         : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.4035.00 Install         : Successful Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0005_D3F2LN81_SQLSupport_1.log -------------------------------------------------------------------------------- Machine         : D3F2LN81 Product         : Microsoft SQL Server Native Client Product Version : 9.00.4035.00 Install         : Successful Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0005_D3F2LN81_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine         : D3F2LN81 Product&nb

Kerberos issue with SQL Reporting Services 2005 on Server 2003 R2

Hi Guys,apologies if this is the incorrect forum, so moderators, feel free to move it to SQL/IIS/SharePoint as appropriate... [Windows Server Security moderator pushed me this direction]I have a test environment that I'm trying to get SQL Reporting Services 2005 SP3 working in integrated mode with SharePoint 2007 SP2.The environment is all in VMWare, running Server 2003 R2 x86 and is layed out like this:SERVER A:AD/DNS/DHCPSERVER B:SQL 2005 SP3 CU8SERVER C:SharePoint 2007 SP2 Dec 09 CU- Central admin on port 9000- SSP on port 9001- MySite on port 81- Main Content on port 80SQL Reporting Services 2005 SP3 CU8- Reporting Service website on port 82SERVER D:SharePoint 2007 SP2 Dec 09 CU- Central admin on port 9000- SSP on port 9001- MySite on port 81- Main Content on port 80SQL Reporting Services 2005 SP3 CU8- Reporting Service website on port 82Through the use of DNS and (SharePoint) Alternate Access Names, SERVER D is used to deliver the Main Content in SharePoint and the Reporting Service website.  SERVER C is used to deliver the Central Admin, SSP and MySite.I've set up SPN's for the SharePoint App Pools, using the following: [main content] setspn -S HTTP/SERVERA DOMAIN\AppPoolUserA setspn -S HTTP/SERVERA.FQDN DOMAIN\AppPoolUserA setspn -S HTTP/SERVERB DOMAIN\AppPoolUserA setspn -S HTTP/SERVERB.FQDN DOMAIN\AppPoolUserA [repor
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend