Problem returning SQL data

I'm having trouble with the display of data when I test my asp page. I basically retrieves or pulls data from different tables in a database. Based on an ID number (which I can change manually by typing in a value and appending it to the URL), it shows GuestName, GuestDescription and URL as text link. I can get it to do that much. But for some reason it's not showing the URL associated with the Guest Name. I dont think it's the display section of my code. I think it's the Select statement.

Here is what the output looks like in my Firefox and IE browsers when I test. Some data has been changed to protect it's integrity:

(Name in bold) Mark Crisp's author of The Bush Lexicon. His new book...

Related Links:
John Doe interviewed by Susan Smith, 123 News

What it should say in the link is this: Mark Crisp's blog (as text link)

When I test for different data I just change the end of the URL like this:
defaultprogram4.asp?ID=1234 (this number represents an ID column in a table)

Code Snippet

<%
set con = Server.CreateObject("ADODB.Connection")
con.Open "File Name=E:\webservice\Company\Company.UDL"
set rs = Server.CreateObject("ADODB.Recordset")

id=request.querystring("id") 'If this line is commented out the page will be blank.
'However you can still append a record number to the end of the URL and display that one.

IF id <> "" then id=id else id="1234" end if 'This line shows the default record of 1234. If this line is commented out the page will ONLY show the default record but will NOT allow you
'to append a different number

strSQL = "SELECT *, T_Programs.ID AS Expr1, T_ProgramGuests.ProgramID AS Expr2, T_ProgramGuests.GuestName AS Expr3, T_ProgramGuests.GuestDescription AS Expr4, T_ProgramLinks.URL AS Expr5, T_ProgramLinks.Description AS Expr6 FROM T_ProgramGuests CROSS JOIN T_Programs CROSS JOIN T_ProgramLinks WHERE (T_ProgramGuests.ProgramID = '" & id & "')"

rs.Open strSQL,con 'open a connection to the database

%>

<br />
<strong><% Response.Write RS ("GuestName") %> </strong> <% Response.Write RS("GuestDescription") %><br /><br />
Related Links:<br />
<li class='basic'><A HREF="<%= RS("URL") %>"><%= RS("Description") %></A></li>

<!-- END OF THE GUESTS AND LINKS SECTION -->

<%
recProgram.Close
con.Close
set recProgram = nothing
set con = nothing
%>

Bottom line here is this: Why would I be seeing one name but a link not associated with that name? It's as though it's reading a name from the ProgramGuests table and a URL from the
ProgramLinks table (Except that: it shows a completely different unrelated URL to that name).

