Clients in different domains

I have situation like this:

Company with one head office and one remote office. In the two offices I have two domains with two PDCs. The two networks are connected with eachother through leased line and the routers are configured properly. The SQL Server is on the PDC in head office and "local" clients connect fine. I cannot connect from the remote office. I think that I have folowing solutions:

1. make trust relationships between two domains - it will be hard a little bit because second PDC is samba on linux

2. make all clients in remote office to be members of the head office domain - potential problems if the leased line drops

3. make all clients to log in with same account as SQL Server logs locally - stupid

4. something else - what?

Thanks in advance!
DanielSql authentication is designed for such cases as this.

http://msdn.microsoft.com/library/en-us/architec/8_ar_cs_79kj.asp|||I am with SQL Server authentication and despite of this I cannot connect from some computers...|||Take a look at the following kb and make sure the firewall is setup correctly.
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932

Client Components Fail to Install - UPDATE

Me as well can not install the client components on boxes that have CLR 2.0/Office 2007 already installed. Notice that the failures have occured on boxes that doesn't have any SQL Server 2005 components installed. I do not know if it is CLR 2.0 or Office that causes the failures.

The error I'm getting initially is the same as Bogey1 and willgart: "

Upgrade failed due to the following error. The error code is:

-2147467259. Message: Unspecified error"

I have narrowed the failure down somewhat further; it occurs during installation of Business Intelligence Development Studio and it seems to happen during a process when it tries to upgrade the Microsoft Report Server (I have not installed Reporting Services - and it does not make any difference if Reporting Services is installed or not).

The workaround is obviously to choose an advanced setup and de-select BI Dev Studio from the Client Components installation node.

So far this has happened on following boxes:
1. LongHorn Server Beta 3 (LH) with CLR 3.0 and Office 2007 installed
2. A complete new install of LH Server, i.e nothing on the box that is not part of a normal LH installation (notice that CLR 2.0 is part of a LH installation).
3. Win 2K3 sp2 with CLR 3.0 and Office 2007 installed

In the installations above I have no Visual Studio bits installed what-so-ever

The installation succeeded on a complete new Win 2K3 sp2 installation; i.e. no CLR 2.0 bits and no Office 2007 bits.

Hope someone can shed some light on this.

Niels

OK, so I have now done a successful installation on a W2K3 sp2 box with Office 2007 installed - but no CLR 2.0/3.0. Remember from the initial post in this thread that the installation fails on W2K3 sp2 with CLR 2.0 and Office 2007.

It seems that the failures some of us have seen are due to having CLR 2.0/3.0 installed.

After the successful installation I installed the CLR 2.0 SDK, CLR 3.0 and Orcas and everything works just fine.

Niels
|||

Are you sure you do not have Microsoft Visual Studio installed by some application?

This error is usually due to VS installed in a non-default location.

Please confirm if you have VS installed in a non-default location, and if so, make sure that you have devenv.exe.config installed in its default location. For VS8:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe.config

|||Hi,

Thanks for coming back to me on this. The only thing that I have installed, when the installation has failed is CLR 2.0 and the CLR 2.0 SDK. I don't know if the SDK installation installs the VS bits (but I doubt it).

Niels
|||Please double-check if you have this file installed in a non-default location. VS installs as a pre-req for some components, and you might not notice that it is installed.|||Will do. However I'm on the road for another week, and won't be able to do it until I'm back.

Thanks again!

Niels

Client Components Fail to Install - UPDATE

Me as well can not install the client components on boxes that have CLR 2.0/Office 2007 already installed. Notice that the failures have occured on boxes that doesn't have any SQL Server 2005 components installed. I do not know if it is CLR 2.0 or Office that causes the failures.

The error I'm getting initially is the same as Bogey1 and willgart: "

Upgrade failed due to the following error. The error code is:

-2147467259. Message: Unspecified error"

I have narrowed the failure down somewhat further; it occurs during installation of Business Intelligence Development Studio and it seems to happen during a process when it tries to upgrade the Microsoft Report Server (I have not installed Reporting Services - and it does not make any difference if Reporting Services is installed or not).

The workaround is obviously to choose an advanced setup and de-select BI Dev Studio from the Client Components installation node.

