You have a TCP/IP alias established created on your computer. Remove it and
setup should complete successfully. Setup starts SQL Server in a mode to
accept only shared memory connections. The alias is preventing setup from
connecting.
Run cliconfg from Start - Run. Go to the ALias tab and delete the alias for
this server, You do not need it. Or should not need it. If you do then
there is another problem that needs to be addressed.
Rand
This posting is provided "as is" with no warranties and confers no rights.Rand!
You the man! I was about to have a heart attack when i had uninstalled our
SQL Developer server and could not install Standard edition. Your suggestio
n worked like a charm! Your advice is excellent even 6 months later.
Showing posts with label setup. Show all posts
Showing posts with label setup. Show all posts
Friday, March 30, 2012
Problem in installing SQL2K SP3
HI
I'm installing SQL2K SP3 (new installation not upgrade) but I've this error
"Setup failed to configure the server. Refer to the server error logs and setup error logs for more information."
I don't know what's the error and I want to know where I can find the "server error log" or the "setup error log"Originally posted by mac07
HI
I'm installing SQL2K SP3 (new installation not upgrade) but I've this error
"Setup failed to configure the server. Refer to the server error logs and setup error logs for more information."
I don't know what's the error and I want to know where I can find the "server error log" or the "setup error log"
Check out the following files to see where the installation went wrong:
All in C:\Winnt\ folder
setpapi.log
dasetup.log
Hope this helpssql
I'm installing SQL2K SP3 (new installation not upgrade) but I've this error
"Setup failed to configure the server. Refer to the server error logs and setup error logs for more information."
I don't know what's the error and I want to know where I can find the "server error log" or the "setup error log"Originally posted by mac07
HI
I'm installing SQL2K SP3 (new installation not upgrade) but I've this error
"Setup failed to configure the server. Refer to the server error logs and setup error logs for more information."
I don't know what's the error and I want to know where I can find the "server error log" or the "setup error log"
Check out the following files to see where the installation went wrong:
All in C:\Winnt\ folder
setpapi.log
dasetup.log
Hope this helpssql
Problem in IDENTITY COLUMNS
Hi folks! I've a merge replication setup b/w two servers.
Published tables have columns (INT IDENTITY SEED 1 INCREMENT[NOT FOR REPLICATION]).
Whenever i apply the SNAPSHOT, i have to run DBCC CHECKIDENT('table' RESEED) for each table at the subscriber twice, for the values in the columns are almost always greater than the ID-Seed value. For example the last Identity value in the column is 999 but whenever i insert a new row; i get error; couldn't insert duplicate value into the table. When i run the dbcc check i see the following message:
"Checking identity information: current identity value '1', current column value '999'."
How do i square this away?Originally posted by TALAT
Hi folks! I've a merge replication setup b/w two servers.
Published tables have columns (INT IDENTITY SEED 1 INCREMENT[NOT FOR REPLICATION]).
Whenever i apply the SNAPSHOT, i have to run DBCC CHECKIDENT('table' RESEED) for each table at the subscriber twice, for the values in the columns are almost always greater than the ID-Seed value. For example the last Identity value in the column is 999 but whenever i insert a new row; i get error; couldn't insert duplicate value into the table. When i run the dbcc check i see the following message:
"Checking identity information: current identity value '1', current column value '999'."
How do i square this away?
You will have to find the max value and do something like this.
DBCC CHECKIDENT('table',RESEED,@.max_value)|||Howdy!
Running: DBCC CHECKIDENT('table', RESEED). when i run it second time for the table; the identity value gets normal, i.e. it gets the same as the last value in the column. But it's rather painful to run it for each table. I never had this problem at the publisher it's only at the subscriber. Is there a permanent solution?
Thanx for the reply.
Published tables have columns (INT IDENTITY SEED 1 INCREMENT[NOT FOR REPLICATION]).
Whenever i apply the SNAPSHOT, i have to run DBCC CHECKIDENT('table' RESEED) for each table at the subscriber twice, for the values in the columns are almost always greater than the ID-Seed value. For example the last Identity value in the column is 999 but whenever i insert a new row; i get error; couldn't insert duplicate value into the table. When i run the dbcc check i see the following message:
"Checking identity information: current identity value '1', current column value '999'."
How do i square this away?Originally posted by TALAT
Hi folks! I've a merge replication setup b/w two servers.
Published tables have columns (INT IDENTITY SEED 1 INCREMENT[NOT FOR REPLICATION]).
Whenever i apply the SNAPSHOT, i have to run DBCC CHECKIDENT('table' RESEED) for each table at the subscriber twice, for the values in the columns are almost always greater than the ID-Seed value. For example the last Identity value in the column is 999 but whenever i insert a new row; i get error; couldn't insert duplicate value into the table. When i run the dbcc check i see the following message:
"Checking identity information: current identity value '1', current column value '999'."
How do i square this away?
You will have to find the max value and do something like this.
DBCC CHECKIDENT('table',RESEED,@.max_value)|||Howdy!
Running: DBCC CHECKIDENT('table', RESEED). when i run it second time for the table; the identity value gets normal, i.e. it gets the same as the last value in the column. But it's rather painful to run it for each table. I never had this problem at the publisher it's only at the subscriber. Is there a permanent solution?
Thanx for the reply.
Friday, March 9, 2012
Problem Deploying Reports when using SSL
Here is my current setup. I have Report Services sp1 installed on a Windows
2000 machine with SQL Server 2000. We have successfully configured RS to
produce reports over the internet via SSL. The actual viewing of the report
over the internet works great. However, in Visual Studio I receive the
following error when trying to deploy the reports...
"The underlying connection was closed. Could not establish trust
relationship with remote server"
The only work around I have found so far is to modify the
rsreportserver.config file and change secureconnectionlevel= from 2 to 0.
Then I am able to deploy the reports and do not receive this message.
Because SSL is a must, I then have to change the secureconnectionlevel= back
to 2.
Users externally are accessing the report server via
http://FQDN/reportserver. I had gone into the rswebapplication.config file
and changed <ReportServerUrl>http://server/reportserver<ReportServerUrl> to
<ReportServerUrl>http://FQDN/reportserver<ReportServerUrl> but no luck. My
certificate name uses the FQDN as the site name.
My question is why I am not able to deploy my reports when the SSL is turned
on?
I hope this makes sense and I am sure I left something out. Please let me
know your thoughts. Thanks!Sounds like you're hitting the issue in this KB article
http://support.microsoft.com/default.aspx?scid=kb;en-us;823177. Are you
specifying the FQDN in VS when deploying the reports?
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:B42B3849-C5FA-45AB-AEDA-D769D49ED57D@.microsoft.com...
> Here is my current setup. I have Report Services sp1 installed on a
> Windows
> 2000 machine with SQL Server 2000. We have successfully configured RS to
> produce reports over the internet via SSL. The actual viewing of the
> report
> over the internet works great. However, in Visual Studio I receive the
> following error when trying to deploy the reports...
> "The underlying connection was closed. Could not establish trust
> relationship with remote server"
> The only work around I have found so far is to modify the
> rsreportserver.config file and change secureconnectionlevel= from 2 to 0.
> Then I am able to deploy the reports and do not receive this message.
> Because SSL is a must, I then have to change the secureconnectionlevel=> back
> to 2.
> Users externally are accessing the report server via
> http://FQDN/reportserver. I had gone into the rswebapplication.config
> file
> and changed <ReportServerUrl>http://server/reportserver<ReportServerUrl>
> to
> <ReportServerUrl>http://FQDN/reportserver<ReportServerUrl> but no luck.
> My
> certificate name uses the FQDN as the site name.
> My question is why I am not able to deploy my reports when the SSL is
> turned
> on?
> I hope this makes sense and I am sure I left something out. Please let me
> know your thoughts. Thanks!
>
2000 machine with SQL Server 2000. We have successfully configured RS to
produce reports over the internet via SSL. The actual viewing of the report
over the internet works great. However, in Visual Studio I receive the
following error when trying to deploy the reports...
"The underlying connection was closed. Could not establish trust
relationship with remote server"
The only work around I have found so far is to modify the
rsreportserver.config file and change secureconnectionlevel= from 2 to 0.
Then I am able to deploy the reports and do not receive this message.
Because SSL is a must, I then have to change the secureconnectionlevel= back
to 2.
Users externally are accessing the report server via
http://FQDN/reportserver. I had gone into the rswebapplication.config file
and changed <ReportServerUrl>http://server/reportserver<ReportServerUrl> to
<ReportServerUrl>http://FQDN/reportserver<ReportServerUrl> but no luck. My
certificate name uses the FQDN as the site name.
My question is why I am not able to deploy my reports when the SSL is turned
on?
I hope this makes sense and I am sure I left something out. Please let me
know your thoughts. Thanks!Sounds like you're hitting the issue in this KB article
http://support.microsoft.com/default.aspx?scid=kb;en-us;823177. Are you
specifying the FQDN in VS when deploying the reports?
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:B42B3849-C5FA-45AB-AEDA-D769D49ED57D@.microsoft.com...
> Here is my current setup. I have Report Services sp1 installed on a
> Windows
> 2000 machine with SQL Server 2000. We have successfully configured RS to
> produce reports over the internet via SSL. The actual viewing of the
> report
> over the internet works great. However, in Visual Studio I receive the
> following error when trying to deploy the reports...
> "The underlying connection was closed. Could not establish trust
> relationship with remote server"
> The only work around I have found so far is to modify the
> rsreportserver.config file and change secureconnectionlevel= from 2 to 0.
> Then I am able to deploy the reports and do not receive this message.
> Because SSL is a must, I then have to change the secureconnectionlevel=> back
> to 2.
> Users externally are accessing the report server via
> http://FQDN/reportserver. I had gone into the rswebapplication.config
> file
> and changed <ReportServerUrl>http://server/reportserver<ReportServerUrl>
> to
> <ReportServerUrl>http://FQDN/reportserver<ReportServerUrl> but no luck.
> My
> certificate name uses the FQDN as the site name.
> My question is why I am not able to deploy my reports when the SSL is
> turned
> on?
> I hope this makes sense and I am sure I left something out. Please let me
> know your thoughts. Thanks!
>
Subscribe to:
Posts (Atom)