Showing posts with label error. Show all posts
Showing posts with label error. Show all posts

Friday, March 30, 2012

Having trouble getting SP from sql Server 2005 to work in SQL Server 2000

I am getting an error saying incorrect syntax near f

It works in SQL Server 2005, but I cannot get it to work in SQL Server 2000

The error appears to be in the section that I marked in Bold.

CREATE PROCEDURE [dbo].[pe_getReport]
-- Add the parameters for the stored procedure here
@.BranchID INT,
@.InvestorID INT,
@.Status INT,
@.QCAssigned INT,
@.LoanOfficer nvarChar(40),
@.FromCloseDate DateTime,
@.ToCloseDate DateTime,
@.OrderBy nvarChar(50)
AS
DECLARE
@.l_Sql NVarChar(4000),
@.l_OrderBy NVarChar(500),
@.l_OrderCol NVarChar(150),
@.l_CountSql NVarChar(4000),
@.l_Where NVarChar(4000),
@.l_SortDir nvarChar(4)

BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;

SET @.l_Where = N' Where 1=1'

IF (@.BranchID IS NOT NULL)
SET @.l_Where = @.l_Where + N' AND f.BranchID=' + CAST(@.BranchID As NVarChar)

IF (@.Status IS NOT NULL)
SET @.l_Where = @.l_Where + N' AND f.Status=' + CAST(@.Status As NVarChar)

IF (@.InvestorID IS NOT NULL)
SET @.l_Where = @.l_Where + N' AND f.InvestorID=' + CAST(@.InvestorID As NVarChar)

IF (@.QCAssigned IS NOT NULL)
SET @.l_Where = @.l_Where + N' AND f.QCAssigned=' + CAST(@.QCAssigned As NVarChar)

IF (@.LoanOfficer IS NOT NULL)
SET @.l_Where = @.l_Where + N' AND f.LoanOfficer LIKE ''' + @.LoanOfficer + '%'''