What am I missing?Is you asp code showing anything ? As you are referencing the column e.g. GuestName, it should not display anything for this attribute as it does not exists in the recordset. The attribute is renamed (in your query to Expr3, so you either will have to delete the AS Expr3 part or rename the reference of the recordset, e.g. rs("Expr3").

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Problem replication complex database

I have been have real trouble over the last few weeks trying to get an
application database to replicate. The database is relatively complex in
structure - but not ridiculously so.
It doesnt seem to matter what replication technique that is used we always
get the same problem.
Line516: Incorrect syntax near '-'.
(Source: SERVER2 (Data source); Error number: 50007)
xp_execresultset: unable to execute result set
{Source: SERVER2 (Data source); Error number: 50007)
The process could not deliver the snapshot to the Subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
However we found an article
http://support.microsoft.com/default...b;en-us;299439
We have followed this and tried moving the GUID columns to the end but now a
new error is seen...
The schema script '\\SERVER1\d$\sql
data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
could not be propagated to the subscriber.
The schema script '\\SERVER1\d$\sql
data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
------
Operand type clash: int is incompatible with uniqueidentifier
(Source: SERVER2(Data source); Error number: 206)
-----
Any ideas would be very welcome!
Could you please provide the SQL Server version of all servers involved --
select @.@.version.
Could you also please try to manually apply the schema script below to the
subscriber database via query analyzer. Hopefully, this will allow you to
determine where the failure is coming from in the script. Please post the
information back to this thread.
Thanks,
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark Broadbent" <nospam@.nospam.co.uk> wrote in message
news:uCwDBuI4FHA.2364@.TK2MSFTNGP12.phx.gbl...
>I have been have real trouble over the last few weeks trying to get an
>application database to replicate. The database is relatively complex in
>structure - but not ridiculously so.
> It doesnt seem to matter what replication technique that is used we always
> get the same problem.
> Line516: Incorrect syntax near '-'.
> (Source: SERVER2 (Data source); Error number: 50007)
> xp_execresultset: unable to execute result set
> {Source: SERVER2 (Data source); Error number: 50007)
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> However we found an article
> http://support.microsoft.com/default...b;en-us;299439
> We have followed this and tried moving the GUID columns to the end but now
> a new error is seen...
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> Operand type clash: int is incompatible with uniqueidentifier
> (Source: SERVER2(Data source); Error number: 206)
> -----
> Any ideas would be very welcome!
>
|||For what it is worth, we ran into similar '-' problems with our server names
in a recent re-engineering. I don't remember the error number(s), but we did
two things: 1- qualified the server names in source code with [server-name]
2- renamed several servers or changed dns entries to remove the
'-'
Just a thought.
Joseph R.P. Maloney, CSP,CCP,CDP
"Mark Broadbent" wrote:

> I have been have real trouble over the last few weeks trying to get an
> application database to replicate. The database is relatively complex in
> structure - but not ridiculously so.
> It doesnt seem to matter what replication technique that is used we always
> get the same problem.
> Line516: Incorrect syntax near '-'.
> (Source: SERVER2 (Data source); Error number: 50007)
> xp_execresultset: unable to execute result set
> {Source: SERVER2 (Data source); Error number: 50007)
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> However we found an article
> http://support.microsoft.com/default...b;en-us;299439
> We have followed this and tried moving the GUID columns to the end but now a
> new error is seen...
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> Operand type clash: int is incompatible with uniqueidentifier
> (Source: SERVER2(Data source); Error number: 206)
> -----
> Any ideas would be very welcome!
>
>
|||Guys, thanks for your suggestions. It appears (I think) that the new problem
is down to a stored procedure inserting data into a table not using named
columns! Since the ordering of the tables has changed due to the GUID
columns being moved, this caused a problem. The developers have changed the
script.
br,
mark.
"Mark Broadbent" <nospam@.nospam.co.uk> wrote in message
news:uCwDBuI4FHA.2364@.TK2MSFTNGP12.phx.gbl...
>I have been have real trouble over the last few weeks trying to get an
>application database to replicate. The database is relatively complex in
>structure - but not ridiculously so.
> It doesnt seem to matter what replication technique that is used we always
> get the same problem.
> Line516: Incorrect syntax near '-'.
> (Source: SERVER2 (Data source); Error number: 50007)
> xp_execresultset: unable to execute result set
> {Source: SERVER2 (Data source); Error number: 50007)
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> However we found an article
> http://support.microsoft.com/default...b;en-us;299439
> We have followed this and tried moving the GUID columns to the end but now
> a new error is seen...
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> Operand type clash: int is incompatible with uniqueidentifier
> (Source: SERVER2(Data source); Error number: 206)
> -----
> Any ideas would be very welcome!
>
sql

Problem replication complex database

I have been have real trouble over the last few weeks trying to get an
application database to replicate. The database is relatively complex in
structure - but not ridiculously so.
It doesnt seem to matter what replication technique that is used we always
get the same problem.
Line516: Incorrect syntax near '-'.
(Source: SERVER2 (Data source); Error number: 50007)
xp_execresultset: unable to execute result set
{Source: SERVER2 (Data source); Error number: 50007)
The process could not deliver the snapshot to the Subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
However we found an article
http://support.microsoft.com/default...b;en-us;299439
We have followed this and tried moving the GUID columns to the end but now a
new error is seen...
The schema script '\\SERVER1\d$\sql
data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
could not be propagated to the subscriber.
The schema script '\\SERVER1\d$\sql
data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
------
Operand type clash: int is incompatible with uniqueidentifier
(Source: SERVER2(Data source); Error number: 206)
-----
Any ideas would be very welcome!
For what it is worth, we ran into similar '-' problems with our server names
in a recent re-engineering. I don't remember the error number(s), but we did
two things: 1- qualified the server names in source code with [server-name]
2- renamed several servers or changed dns entries to remove the
'-'
Just a thought.
Joseph R.P. Maloney, CSP,CCP,CDP
"Mark Broadbent" wrote:

> I have been have real trouble over the last few weeks trying to get an
> application database to replicate. The database is relatively complex in
> structure - but not ridiculously so.
> It doesnt seem to matter what replication technique that is used we always
> get the same problem.
> Line516: Incorrect syntax near '-'.
> (Source: SERVER2 (Data source); Error number: 50007)
> xp_execresultset: unable to execute result set
> {Source: SERVER2 (Data source); Error number: 50007)
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> However we found an article
> http://support.microsoft.com/default...b;en-us;299439
> We have followed this and tried moving the GUID columns to the end but now a
> new error is seen...
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> Operand type clash: int is incompatible with uniqueidentifier
> (Source: SERVER2(Data source); Error number: 206)
> -----
> Any ideas would be very welcome!
>
>
|||Guys, thanks for your suggestions. It appears (I think) that the new problem
is down to a stored procedure inserting data into a table not using named
columns! Since the ordering of the tables has changed due to the GUID
columns being moved, this caused a problem. The developers have changed the
script.
br,
mark.
"Mark Broadbent" <nospam@.nospam.co.uk> wrote in message
news:uCwDBuI4FHA.2364@.TK2MSFTNGP12.phx.gbl...
>I have been have real trouble over the last few weeks trying to get an
>application database to replicate. The database is relatively complex in
>structure - but not ridiculously so.
> It doesnt seem to matter what replication technique that is used we always
> get the same problem.
> Line516: Incorrect syntax near '-'.
> (Source: SERVER2 (Data source); Error number: 50007)
> xp_execresultset: unable to execute result set
> {Source: SERVER2 (Data source); Error number: 50007)
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> However we found an article
> http://support.microsoft.com/default...b;en-us;299439
> We have followed this and tried moving the GUID columns to the end but now
> a new error is seen...
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> Operand type clash: int is incompatible with uniqueidentifier
> (Source: SERVER2(Data source); Error number: 206)
> -----
> Any ideas would be very welcome!
>

Problem replication complex database

I have been have real trouble over the last few weeks trying to get an
application database to replicate. The database is relatively complex in
structure - but not ridiculously so.
It doesnt seem to matter what replication technique that is used we always
get the same problem.
Line516: Incorrect syntax near '-'.
(Source: SERVER2 (Data source); Error number: 50007)
xp_execresultset: unable to execute result set
{Source: SERVER2 (Data source); Error number: 50007)
The process could not deliver the snapshot to the Subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
However we found an article
http://support.microsoft.com/default.aspx?scid=kb;en-us;299439
We have followed this and tried moving the GUID columns to the end but now a
new error is seen...
The schema script '\\SERVER1\d$\sql
data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\20051103135903\spGetCriticalSectionToken_32.sch'
could not be propagated to the subscriber.
The schema script '\\SERVER1\d$\sql
data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\20051103135903\spGetCriticalSectionToken_32.sch'
could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
------
Operand type clash: int is incompatible with uniqueidentifier
(Source: SERVER2(Data source); Error number: 206)
-----
Any ideas would be very welcome!For what it is worth, we ran into similar '-' problems with our server names
in a recent re-engineering. I don't remember the error number(s), but we did
two things: 1- qualified the server names in source code with [server-name]
2- renamed several servers or changed dns entries to remove the
'-'
Just a thought.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Mark Broadbent" wrote:
> I have been have real trouble over the last few weeks trying to get an
> application database to replicate. The database is relatively complex in
> structure - but not ridiculously so.
> It doesnt seem to matter what replication technique that is used we always
> get the same problem.
> Line516: Incorrect syntax near '-'.
> (Source: SERVER2 (Data source); Error number: 50007)
> xp_execresultset: unable to execute result set
> {Source: SERVER2 (Data source); Error number: 50007)
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> However we found an article
> http://support.microsoft.com/default.aspx?scid=kb;en-us;299439
> We have followed this and tried moving the GUID columns to the end but now a
> new error is seen...
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\20051103135903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\20051103135903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> Operand type clash: int is incompatible with uniqueidentifier
> (Source: SERVER2(Data source); Error number: 206)
> -----
> Any ideas would be very welcome!
>
>|||Guys, thanks for your suggestions. It appears (I think) that the new problem
is down to a stored procedure inserting data into a table not using named
columns! Since the ordering of the tables has changed due to the GUID
columns being moved, this caused a problem. The developers have changed the
script.
br,
mark.
"Mark Broadbent" <nospam@.nospam.co.uk> wrote in message
news:uCwDBuI4FHA.2364@.TK2MSFTNGP12.phx.gbl...
>I have been have real trouble over the last few weeks trying to get an
>application database to replicate. The database is relatively complex in
>structure - but not ridiculously so.
> It doesnt seem to matter what replication technique that is used we always
> get the same problem.
> Line516: Incorrect syntax near '-'.
> (Source: SERVER2 (Data source); Error number: 50007)
> xp_execresultset: unable to execute result set
> {Source: SERVER2 (Data source); Error number: 50007)
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> However we found an article
> http://support.microsoft.com/default.aspx?scid=kb;en-us;299439
> We have followed this and tried moving the GUID columns to the end but now
> a new error is seen...
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\20051103135903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\20051103135903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> Operand type clash: int is incompatible with uniqueidentifier
> (Source: SERVER2(Data source); Error number: 206)
> -----
> Any ideas would be very welcome!
>

Problem replication complex database

I have been have real trouble over the last few weeks trying to get an
application database to replicate. The database is relatively complex in
structure - but not ridiculously so.
It doesnt seem to matter what replication technique that is used we always
get the same problem.
Line516: Incorrect syntax near '-'.
(Source: SERVER2 (Data source); Error number: 50007)
xp_execresultset: unable to execute result set
{Source: SERVER2 (Data source); Error number: 50007)
The process could not deliver the snapshot to the Subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
However we found an article
http://support.microsoft.com/defaul...kb;en-us;299439
We have followed this and tried moving the GUID columns to the end but now a
new error is seen...
The schema script '\\SERVER1\d$\sql
data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\
20051103135903\spGetCriticalSectionT
oken_32.sch'
could not be propagated to the subscriber.
The schema script '\\SERVER1\d$\sql
data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\
20051103135903\spGetCriticalSectionT
oken_32.sch'
could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
----
--
Operand type clash: int is incompatible with uniqueidentifier
(Source: SERVER2(Data source); Error number: 206)
----
--
Any ideas would be very welcome!For what it is worth, we ran into similar '-' problems with our server names
in a recent re-engineering. I don't remember the error number(s), but we di
d
two things: 1- qualified the server names in source code with [server-na
me]
2- renamed several servers or changed dns entries to remove the
'-'
Just a thought.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Mark Broadbent" wrote:

> I have been have real trouble over the last few weeks trying to get an
> application database to replicate. The database is relatively complex in
> structure - but not ridiculously so.
> It doesnt seem to matter what replication technique that is used we always
> get the same problem.
> Line516: Incorrect syntax near '-'.
> (Source: SERVER2 (Data source); Error number: 50007)
> xp_execresultset: unable to execute result set
> {Source: SERVER2 (Data source); Error number: 50007)
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> However we found an article
> http://support.microsoft.com/defaul...kb;en-us;299439
> We have followed this and tried moving the GUID columns to the end but now
a
> new error is seen...
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\
20051103135903\spGetCriticalSectio
nToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\
20051103135903\spGetCriticalSectio
nToken_32.sch'
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ----
--
> Operand type clash: int is incompatible with uniqueidentifier
> (Source: SERVER2(Data source); Error number: 206)
> ----
--
> Any ideas would be very welcome!
>
>|||Guys, thanks for your suggestions. It appears (I think) that the new problem
is down to a stored procedure inserting data into a table not using named
columns! Since the ordering of the tables has changed due to the GUID
columns being moved, this caused a problem. The developers have changed the
script.
br,
mark.
"Mark Broadbent" <nospam@.nospam.co.uk> wrote in message
news:uCwDBuI4FHA.2364@.TK2MSFTNGP12.phx.gbl...
>I have been have real trouble over the last few weeks trying to get an
>application database to replicate. The database is relatively complex in
>structure - but not ridiculously so.
> It doesnt seem to matter what replication technique that is used we always
> get the same problem.
> Line516: Incorrect syntax near '-'.
> (Source: SERVER2 (Data source); Error number: 50007)
> xp_execresultset: unable to execute result set
> {Source: SERVER2 (Data source); Error number: 50007)
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> However we found an article
> http://support.microsoft.com/defaul...kb;en-us;299439
> We have followed this and tried moving the GUID columns to the end but now
> a new error is seen...
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\
20051103135903\spGetCriticalSectio
nToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\
20051103135903\spGetCriticalSectio
nToken_32.sch'
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ----
--
> Operand type clash: int is incompatible with uniqueidentifier
> (Source: SERVER2(Data source); Error number: 206)
> ----
--
> Any ideas would be very welcome!
>

Problem on Saving Data to one of the Database but work normal on other DB

Hi All,
I have some trouble on supporting a Windows Base System wrote by DELPHI
language implemented in my Company
Environment :
There are two Windows Server 2003 Std Ed servers
Server1 is Application Server
Server2 is Database Server(MS SQL2000 Std SP3a)
Hardware:
IBM Dual Xeon CPU
4GB Memory
Raid5 with 137GB Harddisk Space
Networking:
Server1 exposed to the Internet with firewall protected
A cross over cable connected between Server1 and Server2
Our Case:
We setup the Application on Server1
And all Workstations using the Windows Base Interface to use the program
If some user work outside Office, they will use the program through a remote
connection named TAXXI(http://www.taxxi.com).
Now we met a problem, on the SQL Server, we have created 3-5 database for
different group of users.
One of the database named D on the SQL Server always hang without any error
log.
It suddenly hang when user save their Data.
They can get the data from the System ,
only Save the data will make the screen freeze and lost of data after the
system back to normal in a hrs later.
We can't find any strange log on the EVENT VIEWER or SQL Server Log
From the Performance Monitor, we just found the Page Fault/sec was high and
always reach the Peak on Server1.
For Server2, only Write to Physical Disk was high.
If we login to other database in the time database D freeze the user screen
when save,
it works normally with input or save data to the system.
Plz help and give some suggestions for us to solve the problem.
Thx
Jack
Have you checked for database blocking during the save operation?
Hope this helps.
Dan Guzman
SQL Server MVP
"J" <j@.j> wrote in message news:%23hqYryrMFHA.2384@.tk2msftngp13.phx.gbl...
> Hi All,
> I have some trouble on supporting a Windows Base System wrote by DELPHI
> language implemented in my Company
> Environment :
> There are two Windows Server 2003 Std Ed servers
> Server1 is Application Server
> Server2 is Database Server(MS SQL2000 Std SP3a)
> Hardware:
> IBM Dual Xeon CPU
> 4GB Memory
> Raid5 with 137GB Harddisk Space
> Networking:
> Server1 exposed to the Internet with firewall protected
> A cross over cable connected between Server1 and Server2
> Our Case:
> We setup the Application on Server1
> And all Workstations using the Windows Base Interface to use the program
> If some user work outside Office, they will use the program through a
> remote
> connection named TAXXI(http://www.taxxi.com).
> Now we met a problem, on the SQL Server, we have created 3-5 database for
> different group of users.
> One of the database named D on the SQL Server always hang without any
> error
> log.
> It suddenly hang when user save their Data.
> They can get the data from the System ,
> only Save the data will make the screen freeze and lost of data after the
> system back to normal in a hrs later.
> We can't find any strange log on the EVENT VIEWER or SQL Server Log
> From the Performance Monitor, we just found the Page Fault/sec was high
> and
> always reach the Peak on Server1.
> For Server2, only Write to Physical Disk was high.
> If we login to other database in the time database D freeze the user
> screen
> when save,
> it works normally with input or save data to the system.
> Plz help and give some suggestions for us to solve the problem.
> Thx
> Jack
>
|||I agree with Dan, it sounds like a locking problem... when things are hung
up, use sp_who or Sp_who2, and check the blocking field. If it is non-zero,
then the corresponding spid is being blocked by the spid in the blocking
field...
This problem is generally caused by long-running trasnactions.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"J" <j@.j> wrote in message news:%23hqYryrMFHA.2384@.tk2msftngp13.phx.gbl...
> Hi All,
> I have some trouble on supporting a Windows Base System wrote by DELPHI
> language implemented in my Company
> Environment :
> There are two Windows Server 2003 Std Ed servers
> Server1 is Application Server
> Server2 is Database Server(MS SQL2000 Std SP3a)
> Hardware:
> IBM Dual Xeon CPU
> 4GB Memory
> Raid5 with 137GB Harddisk Space
> Networking:
> Server1 exposed to the Internet with firewall protected
> A cross over cable connected between Server1 and Server2
> Our Case:
> We setup the Application on Server1
> And all Workstations using the Windows Base Interface to use the program
> If some user work outside Office, they will use the program through a
> remote
> connection named TAXXI(http://www.taxxi.com).
> Now we met a problem, on the SQL Server, we have created 3-5 database for
> different group of users.
> One of the database named D on the SQL Server always hang without any
> error
> log.
> It suddenly hang when user save their Data.
> They can get the data from the System ,
> only Save the data will make the screen freeze and lost of data after the
> system back to normal in a hrs later.
> We can't find any strange log on the EVENT VIEWER or SQL Server Log
> From the Performance Monitor, we just found the Page Fault/sec was high
> and
> always reach the Peak on Server1.
> For Server2, only Write to Physical Disk was high.
> If we login to other database in the time database D freeze the user
> screen
> when save,
> it works normally with input or save data to the system.
> Plz help and give some suggestions for us to solve the problem.
> Thx
> Jack
>

Problem on Saving Data to one of the Database but work normal on other DB

Hi All,
I have some trouble on supporting a Windows Base System wrote by DELPHI
language implemented in my Company
Environment :
There are two Windows Server 2003 Std Ed servers
Server1 is Application Server
Server2 is Database Server(MS SQL2000 Std SP3a)
Hardware:
IBM Dual Xeon CPU
4GB Memory
Raid5 with 137GB Harddisk Space
Networking:
Server1 exposed to the Internet with firewall protected
A cross over cable connected between Server1 and Server2
Our Case:
We setup the Application on Server1
And all Workstations using the Windows Base Interface to use the program
If some user work outside Office, they will use the program through a remote
connection named TAXXI(http://www.taxxi.com).
Now we met a problem, on the SQL Server, we have created 3-5 database for
different group of users.
One of the database named D on the SQL Server always hang without any error
log.
It suddenly hang when user save their Data.
They can get the data from the System ,
only Save the data will make the screen freeze and lost of data after the
system back to normal in a hrs later.
We can't find any strange log on the EVENT VIEWER or SQL Server Log
From the Performance Monitor, we just found the Page Fault/sec was high and
always reach the Peak on Server1.
For Server2, only Write to Physical Disk was high.
If we login to other database in the time database D freeze the user screen
when save,
it works normally with input or save data to the system.
Plz help and give some suggestions for us to solve the problem.
Thx
JackHave you checked for database blocking during the save operation?
Hope this helps.
Dan Guzman
SQL Server MVP
"J" <j@.j> wrote in message news:%23hqYryrMFHA.2384@.tk2msftngp13.phx.gbl...
> Hi All,
> I have some trouble on supporting a Windows Base System wrote by DELPHI
> language implemented in my Company
> Environment :
> There are two Windows Server 2003 Std Ed servers
> Server1 is Application Server
> Server2 is Database Server(MS SQL2000 Std SP3a)
> Hardware:
> IBM Dual Xeon CPU
> 4GB Memory
> Raid5 with 137GB Harddisk Space
> Networking:
> Server1 exposed to the Internet with firewall protected
> A cross over cable connected between Server1 and Server2
> Our Case:
> We setup the Application on Server1
> And all Workstations using the Windows Base Interface to use the program
> If some user work outside Office, they will use the program through a
> remote
> connection named TAXXI(http://www.taxxi.com).
> Now we met a problem, on the SQL Server, we have created 3-5 database for
> different group of users.
> One of the database named D on the SQL Server always hang without any
> error
> log.
> It suddenly hang when user save their Data.
> They can get the data from the System ,
> only Save the data will make the screen freeze and lost of data after the
> system back to normal in a hrs later.
> We can't find any strange log on the EVENT VIEWER or SQL Server Log
> From the Performance Monitor, we just found the Page Fault/sec was high
> and
> always reach the Peak on Server1.
> For Server2, only Write to Physical Disk was high.
> If we login to other database in the time database D freeze the user
> screen
> when save,
> it works normally with input or save data to the system.
> Plz help and give some suggestions for us to solve the problem.
> Thx
> Jack
>|||I agree with Dan, it sounds like a locking problem... when things are hung
up, use sp_who or Sp_who2, and check the blocking field. If it is non-zero,
then the corresponding spid is being blocked by the spid in the blocking
field...
This problem is generally caused by long-running trasnactions.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"J" <j@.j> wrote in message news:%23hqYryrMFHA.2384@.tk2msftngp13.phx.gbl...
> Hi All,
> I have some trouble on supporting a Windows Base System wrote by DELPHI
> language implemented in my Company
> Environment :
> There are two Windows Server 2003 Std Ed servers
> Server1 is Application Server
> Server2 is Database Server(MS SQL2000 Std SP3a)
> Hardware:
> IBM Dual Xeon CPU
> 4GB Memory
> Raid5 with 137GB Harddisk Space
> Networking:
> Server1 exposed to the Internet with firewall protected
> A cross over cable connected between Server1 and Server2
> Our Case:
> We setup the Application on Server1
> And all Workstations using the Windows Base Interface to use the program
> If some user work outside Office, they will use the program through a
> remote
> connection named TAXXI(http://www.taxxi.com).
> Now we met a problem, on the SQL Server, we have created 3-5 database for
> different group of users.
> One of the database named D on the SQL Server always hang without any
> error
> log.
> It suddenly hang when user save their Data.
> They can get the data from the System ,
> only Save the data will make the screen freeze and lost of data after the
> system back to normal in a hrs later.
> We can't find any strange log on the EVENT VIEWER or SQL Server Log
> From the Performance Monitor, we just found the Page Fault/sec was high
> and
> always reach the Peak on Server1.
> For Server2, only Write to Physical Disk was high.
> If we login to other database in the time database D freeze the user
> screen
> when save,
> it works normally with input or save data to the system.
> Plz help and give some suggestions for us to solve the problem.
> Thx
> Jack
>

Problem on Saving Data to one of the Database but work normal on other DB

Hi All,
I have some trouble on supporting a Windows Base System wrote by DELPHI
language implemented in my Company
Environment :
There are two Windows Server 2003 Std Ed servers
Server1 is Application Server
Server2 is Database Server(MS SQL2000 Std SP3a)
Hardware:
IBM Dual Xeon CPU
4GB Memory
Raid5 with 137GB Harddisk Space
Networking:
Server1 exposed to the Internet with firewall protected
A cross over cable connected between Server1 and Server2
Our Case:
We setup the Application on Server1
And all Workstations using the Windows Base Interface to use the program
If some user work outside Office, they will use the program through a remote
connection named TAXXI(http://www.taxxi.com).
Now we met a problem, on the SQL Server, we have created 3-5 database for
different group of users.
One of the database named D on the SQL Server always hang without any error
log.
It suddenly hang when user save their Data.
They can get the data from the System ,
only Save the data will make the screen freeze and lost of data after the
system back to normal in a hrs later.
We can't find any strange log on the EVENT VIEWER or SQL Server Log
From the Performance Monitor, we just found the Page Fault/sec was high and
always reach the Peak on Server1.
For Server2, only Write to Physical Disk was high.
If we login to other database in the time database D freeze the user screen
when save,
it works normally with input or save data to the system.
Plz help and give some suggestions for us to solve the problem.
Thx
JackHave you checked for database blocking during the save operation?
--
Hope this helps.
Dan Guzman
SQL Server MVP
"J" <j@.j> wrote in message news:%23hqYryrMFHA.2384@.tk2msftngp13.phx.gbl...
> Hi All,
> I have some trouble on supporting a Windows Base System wrote by DELPHI
> language implemented in my Company
> Environment :
> There are two Windows Server 2003 Std Ed servers
> Server1 is Application Server
> Server2 is Database Server(MS SQL2000 Std SP3a)
> Hardware:
> IBM Dual Xeon CPU
> 4GB Memory
> Raid5 with 137GB Harddisk Space
> Networking:
> Server1 exposed to the Internet with firewall protected
> A cross over cable connected between Server1 and Server2
> Our Case:
> We setup the Application on Server1
> And all Workstations using the Windows Base Interface to use the program
> If some user work outside Office, they will use the program through a
> remote
> connection named TAXXI(http://www.taxxi.com).
> Now we met a problem, on the SQL Server, we have created 3-5 database for
> different group of users.
> One of the database named D on the SQL Server always hang without any
> error
> log.
> It suddenly hang when user save their Data.
> They can get the data from the System ,
> only Save the data will make the screen freeze and lost of data after the
> system back to normal in a hrs later.
> We can't find any strange log on the EVENT VIEWER or SQL Server Log
> From the Performance Monitor, we just found the Page Fault/sec was high
> and
> always reach the Peak on Server1.
> For Server2, only Write to Physical Disk was high.
> If we login to other database in the time database D freeze the user
> screen
> when save,
> it works normally with input or save data to the system.
> Plz help and give some suggestions for us to solve the problem.
> Thx
> Jack
>|||I agree with Dan, it sounds like a locking problem... when things are hung
up, use sp_who or Sp_who2, and check the blocking field. If it is non-zero,
then the corresponding spid is being blocked by the spid in the blocking
field...
This problem is generally caused by long-running trasnactions.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"J" <j@.j> wrote in message news:%23hqYryrMFHA.2384@.tk2msftngp13.phx.gbl...
> Hi All,
> I have some trouble on supporting a Windows Base System wrote by DELPHI
> language implemented in my Company
> Environment :
> There are two Windows Server 2003 Std Ed servers
> Server1 is Application Server
> Server2 is Database Server(MS SQL2000 Std SP3a)
> Hardware:
> IBM Dual Xeon CPU
> 4GB Memory
> Raid5 with 137GB Harddisk Space
> Networking:
> Server1 exposed to the Internet with firewall protected
> A cross over cable connected between Server1 and Server2
> Our Case:
> We setup the Application on Server1
> And all Workstations using the Windows Base Interface to use the program
> If some user work outside Office, they will use the program through a
> remote
> connection named TAXXI(http://www.taxxi.com).
> Now we met a problem, on the SQL Server, we have created 3-5 database for
> different group of users.
> One of the database named D on the SQL Server always hang without any
> error
> log.
> It suddenly hang when user save their Data.
> They can get the data from the System ,
> only Save the data will make the screen freeze and lost of data after the
> system back to normal in a hrs later.
> We can't find any strange log on the EVENT VIEWER or SQL Server Log
> From the Performance Monitor, we just found the Page Fault/sec was high
> and
> always reach the Peak on Server1.
> For Server2, only Write to Physical Disk was high.
> If we login to other database in the time database D freeze the user
> screen
> when save,
> it works normally with input or save data to the system.
> Plz help and give some suggestions for us to solve the problem.
> Thx
> Jack
>

Problem installing some components SQL 2005

Hi,

I'm having trouble installing SQL2005 completely. I get a message:
"A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component."

It concerns "Integration services", "Notification services" and "Workstation Components, Books Online and Development Tools"

What should I do?

Regards,
Ronald

Here is the complete listing of summary.txt:

Microsoft SQL Server 2005 9.00.1399.06

==============================

OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)

Time : Sat Nov 12 21:29:32 2005

Machine : VL023188

Product : Microsoft SQL Server Setup Support Files (English)

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLSupport_1.log

--

Machine : VL023188

Product : Microsoft SQL Server Native Client

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLNCLI_1.log

--

Machine : VL023188

Product : Microsoft Office 2003 Web Components

Product Version : 11.0.6558.0

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_OWC11_1.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Backward compatibility

Product Version : 8.05.1054

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_BackwardsCompat_1.log

--

Machine : VL023188

Product : MSXML 6.0 Parser

Product Version : 6.00.3883.8

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_MSXML6_1.log

--

Machine : VL023188

Product : Microsoft SQL Server Setup Support Files (English)

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLSupport_2.log

--

Machine : VL023188

Product : Microsoft SQL Server Native Client

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLNCLI_2.log

--

Machine : VL023188

Product : Microsoft Office 2003 Web Components

Product Version : 11.0.6558.0

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_OWC11_2.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Backward compatibility

Product Version : 8.05.1054

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_BackwardsCompat_2.log

--

Machine : VL023188

Product : MSXML 6.0 Parser

Product Version : 6.00.3883.8

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_MSXML6_2.log

--

Machine : VL023188

Product : Microsoft SQL Server Setup Support Files (English)

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLSupport_3.log

--

Machine : VL023188

Product : Microsoft Office 2003 Web Components

Product Version : 11.0.6558.0

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_OWC11_3.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Backward compatibility

Product Version : 8.05.1054

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_BackwardsCompat_3.log

--

Machine : VL023188

Product : Microsoft SQL Server Setup Support Files (English)

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLSupport_4.log

--

Machine : VL023188

Product : Microsoft SQL Server Native Client

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLNCLI_3.log

--

Machine : VL023188

Product : Microsoft Office 2003 Web Components

Product Version : 11.0.6558.0

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_OWC11_4.log

--

Machine : VL023188

Product : Microsoft SQL Server VSS Writer

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SqlWriter_1.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Backward compatibility

Product Version : 8.05.1054

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_BackwardsCompat_4.log

--

Machine : VL023188

Product : MSXML 6.0 Parser

Product Version : 6.00.3883.8

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_MSXML6_3.log

--

Machine : VL023188

Product : Microsoft SQL Server Setup Support Files (English)

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLSupport_5.log

--

Machine : VL023188

Product : Microsoft SQL Server Native Client

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLNCLI_4.log

--

Machine : VL023188

Product : Microsoft Office 2003 Web Components

Product Version : 11.0.6558.0

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_OWC11_5.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Books Online (English)

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_BOL_1.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Backward compatibility

Product Version : 8.05.1054

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_BackwardsCompat_5.log

--

Machine : VL023188

Product : MSXML 6.0 Parser

Product Version : 6.00.3883.8

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_MSXML6_4.log

--

Machine : VL023188

Product : Integration Services

Error : A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component.

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Integration Services

Product Version : 9.00.1399.06

Install : Failed

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_DTS.log

Error Number : 1603

--

Machine : VL023188

Product : SQLXML4

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLXML4_1.log

--

Machine : VL023188

Product : Microsoft SQL Server 2005

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQL.log

--

Machine : VL023188

Product : SQLXML4

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_SQLXML4_2.log

--

Machine : VL023188

Product : Notification Services

Error : A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component.

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Notification Services

Product Version : 9.00.1399.06

Install : Failed

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_NS.log

Error Number : 1603

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Reporting Services

Product Version : 9.00.1399.06

Install : Successful

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_RS.log

--

Machine : VL023188

Product : Workstation Components, Books Online and Development Tools

Error : A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component.

--

Machine : VL023188

Product : Microsoft SQL Server 2005 Tools

Product Version : 9.00.1399.06

Install : Failed

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_VL023188_Tools.log

Error Number : 1603

--

SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

Let's start by looking at what's already installed on your machine. The error you're getting usually means the component is already installed. To figure out what's installed, go to Add/Remove Programs and find the entry for "SQL Server 2005". Select that entry and click Change. Once the dialog appears you should see a button named "Report". Click that button and you'll get a report detailing your installation. Select the contents of that report and copy/paste them into a reply here. Once we determine what you have installed we can figure out what you need to do.

Dan|||

Below the output of "Report". I also found out that there are a number of CTP rows in the add/remove software list. I thought I removed all SQL components but this morning after rebooting I discovered these components and I don't know where they come from. I have installed VS2005 also after installing SQL2005. Should I remove those CTP components? And in what order?
Perhaps you should also know that I removed all SQL branches in the registry (9.00....) because the installation of SQL2005 wouldn't start.
VL023188

The following components are installed on this server

MSSQLSERVER

Analysis Services

[Version: 9.00.1399.06 Edition: Developer Edition Patch level: 9.00.1399.06 Language: Engels (Verenigde Staten)]

Database Engine

[Version: 9.00.1399.06 Edition: Developer Edition Patch level: 9.00.1399.06 Language: Engels (Verenigde Staten)]

Reporting Services

[Version: 9.00.1399.06 Edition: Developer Edition Patch level: 9.00.1399.06 Language: Engels (Verenigde Staten)]

SQLEXPRESS

Database Engine

[Version: 9.00.1399.06 Edition: Express Edition Patch level: 9.00.1399.06 Language: Engels (Verenigde Staten)]

|||

Well, I managed to uninstall most of the CTP components. Just one is left that I cannot uninstall: Microsoft SQL Server Tools CTP. This one is looking into a directory that doesn't exist anymore. I can see that it was the SQL 2005 September CTP enterprise edition but I don't have that one anymore (also not available for subscribers?). How can I uninstall this one?

|||I found out that the report services weren't functioning very well (I was not able to open an existing report project). So I uninstalled the component reporting services (in add/remove, change on SQL2005). But after that I am not able to reinstall reporting services because:

Machine : VL023188
Product : Reporting Services

Error : An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
-
Machine : VL023188
Product : Microsoft SQL Server 2005 Reporting Services
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0023_VL023188_RS.log
Last Action : DetectInstanceClash
Error String : An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
Error Number : 28086
-

What to do?

|||

Plenty wrote:

Well, I managed to uninstall most of the CTP components. Just one is left that I cannot uninstall: Microsoft SQL Server Tools CTP. This one is looking into a directory that doesn't exist anymore. I can see that it was the SQL 2005 September CTP enterprise edition but I don't have that one anymore (also not available for subscribers?). How can I uninstall this one?

I got a solution for this problem:
http://blogs.msdn.com/brada/archive/2005/06/24/432209.aspx

This helped me, now I could install the tools

But the one above still isn't solved (reporting services, existing instance). How can I remove that exsiting instance?|||

Try the following:

1. Kill the service with command sc if it still exists.

2. Go to Registry editor, remove those registy keys related to the service. You need to search the whole regisgtry tree.

3. Reboot the machine.

problem inserting datetime

Since two days, I suddenly experience trouble inserting datetime values on my contracters sql server
As example I can created a table like this:
CREATE testDateTime
(dateTime DATETIME)
and insert:
insert testDateTime (dateTime)
values ('13-8-2005 11:56:39')
this works OK on my local Microsoft SQL Server 2000, but since two days not anymore on my contracters Microsoft SQL Server ("The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value")
Maybe they had an upgrade with changes in the way datetime values are handled? I sent an email to the administators of my contractors webserver, and I will put a question on a Microsoft SQL Server forum. I have the same problem with inserting smalldatetime valuesThe interpretation of the datetime value depends on the language and date format setting. For example, if you SET LANGUAGE to us_english then this will not work. You need to use the ISO format to make sure that the datetime value is interpreted correctly irrespective of language or date format setting. So do instead: '20050813T11:56:39'.|||Feel like reading some more? :)
http://www.karaszi.com/SQLServer/info_datetime.asp
http://www.sql-server-performance.com/fk_datetime.asp
--
Frank Kalis
Microsoft SQL Server MVP
http://www.insidesql.de
Ich unterstütze PASS Deutschland e.V. (http://www.sqlpass.de)