Failed to register instance from Windows 2003 server

Hi,
We have a Windows 2000 server (domain server) as suport for our database,
with two instances of SQL Server 2000 (one sensitive and one insensitive) and
decided to move the sensitive instance on a Windows 2003 server.
When I try to make the registration of the instance from Windows 2003
Server on Enterprise Manager from Windows 2000 Server it fail with time out
message.
I need to make a link server on instance from Windows 2000 but it seems
Windows 2003 has a security setting that stop me from doing this.
Any idea would be appreciated."You may not be able to connect to an instance of SQL Server 2000 Service
Pack 2 or earlier that is installed on a Windows Server 2003 computer
through the TCP/IP port"
http://support.microsoft.com/default.aspx?scid=kb;en-us;884012
Cristian Lefter, SQL Server MVP
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
> and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
> out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>|||Thank you, but on both systems SQL Server instances are with Service Pack 3
installed. Windows 2000 server is with Service Pack 4 installed.
"Cristian Lefter" wrote:
> "You may not be able to connect to an instance of SQL Server 2000 Service
> Pack 2 or earlier that is installed on a Windows Server 2003 computer
> through the TCP/IP port"
> http://support.microsoft.com/default.aspx?scid=kb;en-us;884012
> Cristian Lefter, SQL Server MVP
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> > Hi,
> > We have a Windows 2000 server (domain server) as suport for our database,
> > with two instances of SQL Server 2000 (one sensitive and one insensitive)
> > and
> > decided to move the sensitive instance on a Windows 2003 server.
> > When I try to make the registration of the instance from Windows 2003
> > Server on Enterprise Manager from Windows 2000 Server it fail with time
> > out
> > message.
> > I need to make a link server on instance from Windows 2000 but it seems
> > Windows 2003 has a security setting that stop me from doing this.
> >
> > Any idea would be appreciated.
> >
>
>|||By default when you install win2k3 all network connections are firewalled so
I think you must enable tcp port 1433 in your firewall.
Right click on LAN connection, chose properties then chose advanced tab, on
services tab click add button and Write name and description of service,
chose Tcp, and put 1433 in both textboxes.
Regards,
Daniel
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>|||Thank you, I'll try your tip. I didn't do this because the firewall option
was unchecked. But it could be active some other way.
"Daniel Joskovski" wrote:
> By default when you install win2k3 all network connections are firewalled so
> I think you must enable tcp port 1433 in your firewall.
> Right click on LAN connection, chose properties then chose advanced tab, on
> services tab click add button and Write name and description of service,
> chose Tcp, and put 1433 in both textboxes.
> Regards,
> Daniel
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> > Hi,
> > We have a Windows 2000 server (domain server) as suport for our database,
> > with two instances of SQL Server 2000 (one sensitive and one insensitive)
> and
> > decided to move the sensitive instance on a Windows 2003 server.
> > When I try to make the registration of the instance from Windows 2003
> > Server on Enterprise Manager from Windows 2000 Server it fail with time
> out
> > message.
> > I need to make a link server on instance from Windows 2000 but it seems
> > Windows 2003 has a security setting that stop me from doing this.
> >
> > Any idea would be appreciated.
> >
>
>

Failed to register instance from Windows 2003 server

Hi,
We have a Windows 2000 server (domain server) as suport for our database,
with two instances of SQL Server 2000 (one sensitive and one insensitive) an
d
decided to move the sensitive instance on a Windows 2003 server.
When I try to make the registration of the instance from Windows 2003
Server on Enterprise Manager from Windows 2000 Server it fail with time out
message.
I need to make a link server on instance from Windows 2000 but it seems
Windows 2003 has a security setting that stop me from doing this.
Any idea would be appreciated."You may not be able to connect to an instance of SQL Server 2000 Service
Pack 2 or earlier that is installed on a Windows Server 2003 computer
through the TCP/IP port"
http://support.microsoft.com/defaul...kb;en-us;884012
Cristian Lefter, SQL Server MVP
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
> and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
> out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>|||Thank you, but on both systems SQL Server instances are with Service Pack 3
installed. Windows 2000 server is with Service Pack 4 installed.
"Cristian Lefter" wrote:

> "You may not be able to connect to an instance of SQL Server 2000 Service
> Pack 2 or earlier that is installed on a Windows Server 2003 computer
> through the TCP/IP port"
> http://support.microsoft.com/defaul...kb;en-us;884012
> Cristian Lefter, SQL Server MVP
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
>
>|||By default when you install win2k3 all network connections are firewalled so
I think you must enable tcp port 1433 in your firewall.
Right click on LAN connection, chose properties then chose advanced tab, on
services tab click add button and Write name and description of service,
chose Tcp, and put 1433 in both textboxes.
Regards,
Daniel
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>|||Thank you, I'll try your tip. I didn't do this because the firewall option
was unchecked. But it could be active some other way.
"Daniel Joskovski" wrote:

> By default when you install win2k3 all network connections are firewalled
so
> I think you must enable tcp port 1433 in your firewall.
> Right click on LAN connection, chose properties then chose advanced tab, o
n
> services tab click add button and Write name and description of service,
> chose Tcp, and put 1433 in both textboxes.
> Regards,
> Daniel
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> and
> out
>
>sql

Failed to register instance from Windows 2003 server

Hi,
We have a Windows 2000 server (domain server) as suport for our database,
with two instances of SQL Server 2000 (one sensitive and one insensitive) and
decided to move the sensitive instance on a Windows 2003 server.
When I try to make the registration of the instance from Windows 2003
Server on Enterprise Manager from Windows 2000 Server it fail with time out
message.
I need to make a link server on instance from Windows 2000 but it seems
Windows 2003 has a security setting that stop me from doing this.
Any idea would be appreciated.
"You may not be able to connect to an instance of SQL Server 2000 Service
Pack 2 or earlier that is installed on a Windows Server 2003 computer
through the TCP/IP port"
http://support.microsoft.com/default...b;en-us;884012
Cristian Lefter, SQL Server MVP
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
> and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
> out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>
|||Thank you, but on both systems SQL Server instances are with Service Pack 3
installed. Windows 2000 server is with Service Pack 4 installed.
"Cristian Lefter" wrote:

> "You may not be able to connect to an instance of SQL Server 2000 Service
> Pack 2 or earlier that is installed on a Windows Server 2003 computer
> through the TCP/IP port"
> http://support.microsoft.com/default...b;en-us;884012
> Cristian Lefter, SQL Server MVP
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
>
>
|||By default when you install win2k3 all network connections are firewalled so
I think you must enable tcp port 1433 in your firewall.
Right click on LAN connection, chose properties then chose advanced tab, on
services tab click add button and Write name and description of service,
chose Tcp, and put 1433 in both textboxes.
Regards,
Daniel
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>
|||Thank you, I'll try your tip. I didn't do this because the firewall option
was unchecked. But it could be active some other way.
"Daniel Joskovski" wrote:

> By default when you install win2k3 all network connections are firewalled so
> I think you must enable tcp port 1433 in your firewall.
> Right click on LAN connection, chose properties then chose advanced tab, on
> services tab click add button and Write name and description of service,
> chose Tcp, and put 1433 in both textboxes.
> Regards,
> Daniel
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> and
> out
>
>

failed to register dll files needed for DTS

I found the information of installing DTS service without installing SQL server on the disc:

INSTALLATION NOTES FOR DATA TRANSFORMATION SERVICES (DTS)
------------------
The following files must be registered using the regsvr32.exe utility:
dtsffile.dll
dtspkg.dll
dtspump.dll
axscphst.dll

Example: regsvr32 80\Tools\Binn\dtsffile.dll

The sqlunirl.dll file should reside in the system folder (i.e., \winnt\system32 or \windows\system).

when I attempted to register the dlls, the message
:"loadLibrary("...\dtsffile.dll")failed - The speified module could not be
found.

is there anything I have to do before I can get the dll registered?

Thanks in advance.problem solved, please consult here:

http://www.sqldts.com/default.aspx?6,105,225,0,1

Failed to open malformed assembly 'MyAssembly' with HRESULT 0x80040154

Hello,

I wrote SQL Stored Procedures in C# and I am trying to register the asembly with SQL Server 2005 (Express Edition) using CREATE ASSEMBLY statment. I get this following error.

"Failed to open malformed assembly 'MyAssembly' with HRESULT 0x80040154"

Does anyone know how to solve this problem? It is driving me nuts for the last few days. I did enable CLR for SQL Server and also tried re-install SQL Server, but still I get this error.

Thanks in Advance,

Ravi

If this is an OLE/COM Stored Procedure, you need to create it using sp_OaCreate, rather than Create Assembly. Create Assembly is only for pure CLR based stored procedures. Also, using sp_OaCreate to load CLR based code in SQL Server is not supported: http://support.microsoft.com/kb/322884, so it is recommended that you transition your SP to a CLR based SP that does not rely on COM.

Steven

|||

Hi Steven,

Thanks for the reply. Its is a pure .NET Managed code assembly. It only does simple database operations, I didnt even have any new assemblies referenced also other than the ones Visual Studio adds by default ex: System, System.Data. The same assembly works in a differenct computer.

Ravi

|||

Hi Ravi,

Do you get the same error message when creating a different assembly? Perhaps, could you try one of the CLR samples from the BOL samples available here and let me know what happens? http://www.codeplex.com/MSFTEngProdSamples

Thanks,

Steven

|||

Yes, I get the same error for any assembly I create, I will try these samples and let you know.

Thanks,

Ravi