IF (@.FromCloseDate IS NOT NULL)
SET @.l_Where = @.l_Where + N' AND f.ClosingDate>=''' + CAST(@.FromCloseDate AS NVarChar) + ''''

IF (@.ToCloseDate IS NOT NULL)
SET @.l_Where = @.l_Where + N' AND f.ClosingDate<=''' + CAST(@.ToCloseDate AS NVarChar) + ''''

IF @.OrderBy IS NULL
SET @.OrderBy = 'DateEntered DESC'

SET @.l_SortDir = SUBSTRING(@.OrderBy, CHARINDEX(' ', @.OrderBy) + 1, LEN(@.OrderBy))
SET @.l_OrderCol = SUBSTRING(@.OrderBy, 1, NULLIF(CHARINDEX(' ', @.OrderBy) - 1, -1))
IF @.l_OrderCol = 'InvestorName'
SET @.l_OrderBy = 'i.InvestorName ' + @.l_SortDir
ELSE IF @.l_OrderCol = 'BName'
SET @.l_OrderBy = 'b.BName ' + @.l_SortDir
ELSE IF @.l_OrderCol = 'StatusDesc'
SET @.l_OrderBy = 's.StatusDesc ' + @.l_SortDir
ELSE IF @.l_OrderCol = 'QCAssigned'
SET @.l_OrderBy = 'q.LoginName ' + @.l_SortDir
ELSE SET @.l_OrderBy = 'f.' + @.l_OrderCol + ' ' + @.l_SortDir

SET @.l_CountSql = 'SELECT f.FundedID As FundedID FROM FundedInfo AS f LEFT OUTER JOIN
Investors AS i ON f.InvestorID = i.InvestorID LEFT OUTER JOIN
Branches AS b ON f.BranchID = b.BranchID LEFT OUTER JOIN
Status AS s ON f.Status = s.StatusID LEFT OUTER JOIN
QCLogins AS q f.QCAssigned = q.LoginID '
+ @.l_Where + ' ORDER BY ' + @.l_OrderBy

CREATE TABLE #RsltTable (ID int IDENTITY PRIMARY KEY, FundedID int)
INSERT INTO #RsltTable(FundedID)
EXECUTE (@.l_CountSql)

SELECT f.DateEntered As DateEntered, f.LastName As LastName, f.LoanNumber As LoanNumber,
f.LoanOfficer As LoanOfficer, f.ClosingDate As ClosingDate,
i.InvestorName As InvestorName, b.BName As BName, s.StatusDesc As StatusDesc,
q.LoginName As LoginName
FROM
FundedInfo AS f LEFT OUTER JOIN
Investors AS i ON f.InvestorID = i.InvestorID LEFT OUTER JOIN
Branches AS b ON f.BranchID = b.BranchID LEFT OUTER JOIN
Status AS s ON f.Status = s.StatusID LEFT OUTER JOIN
QCLogins As q ON f.QCAssigned = q.LoginID
WHERE FundedID IN(SELECT FundedID FROM #rsltTable)
ORDER BY
CASE @.OrderBy WHEN 'DateEntered ASC' THEN f.DateEntered END ASC,
CASE @.OrderBy WHEN 'DateEntered DESC' THEN f.DateEntered END DESC,
CASE @.OrderBy WHEN 'LastName ASC' THEN f.LastName END ASC,
CASE @.OrderBy WHEN 'LastName DESC' THEN f.LastName END DESC,
CASE @.OrderBy WHEN 'LoanNumber ASC' THEN f.LoanNumber END ASC,
CASE @.OrderBy WHEN 'LoanNumber DESC' THEN f.LoanNumber END DESC,
CASE @.OrderBy WHEN 'LoanOfficer ASC' THEN f.LoanOfficer END ASC,
CASE @.OrderBy WHEN 'LoanOfficer DESC' THEN f.LoanOfficer END DESC,
CASE @.OrderBy WHEN 'ClosingDate ASC' THEN f.ClosingDate END ASC,
CASE @.OrderBy WHEN 'ClosingDate DESC' THEN f.ClosingDate END DESC,
CASE @.OrderBy WHEN 'InvestorName ASC' THEN i.InvestorName END ASC,
CASE @.OrderBy WHEN 'InvestorName DESC' THEN i.InvestorName END DESC,
CASE @.OrderBy WHEN 'BName ASC' THEN b.BName END ASC,
CASE @.OrderBy WHEN 'BName DESC' THEN b.BName END DESC,
CASE @.OrderBy WHEN 'StatusDesc ASC' THEN s.StatusDesc END ASC,
CASE @.OrderBy WHEN 'StatusDesc DESC' THEN s.StatusDesc END DESC,
CASE @.OrderBy WHEN 'LoginName ASC' THEN q.LoginName END ASC,
CASE @.OrderBy WHEN 'LoginName DESC' THEN q.LoginName END DESC
END
GO

Do a PRINT @.l_CountSql before you EXEC the SQL. That can help you debug the SQL Statement that is being formed.|||Thanks, I am blind... I was missing the 'ON' in the last LEFT OUTER JOIN

Having problems with text datatype!

Hi,

pls can anyone help me to solve the error generated by this query,

set ANSI_NULLS ON

set QUOTED_IDENTIFIER ON

GO

ALTER PROCEDURE [dbo].[spAP_PS_VENDOR_CONVER]

AS

SET NOCOUNT ON

SELECT UPPER(SETID) AS SETID

,UPPER(VENDOR_ID)AS VENDOR_ID

,CONVER_DT

,CONVER_SEQ_NUM

,CNTCT_SEQ_NUM

,UPPER(CONVER_TOPIC) AS CONVER_TOPIC

,UPPER(OPRID)AS OPRID

,REVIEW_DAYS

,REVIEW_DATE

,REVIEW_NEXT_DATE

,UPPER(KEYWORD1) AS KEYWORD1

,UPPER(KEYWORD2) AS KEYWORD2

,UPPER(KEYWORD3) AS KEYWORD3

,CAST(ISNULL(DESCRLONG,'') AS VARCHAR(200)) AS DESCRLONG

,PROCESS_INSTANCE

,MAX(EY_SF_UPDATE_DTTM) AS EY_SF_UPDATE_DTTM

,PROCESS_DTTM

,CREATED_DTTM

,UPPER(EY_SF_ACTN_FLG) AS EY_SF_ACTN_FLG

,UPPER(EY_SF_STATUS) AS EY_SF_STATUS

FROM Metastorm.dbo.AP_PS_VENDOR_CONVER

WHERE EY_SF_STATUS='N'

GROUP BY SETID,VENDOR_ID,CONVER_DT,CONVER_SEQ_NUM,CNTCT_SEQ_NUM,CONVER_TOPIC,OPRID

,REVIEW_DAYS,REVIEW_DATE,REVIEW_NEXT_DATE,KEYWORD1,KEYWORD2,KEYWORD3,DESCRLONG

,PROCESS_INSTANCE,PROCESS_DTTM,CREATED_DTTM,EY_SF_ACTN_FLG

,EY_SF_STATUS

SET NOCOUNT OFF

Msg 306, Level 16, State 2, Procedure spAP_PS_VENDOR_CONVER, Line 4

The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator.

Regards,

Sg

sorry forgot to tell that the descrlong is a text column

Regards,

sg

|||

You couldn't use text, ntext, image datatype in group by.

Try use following statement in group by:

Code Snippet

GROUP BY CAST(ISNULL(DESCRLONG,'') AS VARCHAR(200)), .....

|||

Hi Konstantin,

Thanks a lot.

Regards,

Sg

Wednesday, March 28, 2012

Having Problems Installing SQL Server 2005 Express

I am running WinXP Home edition, and I was trying to install SQL Server Express, but the error message is too vague for me fix. It says my computer lacks the "Service Pack Requirements" to run the software, but I'm afraid I don't know which service pack requirements the error is talking about. What Service Pack do I need to download?

Here is the report from the install:

System Configuration Check

- WMI Service Requirement (Success)

Messages

WMI Service Requirement

Check Passed

- MSXML Requirement (Success)

Messages

MSXML Requirement

Check Passed

- Operating System Minimum Level Requirement (Success)

Messages

Operating System Minimum Level Requirement

Check Passed

- Operating System Service Pack Level Requirement. (Error)

MessagesOperating System Service Pack Level Requirement.

The current operating system does not meet Service Pack level requirements for this SQL Server release. Install the most recent Service Pack from the Microsoft download center at http://go.microsoft.com/fwlink/?LinkId=50380, and then run SQL Server Setup again. For hardware and software requirements, see the readme file or SQL Server Books Online.

- SQL Server Edition Operating System Compatibility (Success)

Messages

SQL Server Edition Operating System Compatibility

Check Passed

- Minimum Hardware Requirement (Warning)

Messages

Minimum Hardware Requirement

The current system does not meet the recommended hardware requirements for this SQL Server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online.

- Pending Reboot Requirement (Success)

Messages

Pending Reboot Requirement

Check Passed

- Default Installation Path Permission Requirement (Success)

Messages

Default Installation Path Permission Requirement

Check Passed

- Internet Explorer Requirement (Success)

Messages

Internet Explorer Requirement

Check Passed

- COM Plus Catalog Requirement (Success)

Messages

COM Plus Catalog Requirement

Check Passed

- ASP.Net Version Registration Requirement (Success)

Messages

ASP.Net Version Registration Requirement

Check Passed

- Minimum MDAC Version Requirement (Success)

Messages

Minimum MDAC Version Requirement

Check Passed

- Edition Change Check (Success)

Messages

Edition Change Check

Check Passed

THe same requirements for Windows XP Professional applies to XP Home:

http://www.microsoft.com/sql/editions/express/sysreqs.mspx

YOu nedd SP2 in order to have the setup working.

HTH, Jens Suessmeyer.


http://www.sqlserver2005.de

|||I am having the same problem. But I have XP Professional SP2 installed. What more could I need?|||I don′t know if that also applies to the .NET Framework existance, because I already has it on my computers. But do you have .NET Framework installed (2.0) ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I installed the Sp2 and problem resolved

Having Problems Installing SQL Server 2005 Express

I am running WinXP Home edition, and I was trying to install SQL Server Express, but the error message is too vague for me fix. It says my computer lacks the "Service Pack Requirements" to run the software, but I'm afraid I don't know which service pack requirements the error is talking about. What Service Pack do I need to download?

Here is the report from the install:

System Configuration Check

- WMI Service Requirement (Success)

Messages

WMI Service Requirement

Check Passed

- MSXML Requirement (Success)

Messages

MSXML Requirement

Check Passed

- Operating System Minimum Level Requirement (Success)

Messages

Operating System Minimum Level Requirement

Check Passed

- Operating System Service Pack Level Requirement. (Error)

MessagesOperating System Service Pack Level Requirement.

The current operating system does not meet Service Pack level requirements for this SQL Server release. Install the most recent Service Pack from the Microsoft download center at http://go.microsoft.com/fwlink/?LinkId=50380, and then run SQL Server Setup again. For hardware and software requirements, see the readme file or SQL Server Books Online.

- SQL Server Edition Operating System Compatibility (Success)

Messages

SQL Server Edition Operating System Compatibility

Check Passed

- Minimum Hardware Requirement (Warning)

Messages

Minimum Hardware Requirement

The current system does not meet the recommended hardware requirements for this SQL Server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online.

- Pending Reboot Requirement (Success)

Messages

Pending Reboot Requirement

Check Passed

- Default Installation Path Permission Requirement (Success)

Messages

Default Installation Path Permission Requirement

Check Passed

- Internet Explorer Requirement (Success)

Messages

Internet Explorer Requirement

Check Passed

- COM Plus Catalog Requirement (Success)

Messages

COM Plus Catalog Requirement

Check Passed

- ASP.Net Version Registration Requirement (Success)

Messages

ASP.Net Version Registration Requirement

Check Passed

- Minimum MDAC Version Requirement (Success)

Messages

Minimum MDAC Version Requirement

Check Passed

- Edition Change Check (Success)

Messages

Edition Change Check

Check Passed

THe same requirements for Windows XP Professional applies to XP Home:

http://www.microsoft.com/sql/editions/express/sysreqs.mspx

YOu nedd SP2 in order to have the setup working.

HTH, Jens Suessmeyer.


http://www.sqlserver2005.de

|||I am having the same problem. But I have XP Professional SP2 installed. What more could I need?|||I don′t know if that also applies to the .NET Framework existance, because I already has it on my computers. But do you have .NET Framework installed (2.0) ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I installed the Sp2 and problem resolved

Having Problems Installing SQL Server 2005 Express

I am running WinXP Home edition, and I was trying to install SQL Server Express, but the error message is too vague for me fix. It says my computer lacks the "Service Pack Requirements" to run the software, but I'm afraid I don't know which service pack requirements the error is talking about. What Service Pack do I need to download?

Here is the report from the install:

System Configuration Check

- WMI Service Requirement (Success)

Messages

WMI Service Requirement

Check Passed

- MSXML Requirement (Success)

Messages

MSXML Requirement

Check Passed

- Operating System Minimum Level Requirement (Success)

Messages

Operating System Minimum Level Requirement

Check Passed

- Operating System Service Pack Level Requirement. (Error)

MessagesOperating System Service Pack Level Requirement.

The current operating system does not meet Service Pack level requirements for this SQL Server release. Install the most recent Service Pack from the Microsoft download center at http://go.microsoft.com/fwlink/?LinkId=50380, and then run SQL Server Setup again. For hardware and software requirements, see the readme file or SQL Server Books Online.

- SQL Server Edition Operating System Compatibility (Success)

Messages

SQL Server Edition Operating System Compatibility

Check Passed

- Minimum Hardware Requirement (Warning)

Messages

Minimum Hardware Requirement

The current system does not meet the recommended hardware requirements for this SQL Server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online.

- Pending Reboot Requirement (Success)

Messages

Pending Reboot Requirement

Check Passed

- Default Installation Path Permission Requirement (Success)

Messages

Default Installation Path Permission Requirement

Check Passed

- Internet Explorer Requirement (Success)

Messages

Internet Explorer Requirement

Check Passed

- COM Plus Catalog Requirement (Success)

Messages

COM Plus Catalog Requirement

Check Passed

- ASP.Net Version Registration Requirement (Success)

Messages

ASP.Net Version Registration Requirement

Check Passed

- Minimum MDAC Version Requirement (Success)

Messages

Minimum MDAC Version Requirement

Check Passed

- Edition Change Check (Success)

Messages

Edition Change Check

Check Passed

THe same requirements for Windows XP Professional applies to XP Home:

http://www.microsoft.com/sql/editions/express/sysreqs.mspx

YOu nedd SP2 in order to have the setup working.

HTH, Jens Suessmeyer.


http://www.sqlserver2005.de

|||I am having the same problem. But I have XP Professional SP2 installed. What more could I need?|||I don′t know if that also applies to the .NET Framework existance, because I already has it on my computers. But do you have .NET Framework installed (2.0) ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I installed the Sp2 and problem resolved

Having problems deploying a report.

I am working with a MS 2005 SQL Server database. I have the following error message. A connection could not be made to the report server http://localhost/ReportServer. I am trying to develop these on a network server. Is this a configuration issue, that it is expecting this on the local machine.

Thanks!

Terry B

Hi,

are you sure that the user (which deploy the report) have access rights to the report server. You can administrate this under http://localhost/reports and then under security, there you must add the AD-user.

I hope this help.

|||

When I go on the internet and type in Http://localhost I receive a not found error message. It claims to be Under Construction and references the IIS Help. But other reports from the server do deploy and I cannot see them from either machine

Thanks!

Terry

|||

Hi,

when localhost the SQL-Reporting-Server is, you must take the url http://localhost/Reports! It is importen to give the subweb Reports to go to the administrationwebsite of the reporting server...

Having problem with my server

I just currently installed Microsoft studio express which includes SQL server and i get this error Server Error in '/WebSite1' Application. it also states "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding" I am wondering do i have to have IIS on to run SQL server 2005 express adition.Sad

I am also having problem with SQL Express installation. After installing it, and configuring with SQL surface area for also remote access via tcp or pipe I still get the message:

>sqlcmd

HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

|||Make sure you have followed all of the steps at http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx in order to enable remote connectivity.

having problem while connecting sql 2000

im using sql server 2000 and i m facing this problem

plz tell me why is this

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"

You failed to connect into the SQL server. I think the IP or the host name is wrong.

Check the following site for connectionstrings

www.connectionstrings.com

Regards

|||Also make sure Named Pipes and TCP/IP network libraries are enabled for the SQL2000 instance. You can easily archieve this in Server Network Utility.|||

hai dude

i want to mentions one thing that i have previously used the same connection class made my self for connecting to the db..

but now on new another pc with new installation of sql server ,,having the same previously used setting.,,its not woking,,,

one thing more im not usgin ip based connection string ...

|||Why not use IP based connection string? IP is often more reliable than machine name, for example when DNS does not work properly so the machine name can't be intepreted?to IP.|||

yah thanks dude

its done

Monday, March 26, 2012

HAving a problem

I am using Windows 2003 server. When iI try to start the sql service using a user account I get an error and cannot start service. When I us a local system account I have no problems. Any ideas on why this is happenning. Thanks.Can you post the error? Are you trying to use domain account,and if yes, - is DC available?

Have you ever got this TempDB error ?

My SQL Server 7.0 (with Service Pack 3) server has 3 drives : C, D, E.
By default, the TempDB locates at C drive and I increased its size by adding
2 more files (1 for TempDB database file and 1 for Temp log) at D drive.
However, I don't know why the TempDB always cannot recognize these 2 D-drive
files when I come to office every morning.
The 2 D-drive files still exist in D drive but from the SQL Enterprise
Manager tells me the TempDB only has C-drive files.
Why, why the D-drive file pointers always become invvalid ?
Hi,
Can you execute the below statement in query analyzer:-
sp_helpdb tempdb
If it is not showing D drive file, then you have not added the new files
properly.
Refer ALTER DATABASE in books online to add a new file to D Drive. (You can
also use Enterprise manager)
Thanks
Hari
MCDBA
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c97hfp$rtr2@.imsp212.netvigator.com...
> My SQL Server 7.0 (with Service Pack 3) server has 3 drives : C, D, E.
> By default, the TempDB locates at C drive and I increased its size by
adding
> 2 more files (1 for TempDB database file and 1 for Temp log) at D drive.
> However, I don't know why the TempDB always cannot recognize these 2
D-drive
> files when I come to office every morning.
> The 2 D-drive files still exist in D drive but from the SQL Enterprise
> Manager tells me the TempDB only has C-drive files.
> Why, why the D-drive file pointers always become invvalid ?
>
>
|||What does "cannot recognize" mean? Do you get an error message (as your
subject implies)? If so, what is it?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c97hfp$rtr2@.imsp212.netvigator.com...
> My SQL Server 7.0 (with Service Pack 3) server has 3 drives : C, D, E.
> By default, the TempDB locates at C drive and I increased its size by
adding
> 2 more files (1 for TempDB database file and 1 for Temp log) at D drive.
> However, I don't know why the TempDB always cannot recognize these 2
D-drive
> files when I come to office every morning.
> The 2 D-drive files still exist in D drive but from the SQL Enterprise
> Manager tells me the TempDB only has C-drive files.
> Why, why the D-drive file pointers always become invvalid ?
>
>
|||It means in SQL Enterprise Manager, it only says the TempDB has 2 C-drive
files but not have the 2 D-drive files I added last night.
However, the 2 D-drive files still exist in the D drive when I used File
Explorer to search them.
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:#uPqAqMREHA.2972@.TK2MSFTNGP09.phx.gbl...
> What does "cannot recognize" mean? Do you get an error message (as your
> subject implies)? If so, what is it?
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
> "cpchan" <cpchaney@.netvigator.com> wrote in message
> news:c97hfp$rtr2@.imsp212.netvigator.com...
> adding
> D-drive
>
|||Hi,
Can you execute the below statement in query analyzer:-
sp_helpdb tempdb
If it is not showing D drive file, then you have not added the new files
properly. Please recreate the files using using ALTER DATABASE command.
Thanks
Hari
MCDBA
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ezZkyaMREHA.3944@.TK2MSFTNGP11.phx.gbl...
> Hi,
> Can you execute the below statement in query analyzer:-
> sp_helpdb tempdb
> If it is not showing D drive file, then you have not added the new files
> properly.
> Refer ALTER DATABASE in books online to add a new file to D Drive. (You
can
> also use Enterprise manager)
> Thanks
> Hari
> MCDBA
>
> "cpchan" <cpchaney@.netvigator.com> wrote in message
> news:c97hfp$rtr2@.imsp212.netvigator.com...
> adding
> D-drive
>

Friday, March 23, 2012

Have you ever got this TempDB error ?

My SQL Server 7.0 (with Service Pack 3) server has 3 drives : C, D, E.
By default, the TempDB locates at C drive and I increased its size by adding
2 more files (1 for TempDB database file and 1 for Temp log) at D drive.
However, I don't know why the TempDB always cannot recognize these 2 D-drive
files when I come to office every morning.
The 2 D-drive files still exist in D drive but from the SQL Enterprise
Manager tells me the TempDB only has C-drive files.
Why, why the D-drive file pointers always become invvalid ?Hi,
Can you execute the below statement in query analyzer:-
sp_helpdb tempdb
If it is not showing D drive file, then you have not added the new files
properly.
Refer ALTER DATABASE in books online to add a new file to D Drive. (You can
also use Enterprise manager)
Thanks
Hari
MCDBA
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c97hfp$rtr2@.imsp212.netvigator.com...
> My SQL Server 7.0 (with Service Pack 3) server has 3 drives : C, D, E.
> By default, the TempDB locates at C drive and I increased its size by
adding
> 2 more files (1 for TempDB database file and 1 for Temp log) at D drive.
> However, I don't know why the TempDB always cannot recognize these 2
D-drive
> files when I come to office every morning.
> The 2 D-drive files still exist in D drive but from the SQL Enterprise
> Manager tells me the TempDB only has C-drive files.
> Why, why the D-drive file pointers always become invvalid ?
>
>|||What does "cannot recognize" mean? Do you get an error message (as your
subject implies)? If so, what is it?
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c97hfp$rtr2@.imsp212.netvigator.com...
> My SQL Server 7.0 (with Service Pack 3) server has 3 drives : C, D, E.
> By default, the TempDB locates at C drive and I increased its size by
adding
> 2 more files (1 for TempDB database file and 1 for Temp log) at D drive.
> However, I don't know why the TempDB always cannot recognize these 2
D-drive
> files when I come to office every morning.
> The 2 D-drive files still exist in D drive but from the SQL Enterprise
> Manager tells me the TempDB only has C-drive files.
> Why, why the D-drive file pointers always become invvalid ?
>
>|||It means in SQL Enterprise Manager, it only says the TempDB has 2 C-drive
files but not have the 2 D-drive files I added last night.
However, the 2 D-drive files still exist in the D drive when I used File
Explorer to search them.
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:#uPqAqMREHA.2972@.TK2MSFTNGP09.phx.gbl...
> What does "cannot recognize" mean? Do you get an error message (as your
> subject implies)? If so, what is it?
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
> "cpchan" <cpchaney@.netvigator.com> wrote in message
> news:c97hfp$rtr2@.imsp212.netvigator.com...
> > My SQL Server 7.0 (with Service Pack 3) server has 3 drives : C, D, E.
> > By default, the TempDB locates at C drive and I increased its size by
> adding
> > 2 more files (1 for TempDB database file and 1 for Temp log) at D drive.
> >
> > However, I don't know why the TempDB always cannot recognize these 2
> D-drive
> > files when I come to office every morning.
> > The 2 D-drive files still exist in D drive but from the SQL Enterprise
> > Manager tells me the TempDB only has C-drive files.
> >
> > Why, why the D-drive file pointers always become invvalid ?
> >
> >
> >
>|||Hi,
Can you execute the below statement in query analyzer:-
sp_helpdb tempdb
If it is not showing D drive file, then you have not added the new files
properly. Please recreate the files using using ALTER DATABASE command.
Thanks
Hari
MCDBA
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ezZkyaMREHA.3944@.TK2MSFTNGP11.phx.gbl...
> Hi,
> Can you execute the below statement in query analyzer:-
> sp_helpdb tempdb
> If it is not showing D drive file, then you have not added the new files
> properly.
> Refer ALTER DATABASE in books online to add a new file to D Drive. (You
can
> also use Enterprise manager)
> Thanks
> Hari
> MCDBA
>
> "cpchan" <cpchaney@.netvigator.com> wrote in message
> news:c97hfp$rtr2@.imsp212.netvigator.com...
> > My SQL Server 7.0 (with Service Pack 3) server has 3 drives : C, D, E.
> > By default, the TempDB locates at C drive and I increased its size by
> adding
> > 2 more files (1 for TempDB database file and 1 for Temp log) at D drive.
> >
> > However, I don't know why the TempDB always cannot recognize these 2
> D-drive
> > files when I come to office every morning.
> > The 2 D-drive files still exist in D drive but from the SQL Enterprise
> > Manager tells me the TempDB only has C-drive files.
> >
> > Why, why the D-drive file pointers always become invvalid ?
> >
> >
> >
>

Have you ever got this TempDB error ?

My SQL Server 7.0 (with Service Pack 3) server has 3 drives : C, D, E.
By default, the TempDB locates at C drive and I increased its size by adding
2 more files (1 for TempDB database file and 1 for Temp log) at D drive.
However, I don't know why the TempDB always cannot recognize these 2 D-drive
files when I come to office every morning.
The 2 D-drive files still exist in D drive but from the SQL Enterprise
Manager tells me the TempDB only has C-drive files.
Why, why the D-drive file pointers always become invvalid ?Hi,
Can you execute the below statement in query analyzer:-
sp_helpdb tempdb
If it is not showing D drive file, then you have not added the new files
properly.
Refer ALTER DATABASE in books online to add a new file to D Drive. (You can
also use Enterprise manager)
Thanks
Hari
MCDBA
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c97hfp$rtr2@.imsp212.netvigator.com...
> My SQL Server 7.0 (with Service Pack 3) server has 3 drives : C, D, E.
> By default, the TempDB locates at C drive and I increased its size by
adding
> 2 more files (1 for TempDB database file and 1 for Temp log) at D drive.
> However, I don't know why the TempDB always cannot recognize these 2
D-drive
> files when I come to office every morning.
> The 2 D-drive files still exist in D drive but from the SQL Enterprise
> Manager tells me the TempDB only has C-drive files.
> Why, why the D-drive file pointers always become invvalid ?
>
>|||What does "cannot recognize" mean? Do you get an error message (as your
subject implies)? If so, what is it?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c97hfp$rtr2@.imsp212.netvigator.com...
> My SQL Server 7.0 (with Service Pack 3) server has 3 drives : C, D, E.
> By default, the TempDB locates at C drive and I increased its size by
adding
> 2 more files (1 for TempDB database file and 1 for Temp log) at D drive.
> However, I don't know why the TempDB always cannot recognize these 2
D-drive
> files when I come to office every morning.
> The 2 D-drive files still exist in D drive but from the SQL Enterprise
> Manager tells me the TempDB only has C-drive files.
> Why, why the D-drive file pointers always become invvalid ?
>
>

have a problem to browse the data in analysis server

:mad: Dear Sir/Madam,

I have a problem to browse the data in analysis server, it displayed: unspecified error, my os is windows xp with sp1 and sql server2000 installed, Do i need to install AS SP3 on the server, but, what are AS SP3 stand for, any other solution?

Rgds,
chenwhat are AS SP3 stand for, any other solution?AS SP3 would be Analysis Services, Service Pack 3 (http://www.microsoft.com/sql/downloads/2000/sp3.asp)

-PatP

Monday, March 19, 2012

Has anyone ever seen this fatal error?

We are getting the following error after execcuting an SP
on one of our clusters:
Server: Msg 7105, Level 22, State 6, Line 8
Page (1:16750), slot 4 for text, ntext, or image node does
not exist.
ODBC: Msg 0, Level 16, State 1
Communication link failure
Connection Broken
We are running SQL Server 2000 with SP3.
DBCC CHECKDB showed a problem with an index which we fixed
but the error still shows when we run the SP. DBCC
CHECKDB now shows no problems.
Is there any other way to track down this problem and/or
repair it?To resolve this problem, obtain the lates service pack for
Microsoft SQL Server 2000.
To work around the problem, either:
- Insert a dummy row in the table to import into so that
the table is not empty, and then delete the dummy row
after you import the data.
-or-
- Do not use the TABLOCK hint.
This posting is provided "AS IS" with no warranties, and
confers no rights.
http://www.microsoft.com/info/cpyright.htm
>--Original Message--
>We are getting the following error after execcuting an SP
>on one of our clusters:
>Server: Msg 7105, Level 22, State 6, Line 8
>Page (1:16750), slot 4 for text, ntext, or image node
does
>not exist.
>ODBC: Msg 0, Level 16, State 1
>Communication link failure
>Connection Broken
>We are running SQL Server 2000 with SP3.
>DBCC CHECKDB showed a problem with an index which we
fixed
>but the error still shows when we run the SP. DBCC
>CHECKDB now shows no problems.
>Is there any other way to track down this problem and/or
>repair it?
>
>.
>

Has anyone ever seen this error before?

A google search turned up nothing when I searched for this.
Is it saying that if my total VARCHARs for all columns in a row add up
to more than 8060, then it can't do it?
I've never heard of such a limitation before!
ALTER TABLE dat_table ADD some_stuff VARCHAR(4000) DEFAULT NULL NULL;
Warning: The table 'dat_table' has been created but its maximum row
size (17500) exceeds the maximum number of bytes per row (8060). INSERT
or UPDATE of a row in this table will fail if the resulting row length
exceeds 8060 bytes.
Does any guru have knowledge of this?
Thanks,
Stewart>A google search turned up nothing when I searched for this.
You should have gotten many hits. Perhaps you inadvertently included the
table name or maximum row size in the search. This is also well documented
in the SQL Server Books Online.
> Is it saying that if my total VARCHARs for all columns in a row add up
> to more than 8060, then it can't do it?
Not exactly. The ALTER TABLE succeeds but the warning message indicates
that the total row size has the *potential* to exceed the 8060 max. If you
later try to insert a row that requires more than 8060 bytes of actual data,
the insert will fail. Other inserts will succeed.
BTW, SQL 2005 provides some relief. When the combined widths exceed the
8060, overflow data are stored separately. However, there more I/O is
required since more pages need to be accessed.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Stewart" <stewart.cambridge@.gmail.com> wrote in message
news:1154604543.119450.193230@.75g2000cwc.googlegroups.com...
>A google search turned up nothing when I searched for this.
> Is it saying that if my total VARCHARs for all columns in a row add up
> to more than 8060, then it can't do it?
> I've never heard of such a limitation before!
> ALTER TABLE dat_table ADD some_stuff VARCHAR(4000) DEFAULT NULL NULL;
> Warning: The table 'dat_table' has been created but its maximum row
> size (17500) exceeds the maximum number of bytes per row (8060). INSERT
> or UPDATE of a row in this table will fail if the resulting row length
> exceeds 8060 bytes.
> Does any guru have knowledge of this?
> Thanks,
> Stewart
>|||Thank you Dan.
Useful to know.
Dan Guzman wrote:
> >A google search turned up nothing when I searched for this.
> You should have gotten many hits. Perhaps you inadvertently included the
> table name or maximum row size in the search. This is also well documented
> in the SQL Server Books Online.
> > Is it saying that if my total VARCHARs for all columns in a row add up
> > to more than 8060, then it can't do it?
> Not exactly. The ALTER TABLE succeeds but the warning message indicates
> that the total row size has the *potential* to exceed the 8060 max. If you
> later try to insert a row that requires more than 8060 bytes of actual data,
> the insert will fail. Other inserts will succeed.
> BTW, SQL 2005 provides some relief. When the combined widths exceed the
> 8060, overflow data are stored separately. However, there more I/O is
> required since more pages need to be accessed.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
>|||From: S Karthikeyan
Hi,
SQL Server can only have 8060 bytes in a row. Incase you want to exceed
this
limit try using image, text etc as the data types.
This is because a SQL data page is 8k in size i.e. 8192 bytes...
Approximately 132 bytes are used for storing information about the rows
like
headers, offset etc.
But if you try to insert/update with more than 8060 bytes in a row, SQL
will
automatically truncate the row to fit within 8060 bytes.
Thank you.
Regards,
Karthik|||> But if you try to insert/update with more than 8060 bytes in a row, SQL
> will
> automatically truncate the row to fit within 8060 bytes.
No, this is not the case. The insert will fail if you try to insert a row
with more than 8060 bytes (including overhead):
CREATE TABLE dbo.BigRowTable
(
Col1 varchar(8000),
Col2 varchar(8000)
)
--no problem
INSERT INTO dbo.BigRowTable (col1, col2)
VALUES(REPLICATE('x', 8000), REPLICATE('x', 47))
--fails
INSERT INTO dbo.BigRowTable (col1, col2)
VALUES(REPLICATE('x', 8000), REPLICATE('x', 48))
SELECT COUNT(*) FROM dbo.BigRowTable
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Stewart" <stewart.cambridge@.gmail.com> wrote in message
news:1154686180.641004.144020@.b28g2000cwb.googlegroups.com...
> From: S Karthikeyan
> Hi,
> SQL Server can only have 8060 bytes in a row. Incase you want to exceed
> this
> limit try using image, text etc as the data types.
> This is because a SQL data page is 8k in size i.e. 8192 bytes...
> Approximately 132 bytes are used for storing information about the rows
> like
> headers, offset etc.
> But if you try to insert/update with more than 8060 bytes in a row, SQL
> will
> automatically truncate the row to fit within 8060 bytes.
> Thank you.
> Regards,
> Karthik
>

Has anyone ever seen this error before?

A google search turned up nothing when I searched for this.
Is it saying that if my total VARCHARs for all columns in a row add up
to more than 8060, then it can't do it?
I've never heard of such a limitation before!
ALTER TABLE dat_table ADD some_stuff VARCHAR(4000) DEFAULT NULL NULL;
Warning: The table 'dat_table' has been created but its maximum row
size (17500) exceeds the maximum number of bytes per row (8060). INSERT
or UPDATE of a row in this table will fail if the resulting row length
exceeds 8060 bytes.
Does any guru have knowledge of this?
Thanks,
Stewart>A google search turned up nothing when I searched for this.
You should have gotten many hits. Perhaps you inadvertently included the
table name or maximum row size in the search. This is also well documented
in the SQL Server Books Online.

> Is it saying that if my total VARCHARs for all columns in a row add up
> to more than 8060, then it can't do it?
Not exactly. The ALTER TABLE succeeds but the warning message indicates
that the total row size has the *potential* to exceed the 8060 max. If you
later try to insert a row that requires more than 8060 bytes of actual data,
the insert will fail. Other inserts will succeed.
BTW, SQL 2005 provides some relief. When the combined widths exceed the
8060, overflow data are stored separately. However, there more I/O is
required since more pages need to be accessed.
Hope this helps.
Dan Guzman
SQL Server MVP
"Stewart" <stewart.cambridge@.gmail.com> wrote in message
news:1154604543.119450.193230@.75g2000cwc.googlegroups.com...
>A google search turned up nothing when I searched for this.
> Is it saying that if my total VARCHARs for all columns in a row add up
> to more than 8060, then it can't do it?
> I've never heard of such a limitation before!
> ALTER TABLE dat_table ADD some_stuff VARCHAR(4000) DEFAULT NULL NULL;
> Warning: The table 'dat_table' has been created but its maximum row
> size (17500) exceeds the maximum number of bytes per row (8060). INSERT
> or UPDATE of a row in this table will fail if the resulting row length
> exceeds 8060 bytes.
> Does any guru have knowledge of this?
> Thanks,
> Stewart
>|||Thank you Dan.
Useful to know.
Dan Guzman wrote:
> You should have gotten many hits. Perhaps you inadvertently included the
> table name or maximum row size in the search. This is also well documente
d
> in the SQL Server Books Online.
>
> Not exactly. The ALTER TABLE succeeds but the warning message indicates
> that the total row size has the *potential* to exceed the 8060 max. If yo
u
> later try to insert a row that requires more than 8060 bytes of actual dat
a,
> the insert will fail. Other inserts will succeed.
> BTW, SQL 2005 provides some relief. When the combined widths exceed the
> 8060, overflow data are stored separately. However, there more I/O is
> required since more pages need to be accessed.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
>|||From: S Karthikeyan
Hi,
SQL Server can only have 8060 bytes in a row. Incase you want to exceed
this
limit try using image, text etc as the data types.
This is because a SQL data page is 8k in size i.e. 8192 bytes...
Approximately 132 bytes are used for storing information about the rows
like
headers, offset etc.
But if you try to insert/update with more than 8060 bytes in a row, SQL
will
automatically truncate the row to fit within 8060 bytes.
Thank you.
Regards,
Karthik|||> But if you try to insert/update with more than 8060 bytes in a row, SQL
> will
> automatically truncate the row to fit within 8060 bytes.
No, this is not the case. The insert will fail if you try to insert a row
with more than 8060 bytes (including overhead):
CREATE TABLE dbo.BigRowTable
(
Col1 varchar(8000),
Col2 varchar(8000)
)
--no problem
INSERT INTO dbo.BigRowTable (col1, col2)
VALUES(REPLICATE('x', 8000), REPLICATE('x', 47))
--fails
INSERT INTO dbo.BigRowTable (col1, col2)
VALUES(REPLICATE('x', 8000), REPLICATE('x', 48))
SELECT COUNT(*) FROM dbo.BigRowTable
Hope this helps.
Dan Guzman
SQL Server MVP
"Stewart" <stewart.cambridge@.gmail.com> wrote in message
news:1154686180.641004.144020@.b28g2000cwb.googlegroups.com...
> From: S Karthikeyan
> Hi,
> SQL Server can only have 8060 bytes in a row. Incase you want to exceed
> this
> limit try using image, text etc as the data types.
> This is because a SQL data page is 8k in size i.e. 8192 bytes...
> Approximately 132 bytes are used for storing information about the rows
> like
> headers, offset etc.
> But if you try to insert/update with more than 8060 bytes in a row, SQL
> will
> automatically truncate the row to fit within 8060 bytes.
> Thank you.
> Regards,
> Karthik
>

Wednesday, March 7, 2012

Hard Code Native Error code in program?

Using VB 6, sp6,
On sql server 2000 (sp4)
When I try to establish a connection to the database
from a VB 6 program using ADO, I get a similar message
if the UserID does not exist or if the UserID does exist
but does not have the permission to the database.
The NativeError number is different,
NativeError - 18456 The UserID does not exist
NativeError - 4060 The UserID exists, but does not have permission
to the database.
Can I hard code the NativeError number in my VB 6
program to determine exactly what happened,
(the UserID did not exist or the UserID does exist but
does not have the proper permission.)
I worry that the code number might change in a future
version of sql server.
I hate to do this but there is no other way to determine
exactly what happened.
Thanks in Advance,
Laurence Nuttall
Programmer Analyst III
UCLA - Division of Continuing EducationIt's unlikely that the error codes would change. Could happen, but more
probable that additional codes would be added for other (and new)
situations.
If you are concerned, you could use a config file, and put the codes in the
config file. Have the app read the config file at start up and hold the
error codes in global variables. (An xml file works good for that.)
Otherwise, set them up as constants.
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Larry" <bliff@.Blifff.com> wrote in message
news:OlggCs6mGHA.2360@.TK2MSFTNGP04.phx.gbl...
> Using VB 6, sp6,
> On sql server 2000 (sp4)
> When I try to establish a connection to the database
> from a VB 6 program using ADO, I get a similar message
> if the UserID does not exist or if the UserID does exist
> but does not have the permission to the database.
> The NativeError number is different,
> NativeError - 18456 The UserID does not exist
> NativeError - 4060 The UserID exists, but does not have permission
> to the database.
> Can I hard code the NativeError number in my VB 6
> program to determine exactly what happened,
> (the UserID did not exist or the UserID does exist but
> does not have the proper permission.)
> I worry that the code number might change in a future
> version of sql server.
> I hate to do this but there is no other way to determine
> exactly what happened.
> Thanks in Advance,
> Laurence Nuttall
> Programmer Analyst III
> UCLA - Division of Continuing Education
>
>|||It's unlikely that the error codes would change. Could happen, but more
probable that additional codes would be added for other (and new)
situations.
If you are concerned, you could use a config file, and put the codes in the
config file. Have the app read the config file at start up and hold the
error codes in global variables. (An xml file works good for that.)
Otherwise, set them up as constants.
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Larry" <bliff@.Blifff.com> wrote in message
news:OlggCs6mGHA.2360@.TK2MSFTNGP04.phx.gbl...
> Using VB 6, sp6,
> On sql server 2000 (sp4)
> When I try to establish a connection to the database
> from a VB 6 program using ADO, I get a similar message
> if the UserID does not exist or if the UserID does exist
> but does not have the permission to the database.
> The NativeError number is different,
> NativeError - 18456 The UserID does not exist
> NativeError - 4060 The UserID exists, but does not have permission
> to the database.
> Can I hard code the NativeError number in my VB 6
> program to determine exactly what happened,
> (the UserID did not exist or the UserID does exist but
> does not have the proper permission.)
> I worry that the code number might change in a future
> version of sql server.
> I hate to do this but there is no other way to determine
> exactly what happened.
> Thanks in Advance,
> Laurence Nuttall
> Programmer Analyst III
> UCLA - Division of Continuing Education
>
>

Happens w/Office 2007

I can't install SQL 2005 Delveloper edition and show error with MSXML component

It shows these massage:

=== Verbose logging started: 6/11/2007 17:17:36 Build type: SHIP UNICODE 3.01.4000.4003 Calling process: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe ===
MSI (c) (A8:90) [17:17:36:545]: Resetting cached policy values
MSI (c) (A8:90) [17:17:36:545]: Machine policy value 'Debug' is 0
MSI (c) (A8:90) [17:17:36:545]: ******* RunEngine:
******* Product: \\inwa202746-1\G\SQL Server x86\Servers\Setup\msxml6.msi
******* Action:
******* CommandLine: **********
MSI (c) (A8:90) [17:17:36:545]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (A8:90) [17:17:36:545]: Grabbed execution mutex.
MSI (c) (A8:90) [17:17:36:555]: Cloaking enabled.
MSI (c) (A8:90) [17:17:36:555]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (A8:90) [17:17:36:555]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (30:AC) [17:17:36:575]: Grabbed execution mutex.
MSI (s) (30:40) [17:17:36:575]: Resetting cached policy values
MSI (s) (30:40) [17:17:36:575]: Machine policy value 'Debug' is 0
MSI (s) (30:40) [17:17:36:575]: ******* RunEngine:
******* Product: \\inwa202746-1\G\SQL Server x86\Servers\Setup\msxml6.msi
******* Action:
******* CommandLine: **********
MSI (s) (30:40) [17:17:36:675]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (30:40) [17:17:36:906]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (30:40) [17:17:37:176]: File will have security applied from OpCode.
MSI (s) (30:40) [17:17:39:119]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (30:40) [17:17:39:269]: SOFTWARE RESTRICTION POLICY: Verifying package --> '\\inwa202746-1\G\SQL Server x86\Servers\Setup\msxml6.msi' against software restriction policy
MSI (s) (30:40) [17:17:39:269]: SOFTWARE RESTRICTION POLICY: \\inwa202746-1\G\SQL Server x86\Servers\Setup\msxml6.msi has a digital signature
MSI (s) (30:40) [17:17:41:702]: SOFTWARE RESTRICTION POLICY: \\inwa202746-1\G\SQL Server x86\Servers\Setup\msxml6.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (30:40) [17:17:41:702]: End dialog not enabled
MSI (s) (30:40) [17:17:41:702]: Original package ==> \\inwa202746-1\G\SQL Server x86\Servers\Setup\msxml6.msi
MSI (s) (30:40) [17:17:41:702]: Package we're running from ==> C:\WINDOWS\Installer\3afbb9.msi
MSI (s) (30:40) [17:17:41:722]: APPCOMPAT: looking for appcompat database entry with ProductCode '{AEB9948B-4FF2-47C9-990E-47014492A0FE}'.
MSI (s) (30:40) [17:17:41:722]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (30:40) [17:17:41:722]: MSCOREE already loaded, using loaded copy
MSI (s) (30:40) [17:17:41:732]: Machine policy value 'TransformsSecure' is 0
MSI (s) (30:40) [17:17:41:732]: User policy value 'TransformsAtSource' is 0
MSI (s) (30:40) [17:17:41:732]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (30:40) [17:17:41:732]: Machine policy value 'DisablePatch' is 0
MSI (s) (30:40) [17:17:41:732]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (30:40) [17:17:41:732]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (30:40) [17:17:41:732]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (30:40) [17:17:41:732]: APPCOMPAT: looking for appcompat database entry with ProductCode '{AEB9948B-4FF2-47C9-990E-47014492A0FE}'.
MSI (s) (30:40) [17:17:41:732]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (30:40) [17:17:41:732]: Transforms are not secure.
MSI (s) (30:40) [17:17:41:732]: Command Line: STPSETUPTHREADID=3708 STPSETUPPROCESSID=424 EXTERNALCONTROL=1 ADDLOCAL=ALL SKIPPENDINGREBOOTCHECK=1 APPGUID={982DB00A-9C4E-436B-8707-18E113BAA44C} REBOOT=ReallySuppress CURRENTDIRECTORY=C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap CLIENTUILEVEL=3 CLIENTPROCESSID=424
MSI (s) (30:40) [17:17:41:732]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{A60D52F8-FAAB-4544-AF65-EAC1A22E5435}'.
MSI (s) (30:40) [17:17:41:732]: Product Code passed to Engine.Initialize: ''
MSI (s) (30:40) [17:17:41:732]: Product Code from property table before transforms: '{AEB9948B-4FF2-47C9-990E-47014492A0FE}'
MSI (s) (30:40) [17:17:41:732]: Product Code from property table after transforms: '{AEB9948B-4FF2-47C9-990E-47014492A0FE}'
MSI (s) (30:40) [17:17:41:732]: Product not registered: beginning first-time install
MSI (s) (30:40) [17:17:41:732]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
MSI (s) (30:40) [17:17:41:732]: Entering CMsiConfigurationManager:Tongue TiedetLastUsedSource.
MSI (s) (30:40) [17:17:41:763]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (30:40) [17:17:41:763]: Adding new sources is allowed.
MSI (s) (30:40) [17:17:41:763]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
MSI (s) (30:40) [17:17:41:763]: Package name extracted from package path: 'msxml6.msi'
MSI (s) (30:40) [17:17:41:763]: Package to be registered: 'msxml6.msi'
MSI (s) (30:40) [17:17:41:763]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (30:40) [17:17:41:763]: Machine policy value 'DisableMsi' is 0
MSI (s) (30:40) [17:17:41:763]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (30:40) [17:17:41:763]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (30:40) [17:17:41:763]: Product installation will be elevated because user is admin and product is being installed per-machine.
MSI (s) (30:40) [17:17:41:763]: Running product '{AEB9948B-4FF2-47C9-990E-47014492A0FE}' with elevated privileges: Product is assigned.
MSI (s) (30:40) [17:17:41:763]: PROPERTY CHANGE: Adding STPSETUPTHREADID property. Its value is '3708'.
MSI (s) (30:40) [17:17:41:763]: PROPERTY CHANGE: Adding STPSETUPPROCESSID property. Its value is '424'.
MSI (s) (30:40) [17:17:41:763]: PROPERTY CHANGE: Adding EXTERNALCONTROL property. Its value is '1'.
MSI (s) (30:40) [17:17:41:763]: PROPERTY CHANGE: Adding ADDLOCAL property. Its value is 'ALL'.
MSI (s) (30:40) [17:17:41:763]: PROPERTY CHANGE: Adding SKIPPENDINGREBOOTCHECK property. Its value is '1'.
MSI (s) (30:40) [17:17:41:763]: PROPERTY CHANGE: Adding APPGUID property. Its value is '{982DB00A-9C4E-436B-8707-18E113BAA44C}'.
MSI (s) (30:40) [17:17:41:763]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
MSI (s) (30:40) [17:17:41:763]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap'.
MSI (s) (30:40) [17:17:41:763]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (30:40) [17:17:41:763]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '424'.
MSI (s) (30:40) [17:17:41:763]: TRANSFORMS property is now:
MSI (s) (30:40) [17:17:41:763]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '300'.
MSI (s) (30:40) [17:17:41:773]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\Application Data
MSI (s) (30:40) [17:17:41:773]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\Favorites
MSI (s) (30:40) [17:17:41:773]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\NetHood
MSI (s) (30:40) [17:17:41:773]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\My Documents
MSI (s) (30:40) [17:17:41:773]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\PrintHood
MSI (s) (30:40) [17:17:41:773]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\Recent
MSI (s) (30:40) [17:17:41:783]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\SendTo
MSI (s) (30:40) [17:17:41:783]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\Templates
MSI (s) (30:40) [17:17:41:783]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\All Users\Application Data
MSI (s) (30:40) [17:17:41:783]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\Local Settings\Application Data
MSI (s) (30:40) [17:17:41:783]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\My Documents\My Pictures
MSI (s) (30:40) [17:17:41:783]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools
MSI (s) (30:40) [17:17:41:783]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs\Startup
MSI (s) (30:40) [17:17:41:793]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs
MSI (s) (30:40) [17:17:41:793]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu
MSI (s) (30:40) [17:17:41:793]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\All Users\Desktop
MSI (s) (30:40) [17:17:41:793]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\Start Menu\Programs\Administrative Tools
MSI (s) (30:40) [17:17:41:793]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\Start Menu\Programs\Startup
MSI (s) (30:40) [17:17:41:793]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\Start Menu\Programs
MSI (s) (30:40) [17:17:41:803]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\Start Menu
MSI (s) (30:40) [17:17:41:803]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\Admin\Desktop
MSI (s) (30:40) [17:17:41:803]: SHELL32:Tongue TiedHGetFolderPath returned: C:\Documents and Settings\All Users\Templates
MSI (s) (30:40) [17:17:41:803]: SHELL32:Tongue TiedHGetFolderPath returned: C:\WINDOWS\Fonts
MSI (s) (30:40) [17:17:41:803]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (s) (30:40) [17:17:41:803]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
MSI (s) (30:40) [17:17:41:803]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (30:40) [17:17:41:803]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'Exact'.
MSI (s) (30:40) [17:17:41:803]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (30:40) [17:17:41:803]: PROPERTY CHANGE: Adding COMPANYNAME property. Its value is 'Exact Software'.
MSI (s) (30:40) [17:17:41:803]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\WINDOWS\Installer\3afbb9.msi'.
MSI (s) (30:40) [17:17:41:803]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is '\\inwa202746-1\G\SQL Server x86\Servers\Setup\msxml6.msi'.
MSI (s) (30:40) [17:17:41:803]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (30:40) [17:17:41:803]: Machine policy value 'DisableRollback' is 0
MSI (s) (30:40) [17:17:41:803]: User policy value 'DisableRollback' is 0
MSI (s) (30:40) [17:17:41:803]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
=== Logging started: 6/11/2007 17:17:41 ===
MSI (s) (30:40) [17:17:41:803]: PROPERTY CHANGE: Adding Preselected property. Its value is '1'.
MSI (s) (30:40) [17:17:41:803]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (s) (30:40) [17:17:41:803]: Doing action: INSTALL
MSI (s) (30:40) [17:17:41:803]: Running ExecuteSequence
MSI (s) (30:40) [17:17:41:803]: Skipping action: SkipInstallCA (condition is false)
MSI (s) (30:40) [17:17:41:803]: Doing action: LaunchConditions
Action start 17:17:41: INSTALL.
Action start 17:17:41: LaunchConditions.
MSI (s) (30:40) [17:17:41:803]: Doing action: FindRelatedProducts
Action ended 17:17:41: LaunchConditions. Return value 1.
Action start 17:17:41: FindRelatedProducts.
MSI (s) (30:40) [17:17:41:813]: PROPERTY CHANGE: Adding NEWERFOUND.72DE5BCD_5CB0_4335_B118_AB4C4DA70AE1 property. Its value is '{A43BF6A5-D5F0-4AAA-BF41-65995063EC44}'.
MSI (s) (30:40) [17:17:41:813]: Skipping action: CA_SetRefCountUpgradeFlag (condition is false)
MSI (s) (30:40) [17:17:41:813]: Doing action: CA_SetRefCountNewerFoundFlag
Action ended 17:17:41: FindRelatedProducts. Return value 1.
MSI (s) (30:40) [17:17:41:813]: PROPERTY CHANGE: Adding NEWERFOUND999893F976BBB4A4DAD8F62CFA4D7C55 property. Its value is '1'.
Action start 17:17:41: CA_SetRefCountNewerFoundFlag.
MSI (s) (30:40) [17:17:41:813]: Doing action: IsPendingRebootKey
Action ended 17:17:41: CA_SetRefCountNewerFoundFlag. Return value 1.
MSI (s) (30:F8) [17:17:41:813]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI68.tmp, Entrypoint: IsPendingReboot
MSI (s) (30:1C) [17:17:41:813]: Generating random cookie.
MSI (s) (30:1C) [17:17:41:823]: Created Custom Action Server with PID 1832 (0x728).
MSI (s) (30Big Smile4) [17:17:41:873]: Running as a service.
MSI (s) (30Big Smile4) [17:17:41:873]: Hello, I'm your 32bit Impersonated custom action server.
Action start 17:17:41: IsPendingRebootKey.
No PendingFileRenameOperations
MSI (s) (30:40) [17:17:41:973]: Skipping action: CA_ErrorDifferentLang (condition is false)
MSI (s) (30:40) [17:17:41:973]: Skipping action: SetWOW (condition is false)
MSI (s) (30:40) [17:17:41:973]: Skipping action: SetWOWAppendCustomPath (condition is false)
MSI (s) (30:40) [17:17:41:973]: Skipping action: SetWOWINSTALLSQLSHAREDDIR_CUSTOMPATH (condition is false)
MSI (s) (30:40) [17:17:41:973]: Skipping action: SetWOWINSTALLSQLSHAREDDIR_CUSTOMPATH_ADD (condition is false)
MSI (s) (30:40) [17:17:41:973]: Doing action: Sqlmsirc_ValidateAppGuid_NewerFound.8AC30717_CC63_4611_9BB6_8CBCA668674D
Action ended 17:17:41: IsPendingRebootKey. Return value 1.
MSI (s) (30:50) [17:17:41:983]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI69.tmp, Entrypoint: Sqlmsirc_ValidateAppGuid
Action start 17:17:41: Sqlmsirc_ValidateAppGuid_NewerFound.8AC30717_CC63_4611_9BB6_8CBCA668674D.
<Func Name='Sqlmsirc_ValidateAppGuid'>
<EndFunc Name='Sqlmsirc_ValidateAppGuid' Return='0' GetLastError='0'>
MSI (s) (30:40) [17:17:42:003]: Doing action: Sqlmsirc_RefCountAppGuid_NewerFound.8AC30717_CC63_4611_9BB6_8CBCA668674D
Action ended 17:17:42: Sqlmsirc_ValidateAppGuid_NewerFound.8AC30717_CC63_4611_9BB6_8CBCA668674D. Return value 1.
MSI (s) (30:EC) [17:17:42:013]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI6A.tmp, Entrypoint: Sqlmsirc_RefCountAppGuid
Action start 17:17:42: Sqlmsirc_RefCountAppGuid_NewerFound.8AC30717_CC63_4611_9BB6_8CBCA668674D.
<Func Name='Sqlmsirc_RefCountAppGuid'>
<EndFunc Name='Sqlmsirc_RefCountAppGuid' Return='2' GetLastError='0'>
Action ended 17:17:42: Sqlmsirc_RefCountAppGuid_NewerFound.8AC30717_CC63_4611_9BB6_8CBCA668674D. Return value 3.
Action ended 17:17:42: INSTALL. Return value 3.
Property(S): ProductCode = {AEB9948B-4FF2-47C9-990E-47014492A0FE}
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 6.00.3883.8
Property(S): ProductLanguage = 1033
Property(S): UpgradeCode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
Property(S): NEWERFOUND999893F976BBB4A4DAD8F62CFA4D7C55 = 1
Property(S): ARPPRODUCTICON = ARPIco
Property(S): PIDTemplate = 53934<````=````=````=````=`````>@.@.@.@.@.
Property(S): PROMPTROLLBACKCOST = P
Property(S): DiskPrompt = [1]
Property(S): INSTALLLEVEL = 100
Property(S): ALLUSERS = 1
Property(S): InstallMode = Typical
Property(S): ErrorIcon = ErrorIco
Property(S): SuccessIcon = SuccessIco
Property(S): WarningIcon = WarningIco
Property(S): LicenseIcon = LicenseIco
Property(S): SetupIcon = SetupIco
Property(S): CompleteIcon = CompleteIco
Property(S): CustomIcon = CustomIco
Property(S): RepairIcon = RepairIco
Property(S): RemoveIcon = RemoveIco
Property(S): ModifyIcon = ModifyIco
Property(S): NewIcon = NewIco
Property(S): UpIcon = UpIco
Property(S): DialogBanner = BannerBmp
Property(S): WelcomeBmp = WelcomeBmp
Property(S): ApplicationUsers = AllUsers
Property(S): Details = 0
Property(S): AgreeToLicense = No
Property(S): _IsMaintenance = Reinstall
Property(S): _IsMaintenance2 = Modify
Property(S): ReinstallModeText = omus
Property(S): Display_IsBitmapDlg = 1
Property(S): Interrupted = 0
Property(S): ProductID = none
Property(S): ISENABLEDWUSFINISHDIALOG = 1
Property(S): SQLServerText1 = 0
Property(S): SQLServerVersionText1 = 0
Property(S): SQLServerVersionText2 = 0
Property(S): SQLServerVersionText3 = 0
Property(S): CA_ERRORCOUNT = 0
Property(S): CA_WARNINGCOUNT = 0
Property(S): CA_SUCCESSCOUNT = 0
Property(S): MINIMUMOS = true
Property(S): UI_SHOWCOPYRIGHT = yes
Property(S): ShowUserRegistrationDlg = 1
Property(S): ErrorDialog = ErrorDlg
Property(S): DefaultUIFont = Tahoma8
Property(S): NEWERFOUND.72DE5BCD_5CB0_4335_B118_AB4C4DA70AE1 = {A43BF6A5-D5F0-4AAA-BF41-65995063EC44}
Property(S): VersionNT = 501
Property(S): ARPHELPLINK = http://go.microsoft.com/fwlink/?LinkId=52156
Property(S): SecureCustomProperties = NEWERFOUND.72DE5BCD_5CB0_4335_B118_AB4C4DA70AE1;OLDERFOUND.72DE5BCD_5CB0_4335_B118_AB4C4DA70AE1;OLDERFOUND2.72DE5BCD_5CB0_4335_B118_AB4C4DA70AE1
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(S): ButtonTextStyle = {\ButtonTextStyle}
Property(S): DlgTextStyle = {\DlgTextStyle}
Property(S): DlgTextStyleB = {\DlgTextStyleB}
Property(S): DlgTitleStyle = {\DlgTitleStyle}
Property(S): DlgTitleStyleB = {\DlgTitleStyleB}
Property(S): FixedStyle = {\FixedStyle}
Property(S): COMPANYNAME = Exact Software
Property(S): USERNAME = Exact
Property(S): DialogTitleSetup = Setup
Property(S): DialogTitlePatch = Patch
Property(S): DialogTitleUpgrade = Upgrade
Property(S): Text_ArrowLeft = <
Property(S): Text_ArrowRight = >
Property(S): ButtonText_Next = Next
Property(S): ButtonText_Next_Hot = &Next
Property(S): ButtonText_Cancel = Cancel
Property(S): ButtonText_Cancel_Hot = &Cancel
Property(S): ButtonText_Back = Back
Property(S): ButtonText_Back_Hot = &Back
Property(S): ButtonText_Finish = Finish
Property(S): ButtonText_Finish_Hot = &Finish
Property(S): ButtonText_Update = Update >
Property(S): ButtonText_Update_Hot = &Update >
Property(S): ButtonText_Ok = OK
Property(S): ButtonText_Ok_Hot = &OK
Property(S): ButtonText_Yes = Yes
Property(S): ButtonText_Yes_Hot = &Yes
Property(S): ButtonText_No = No
Property(S): ButtonText_No_Hot = &No
Property(S): ButtonText_Abort = Abort
Property(S): ButtonText_Abort_Hot = &Abort
Property(S): ButtonText_Ignore = Ignore
Property(S): ButtonText_Ignore_Hot = &Ignore
Property(S): ButtonText_Retry = Retry
Property(S): ButtonText_Retry_Hot = &Retry
Property(S): ButtonText_Change = Change...
Property(S): ButtonText_Change_Hot = &Change...
Property(S): ButtonText_Help = Help
Property(S): ButtonText_Help_Hot = &Help
Property(S): ButtonText_Install = Install
Property(S): ButtonText_Install_Hot = &Install
Property(S): ButtonText_Exit = Exit
Property(S): ButtonText_Exit_Hot = &Exit
Property(S): ButtonText_Remove = Remove
Property(S): ButtonText_Remove_Hot = &Remove
Property(S): ButtonText_Space = Space
Property(S): ButtonText_Space_Hot = &Space
Property(S): ButtonText_Browse = Browse...
Property(S): ButtonText_Browse_Hot = Bro&wse...
Property(S): ButtonText_DiskCost = Disk Cost...
Property(S): ButtonText_DiskCost_Hot = &Disk Cost...
Property(S): LabelText_Status = Status
Property(S): LabelText_SerialNumber = &Serial Number:
Property(S): LabelText_UserName = &User Name
Property(S): LabelText_PersonName = Name
Property(S): LabelText_PersonOrganization = Company
Property(S): LabelText_InstallTo = Install to
Property(S): LabelText_Modify = &Modify
Property(S): LabelText_Repair = Re&pair
Property(S): LabelText_Remove = &Remove
Property(S): LabelText_Complete = &Complete
Property(S): LabelText_Custom = Cu&stom
Property(S): LabelText_NetworkLocation = &Network location:
Property(S): LabelText_LookIn = &Look in
Property(S): LabelText_FolderName = &Folder name
Property(S): LabelText_FeatureDescription = Feature description
Property(S): LabelText_CopyFilesFrom = Copy Files from
Property(S): LabelText_InstallFor = Install this application for
Property(S): HeadText_AdminWelcome = Welcome to the Install Wizard for
Property(S): HeadText_InstallWelcome = Welcome to the Install Wizard for
Property(S): HeadText_WelcomePatch = Welcome to the Patch for
Property(S): HeadText_SetupWelcome = Welcome to the
Property(S): HeadText_SetupWelcome2 = Setup
Property(S): HeadText_ResumeInstall = Resuming the Install Wizard for
Property(S): HeadText_SetupInterrupted = Setup Interrupted
Property(S): HeadText_LicenseAgreement = License Agreement
Property(S): HeadText_FeatureSelection = Feature Selection
Property(S): HeadText_NetworkLocation = Network Location
Property(S): HeadText_ProgramMaintenance = Program Maintenance
Property(S): HeadText_DiskSpaceRequirements = Disk Space Requirements
Property(S): HeadText_FilesInUse = Files in Use
Property(S): HeadText_DatabaseFolder = Database Folder
Property(S): HeadText_RegistrationInformation = Registration Information
Property(S): HeadText_CompletingSetup = Completing the
Property(S): HeadText_CompletingSetup2 = Setup
Property(S): HeadText_InstallingProduct = Installing
Property(S): HeadText_UninstallProduct = Uninstalling
Property(S): HeadText_ChangeDestinationFolder = Change Current Destination Folder
Property(S): HeadText_ReadyInstall = Ready to Install the Program
Property(S): HeadText_ReadyRepair = Ready to Repair the Program
Property(S): HeadText_ReadyModify = Ready to Modify the Program
Property(S): HeadText_RemoveProgram = Remove the Program
Property(S): HeadText_OutOfDiskSpace = Out of Disk Space
Property(S): DescText_FilesInUse = Some files that need to be updated are currently in use.
Property(S): DescText_RegistrationInformation = The following information will personalize your installation.
Property(S): DescText_ServerImage = Setup will create a server image of
Property(S): DescText_ServerImage2 = at a specified network location. To continue, click Next.
Property(S): DescText_InstallModifyRemove = Setup helps you install, modify or remove
Property(S): DescText_InstallModifyRemove2 = . To continue, click Next.
Property(S): DescText_PatchInstall = The Install Wizard will install the Patch for
Property(S): DescText_PatchInstall2 = on your computer. To continue, click Update.
Property(S): DescText_WizardComplete = The Install Wizard will complete the installation of
Property(S): DescText_WizardComplete2 = on your computer. To continue, click Next.
Property(S): DescText_CompleteSuspended = The Install Wizard will complete the suspended installation of
Property(S): DescText_CompleteSuspended2 = on your computer. To continue, click Next.
Property(S): DescText_SuccessfulInstallation = Setup has installed
Property(S): DescText_SuccessfulInstallation2 = successfully. Click Finish to exit.
Property(S): DescText_SuccessfulRemove = Setup has removed
Property(S): DescText_SuccessfulRemove2 = successfully. Click Finish to exit.
Property(S): DescText_SuccessfulRepair = Setup has repaired
Property(S): DescText_SuccessfulRepair2 = successfully. Click Finish to exit.
Property(S): DescText_SuccessfulModify = Setup has modified
Property(S): DescText_SuccessfulModify2 = successfully. Click Finish to exit.
Property(S): DescText_SetupInterrupted = Setup was interrupted before
Property(S): DescText_SetupInterrupted2 = could be completely installed.
Property(S): DescText_PreparingSetup = Setup is preparing the Install Wizard which will guide you through the program setup process. Please wait.
Property(S): DescText_FeatureSelection = Select the program features you want installed.
Property(S): DescText_ProgramFeaturesInstall = The program features you selected are being installed.
Property(S): DescText_ProgramFeaturesUninstall = The program features you selected are being uninstalled.
Property(S): DescText_ReadLicense = Please read the following license agreement carefully.
Property(S): DescText_SpecifyNetworkLocation = Specify a network location for the server image of the product.
Property(S): DescText_BrowseDestination = Browse to the destination folder.
Property(S): DescText_ModifyRepairRemove = Repair or remove the program.
Property(S): DescText_ReadyInstallation = Setup is ready to begin installation.
Property(S): DescText_ChosenRemove = You have chosen to remove the program from your system.
Property(S): DescText_DiskSpaceRequirements = The disk space required for the installation of the selected features.
Property(S): DescText_DiskExceedsAvailable = Disk space required for the installation exceeds available disk space.
Property(S): Text_ReRunSetup = Your system has not been modified. To complete installation at another time, please run setup again.
Property(S): Text_FinishExit = Click Finish to exit Setup.
Property(S): Text_RestoreState = You can either keep any existing installed elements on your system to continue this installation at a later time or you can restore your system to its original state prior to the installation.
Property(S): Text_RestoreClick = Click Restore or Continue Later to exit Setup.
Property(S): Text_InstallWait = Please wait while the Install Wizard installs
Property(S): Text_InstallWait2 = . This may take several minutes.
Property(S): Text_UninstallWaitText = Please wait while the Install Wizard uninstalls
Property(S): Text_UninstallWaitText2 = . This may take several minutes.
Property(S): Text_UninstallWait = Please wait while the Install Wizard uninstalls
Property(S): Text_UninstallWait2 = . This may take several minutes.
Property(S): Text_ProgressDone = Progress done
Property(S): Text_Copyright = WARNING: This program is protected by copyright law and international treaties.
Property(S): Text_BeginInstallation = Click Install to begin the installation.
Property(S): Text_ReviewChange = If you want to review or change any of your installation settings, click Back. Click Cancel to exit Setup.
Property(S): Text_AlterFeatureInstall = Click an icon in the following list to change how a feature is installed.
Property(S): Text_ConfirmExit = The installation is not yet complete. Are you sure you want to exit?
Property(S): Text_FeatureSelectionDescription = This feature requires 4 MB on your hard drive.
Property(S): Text_EnterNetworkLocation = Enter the network location or click Change to browse to a location. Click Install to create a server image of
Property(S): Text_EnterNetworkLocation2 = at the specified network location or click Cancel to exit Setup.
Property(S): Text_SelectDifferentDrive = The highlighted volumes do not have enough disk space available for the currently selected features. You can remove files from the highlighted volumes, choose to install less features onto local drives, or select different destination drives.
Property(S): Text_RepairInstallationErrors = Repair installation errors in the program. This option fixes missing or corrupt files, shortcuts, and registry entries.
Property(S): Text_RemoveFromComputer = Remove
Property(S): Text_RemoveFromComputer2 = from your computer.
Property(S): Text_UsingFilesRetry = The following applications are using files that need to be updated by this setup. Close these applications and click Retry to continue.
Property(S): Text_ClickRemove = Click Remove to remove
Property(S): Text_ClickRemove2 = from your computer. After removal, this program will no longer be available for use.
Property(S): Text_ReviewChangeBack = If you want to review or change any settings, click Back.
Property(S): Text_AllUsers = &Anyone who uses this computer (all users)
Property(S): Text_OnlyMe = Only for &me ([USERNAME])
Property(S): Text_NotAcceptTerms = I &do not accept the terms in the license agreement
Property(S): Text_AcceptTerms = I &accept the terms in the license agreement
Property(S): Text_RegInfoNameAndOrg = Enter your name and the name of your organization in the fields below.
Property(S): Text_RegInfoOrg = Enter the name of your organization in the field below.
Property(S): Upgrade_Confirmation = A lower version of this product has been detected on your system. Would you like to upgrade your existing installation?
Property(S): AdminMessage = Setup requires user to be in the administrator group in order to continue the installation process. Setup is aborting as the current user is not in the administrator group.
Property(S): SupportedOSMessage = Installation of this product failed because it is not supported on this operating system. For information on supported configurations, see the product documentation.
Property(S): ShortCutText = MSXML 6.0
Property(S): DialogTitle = MSXML 6.0 Parser Setup
Property(S): ProductName = MSXML 6.0 Parser
Property(S): ShortName = MSXML 6.0 Parser
Property(S): WrongPackage = This MSXML6.0 package is not supported on the current processor type.
Property(S): DialogPatchTitle = MSXML 6.0 Parser Patch
Property(S): SystemFolder = C:\WINDOWS\system32\
Property(S): WdSfpCaMainModId.41646F16_4E6C_4E96_BF1B_772105414B9D = 86F857F6_A743_463D_B2FE_98CB5F727E09
Property(S): AppGuidRegKey = Wdsfpca_Uninstall_RegKey.86F857F6_A743_463D_B2FE_98CB5F727E09
Property(S): PackageCode = {A60D52F8-FAAB-4544-AF65-EAC1A22E5435}
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): STPSETUPTHREADID = 3708
Property(S): STPSETUPPROCESSID = 424
Property(S): EXTERNALCONTROL = 1
Property(S): ADDLOCAL = ALL
Property(S): SKIPPENDINGREBOOTCHECK = 1
Property(S): APPGUID = {982DB00A-9C4E-436B-8707-18E113BAA44C}
Property(S): REBOOT = ReallySuppress
Property(S): CURRENTDIRECTORY = C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap
Property(S): CLIENTUILEVEL = 3
Property(S): CLIENTPROCESSID = 424
Property(S): VersionDatabase = 300
Property(S): VersionMsi = 3.01
Property(S): WindowsBuild = 2600
Property(S): ServicePackLevel = 2
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 1
Property(S): WindowsFolder = C:\WINDOWS\
Property(S): WindowsVolume = C:\
Property(S): System16Folder = C:\WINDOWS\system\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\DOCUME~1\Admin\LOCALS~1\Temp\
Property(S): ProgramFilesFolder = C:\Program Files\
Property(S): CommonFilesFolder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Documents and Settings\Admin\Application Data\
Property(S): FavoritesFolder = C:\Documents and Settings\Admin\Favorites\
Property(S): NetHoodFolder = C:\Documents and Settings\Admin\NetHood\
Property(S): PersonalFolder = C:\Documents and Settings\Admin\My Documents\
Property(S): PrintHoodFolder = C:\Documents and Settings\Admin\PrintHood\
Property(S): RecentFolder = C:\Documents and Settings\Admin\Recent\
Property(S): SendToFolder = C:\Documents and Settings\Admin\SendTo\
Property(S): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(S): CommonAppDataFolder = C:\Documents and Settings\All Users\Application Data\
Property(S): LocalAppDataFolder = C:\Documents and Settings\Admin\Local Settings\Application Data\
Property(S): MyPicturesFolder = C:\Documents and Settings\Admin\My Documents\My Pictures\
Property(S): AdminToolsFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\Documents and Settings\All Users\Start Menu\Programs\
Property(S): StartMenuFolder = C:\Documents and Settings\All Users\Start Menu\
Property(S): FontsFolder = C:\WINDOWS\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): Intel = 6
Property(S): PhysicalMemory = 1023
Property(S): VirtualMemory = 2183
Property(S): AdminUser = 1
Property(S): LogonUser = Administrator
Property(S): UserSID = S-1-5-21-842925246-1580818891-1957994488-500
Property(S): UserLanguageID = 1033
Property(S): ComputerName = CHUN107907-1
Property(S): SystemLanguageID = 1054
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 25
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 17:17:42
Property(S): Date = 6/11/2007
Property(S): MsiNetAssemblySupport = 2.0.50727.42
Property(S): MsiWin32AssemblySupport = 5.1.2600.3019
Property(S): RedirectedDllSupport = 2
Property(S): Privileged = 1
Property(S): DATABASE = C:\WINDOWS\Installer\3afbb9.msi
Property(S): OriginalDatabase = \\inwa202746-1\G\SQL Server x86\Servers\Setup\msxml6.msi
Property(S): UILevel = 2
Property(S): Preselected = 1
Property(S): ACTION = INSTALL
MSI (s) (30:40) [17:17:42:093]: Note: 1: 1708
MSI (s) (30:40) [17:17:42:093]: Product: MSXML 6.0 Parser -- Installation failed.

MSI (s) (30:40) [17:17:42:093]: Cleaning up uninstalled install packages, if any exist
MSI (s) (30:40) [17:17:42:093]: MainEngineThread is returning 1603
MSI (s) (30:AC) [17:17:42:193]: Destroying RemoteAPI object.
MSI (s) (30:1C) [17:17:42:193]: Custom Action Manager thread ending.
=== Logging stopped: 6/11/2007 17:17:42 ===
MSI (c) (A8:90) [17:17:42:193]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (A8:90) [17:17:42:193]: MainEngineThread is returning 1603
=== Verbose logging stopped: 6/11/2007 17:17:42 ===

Might try by installing FeaturePack and then retry installing SQL 2005 dev.|||Shows "The System administrator has set policies to prevent this installation"
What is policy to block this installation?

Thanks
|||

Hey,

I had the same issues installing MSXML6.0 with my SQL Server 2005 Express Edition as part of CRM Dynamics 3.0. Despite there being no policy (local or global) in place to enforce such a thing, I kept getting a failed installation of SQL Express due to an issue with MSXML6.0. Whenever I tried to install MSXML6.0 stand-alone, all I would receive is this blasted error message:

"The system administrator has set policies to prevent this installation"

I tried several things over several hours including the following:

- registered then unregistered Windows installer package

- uninstalled and reinstalled Windows Installer package

- logging on as local admin to install

- creating a policy and enforcing the use of Windows Installer, as well as elevating the install rights of everyone.

- getting desperate I removed and reinstalled the .NET framework 1.1, 2 and 3 (this was the last thing I changed before having the issues)

- basically tried every recommendation I found through Google on every forum...TO NO AVAIL.

I used the Windows Installer Cleanup Utility (available here: http://support.microsoft.com/kb/290301) to remove the install configuration for MSXML6.0.

After that being done, everything works fine now and no words can express my relief...

I hope this helps someone else.

Kris

|||

Thanks Krobson... it worked for me...

Excelent

|||

The cleaner isn't to be used with Office 2007 according to the KB. Anyone find a work around with Office 2007?

|||

ACTUALLY -- This did the trick after all -- I misunderstood the original article. It's saying not to cleanup any office related installation information. MSXML does not fall under that catagory.

Monday, February 27, 2012

Handling nulls in calculated rport items

Hello,
How do I block null values from displaying "#Error" when I format a
datetime.
dbuchananWould an IIF statement not work in the expression
for example:
=IIF (Fields!Date.Value = "NULL", "",Fields!Date.Value)
This would bring up a blank space (or whatever you want it the output to be)
if the value is NULL, otherwise it just brings out the value.
Im fairly new to all of this so its just a thought.
"dbuchanan" wrote:
> Hello,
> How do I block null values from displaying "#Error" when I format a
> datetime.
> dbuchanan
>|||Theoretically yes that would work but in practice it doesn't as you have to
write
=iif(Fields!Date.Value is system.dbnull.Value, "", Fields!Date.Value)
otherwise deal with it in the initial query.
Greg
"Robert Seal" <RobertSeal@.discussions.microsoft.com> wrote in message
news:AB5060A6-88AE-4FB4-A224-C1C548418EFB@.microsoft.com...
> Would an IIF statement not work in the expression
> for example:
> =IIF (Fields!Date.Value = "NULL", "",Fields!Date.Value)
> This would bring up a blank space (or whatever you want it the output to
> be)
> if the value is NULL, otherwise it just brings out the value.
> Im fairly new to all of this so its just a thought.
> "dbuchanan" wrote:
>> Hello,
>> How do I block null values from displaying "#Error" when I format a
>> datetime.
>> dbuchanan
>>

Handling Errors...

Hello to all,

On my webPage I have Used one SQLDataSource to access DataBase. Now whenever some error occures it shows error page by default. I am not able to catch Errors and tackle in my way...

Furthermore in this new structure of accessing DataBase even I do not know where to write Try... Catch...

Hey mistry,
this is the structure for Try ... Catch ... in SQL

Begin Try
-- e.g.
INSERT INTO a SELECT * FROM b
-- your actual code
End Try
Begin Catch
-- code for error handling
End Catch