So far this has happened on following boxes:
1. LongHorn Server Beta 3 (LH) with CLR 3.0 and Office 2007 installed
2. A complete new install of LH Server, i.e nothing on the box that is not part of a normal LH installation (notice that CLR 2.0 is part of a LH installation).
3. Win 2K3 sp2 with CLR 3.0 and Office 2007 installed

In the installations above I have no Visual Studio bits installed what-so-ever

The installation succeeded on a complete new Win 2K3 sp2 installation; i.e. no CLR 2.0 bits and no Office 2007 bits.

Hope someone can shed some light on this.

Niels

OK, so I have now done a successful installation on a W2K3 sp2 box with Office 2007 installed - but no CLR 2.0/3.0. Remember from the initial post in this thread that the installation fails on W2K3 sp2 with CLR 2.0 and Office 2007.

It seems that the failures some of us have seen are due to having CLR 2.0/3.0 installed.

After the successful installation I installed the CLR 2.0 SDK, CLR 3.0 and Orcas and everything works just fine.

Niels
|||

Are you sure you do not have Microsoft Visual Studio installed by some application?

This error is usually due to VS installed in a non-default location.

Please confirm if you have VS installed in a non-default location, and if so, make sure that you have devenv.exe.config installed in its default location. For VS8:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe.config

|||Hi,

Thanks for coming back to me on this. The only thing that I have installed, when the installation has failed is CLR 2.0 and the CLR 2.0 SDK. I don't know if the SDK installation installs the VS bits (but I doubt it).

Niels
|||Please double-check if you have this file installed in a non-default location. VS installs as a pre-req for some components, and you might not notice that it is installed.|||Will do. However I'm on the road for another week, and won't be able to do it until I'm back.

Thanks again!

Niels

Client Components Fail to Install

Me as well can not install the client components on boxes that have CLR 2.0/Office 2007 already installed. Notice that the failures have occured on boxes that doesn't have any SQL Server 2005 components installed. I do not know if it is CLR 2.0 or Office that causes the failures.

The error I'm getting initially is the same as Bogey1 and willgart: "

Upgrade failed due to the following error. The error code is:

-2147467259. Message: Unspecified error"

I have narrowed the failure down somewhat further; it occurs during installation of Business Intelligence Development Studio and it seems to happen during a process when it tries to upgrade the Microsoft Report Server (I have not installed Reporting Services - and it does not make any difference if Reporting Services is installed or not).

The workaround is obviously to choose an advanced setup and de-select BI Dev Studio from the Client Components installation node.

So far this has happened on following boxes:
1. LongHorn Server Beta 3 (LH) with CLR 3.0 and Office 2007 installed
2. A complete new install of LH Server, i.e nothing on the box that is not part of a normal LH installation (notice that CLR 2.0 is part of a LH installation).
3. Win 2K3 sp2 with CLR 3.0 and Office 2007 installed

In the installations above I have no Visual Studio bits installed what-so-ever

The installation succeeded on a complete new Win 2K3 sp2 installation; i.e. no CLR 2.0 bits and no Office 2007 bits.

Hope someone can shed some light on this.

Niels

OK, so I have now done a successful installation on a W2K3 sp2 box with Office 2007 installed - but no CLR 2.0/3.0. Remember from the initial post in this thread that the installation fails on W2K3 sp2 with CLR 2.0 and Office 2007.

It seems that the failures some of us have seen are due to having CLR 2.0/3.0 installed.

After the successful installation I installed the CLR 2.0 SDK, CLR 3.0 and Orcas and everything works just fine.

Niels
|||

Are you sure you do not have Microsoft Visual Studio installed by some application?

This error is usually due to VS installed in a non-default location.

Please confirm if you have VS installed in a non-default location, and if so, make sure that you have devenv.exe.config installed in its default location. For VS8:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe.config

|||Hi,

Thanks for coming back to me on this. The only thing that I have installed, when the installation has failed is CLR 2.0 and the CLR 2.0 SDK. I don't know if the SDK installation installs the VS bits (but I doubt it).

Niels
|||Please double-check if you have this file installed in a non-default location. VS installs as a pre-req for some components, and you might not notice that it is installed.|||Will do. However I'm on the road for another week, and won't be able to do it until I'm back.

Thanks again!

Niels