Error R6034 in MSIEXEC.EXE while installing Proclarity Desktop Pro 6.3 Evaluation

What can I do about this? There doesn't seem to be any workaround, I've upgraded everything, including the Msiexec to 3.2 (v2), but the same error always pops up.

I've done other installs of the same product without any problem whatsoever.

Can anyone help?

Regards,

Incognitus

Hello,

This isn't an error we commonly see. It actually looks to be a generic error from the Visual C++ runtime (http://msdn2.microsoft.com/en-us/library/ms235299(VS.80).aspx). You might try searching for that error and seeing what others have done to resolve it. Those same solutions will likely work for the ProClarity install as well.

Regards,

Ben

|||

I did search ... it spoke about VC80, manifest and stuff like that. Too technical for me to understand it.

Thanks anyway. I guess I'll have to do the Eval with Proclarity Web Pro, which installed without any problem.

|||

If you have as2000 installed, maybe you will need to install the servicePack 4.

I had problems installing ProClarity 6.3 because i didn't had the latest servicePack of SQLServer 2000.

I hope this helps,

Rafael Augusto

Error R6034 in MSIEXEC.EXE while installing Proclarity Desktop Pro 6.3 Evaluation

What can I do about this? There doesn't seem to be any workaround, I've upgraded everything, including the Msiexec to 3.2 (v2), but the same error always pops up.

I've done other installs of the same product without any problem whatsoever.

Can anyone help?

Regards,

Incognitus

Hello,

This isn't an error we commonly see. It actually looks to be a generic error from the Visual C++ runtime (http://msdn2.microsoft.com/en-us/library/ms235299(VS.80).aspx). You might try searching for that error and seeing what others have done to resolve it. Those same solutions will likely work for the ProClarity install as well.

Regards,

Ben

|||

I did search ... it spoke about VC80, manifest and stuff like that. Too technical for me to understand it.

Thanks anyway. I guess I'll have to do the Eval with Proclarity Web Pro, which installed without any problem.

|||

If you have as2000 installed, maybe you will need to install the servicePack 4.

I had problems installing ProClarity 6.3 because i didn't had the latest servicePack of SQLServer 2000.

I hope this helps,

Rafael Augusto

Error on Query to Sys Views (e.g. sys.objects)

I've just installed SQL Server 2005 Developer Edition, upgraded from SQL Server 2000, and have encountered a problem in trying to query against the System Catalogs.

I've tried SELECT * FROM sys.objects in addition to SELECT suser_name( role_principal_id ) FROM sys.server_role_members. In both cases I receive the following error: Invalid object name 'sys.objects' or 'sys.server_role_members' in the second example.

I changed the properties of the registration for my local db instance to use SQL authentication in lieu of Windows authentication. I used the sa login account to see if that made a difference, no go.

Can someone *please* tell me what I'm doing wrong here?

I would also like to know if it's possible to run a query confirming the user account I'm logged in to the system as.

Thanks!

what i feel is you are still connecting to SQL Server 2000. post the result of

Select @.@.Version

run the above query in query anlyser from where you are getting this error and post the result

you might have only installed Tools...

Madhu

|||

That was it Madhu. Thanks for the prompt reply. I had assumed that in upgrading to Sql Server 2005 all databases were pushed to the 2005 engine. Is there a manual step I must complete in order to do just that?

In addition, can you tell me how to query the user account I'm logged in as?

Thanks again

|||

(a) install SQL Server 2005

(b) use backup/restore or detach /attach method to transfer the database

(c) make script of other server level objects like jobs etc and run it in sql server 2005 instance

To fine user account : SELECT SUSER_SNAME()

Madhu

|||Thanks again for the feedback!

Error on Query to Sys Views (e.g. sys.objects)

I've just installed SQL Server 2005 Developer Edition, upgraded from SQL Server 2000, and have encountered a problem in trying to query against the System Catalogs.

I've tried SELECT * FROM sys.objects in addition to SELECT suser_name( role_principal_id ) FROM sys.server_role_members. In both cases I receive the following error: Invalid object name 'sys.objects' or 'sys.server_role_members' in the second example.

I changed the properties of the registration for my local db instance to use SQL authentication in lieu of Windows authentication. I used the sa login account to see if that made a difference, no go.

Can someone *please* tell me what I'm doing wrong here?

I would also like to know if it's possible to run a query confirming the user account I'm logged in to the system as.

Thanks!

what i feel is you are still connecting to SQL Server 2000. post the result of

Select @.@.Version

run the above query in query anlyser from where you are getting this error and post the result

you might have only installed Tools...

Madhu

|||

That was it Madhu. Thanks for the prompt reply. I had assumed that in upgrading to Sql Server 2005 all databases were pushed to the 2005 engine. Is there a manual step I must complete in order to do just that?

In addition, can you tell me how to query the user account I'm logged in as?

Thanks again

|||

(a) install SQL Server 2005

(b) use backup/restore or detach /attach method to transfer the database

(c) make script of other server level objects like jobs etc and run it in sql server 2005 instance

To fine user account : SELECT SUSER_SNAME()

Madhu

|||Thanks again for the feedback!

Error on Migrating to V2000 SQL from V7

I have just upgraded to SQL 2000 as per the companies allowed versions and
when trying to run an Stored Procedure I am getting the following error.
Syntax error converting the varchar value '2165.05' to a column of data type
int.
The Stored Proc just selects values into a Table, the wierd thing is this
works on v7 (same data / schema everything, but not on 2000) I can code
around it with Convert etc but was wondering if its a common problem and if
there is anything more I should know.
Cheers
Stumpy
Message posted via http://www.droptable.com
Without seeing a repro, I can only guess. It could be that datatype precedence has changed. Say, for
instance, you have a column of datatype varchar and a variable of datatype nvarchar, and then do:
WHERE col = @.a
7.0 would convert the value side to the column sides datatype. But 2000 will go by the rules
specified in Books Online "Datatype Precedence", and above would result in converting the column
side to the value sides datatype.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"stumpy_uk via droptable.com" <u15773@.uwe> wrote in message news:75df584d107f7@.uwe...
>I have just upgraded to SQL 2000 as per the companies allowed versions and
> when trying to run an Stored Procedure I am getting the following error.
> Syntax error converting the varchar value '2165.05' to a column of data type
> int.
> The Stored Proc just selects values into a Table, the wierd thing is this
> works on v7 (same data / schema everything, but not on 2000) I can code
> around it with Convert etc but was wondering if its a common problem and if
> there is anything more I should know.
> Cheers
> Stumpy
> --
> Message posted via http://www.droptable.com
>
|||MS changed the rules for implicit date type converstion between V7 and 2000.
There is nothing you can do about it.
If you use a char data type in a context in which a numeric type is
required, the char value will be converted to int, unless the context
explicitly implies (sic!) that decimal or float is requied. Since 2165.05 is
not an int, but a decimal, the conversion will fail. Since you fail to
provide the SQL code, there's no chance of my giving more details.
Use CAST (val as decimal (18, 2)) [or whatever data type you want] to
resolve. Note: CONVERT is an MS-specific function, so CAST is preferable.
"stumpy_uk via droptable.com" <u15773@.uwe> wrote in message
news:75df584d107f7@.uwe...
>I have just upgraded to SQL 2000 as per the companies allowed versions and
> when trying to run an Stored Procedure I am getting the following error.
> Syntax error converting the varchar value '2165.05' to a column of data
> type
> int.
> The Stored Proc just selects values into a Table, the wierd thing is this
> works on v7 (same data / schema everything, but not on 2000) I can code
> around it with Convert etc but was wondering if its a common problem and
> if
> there is anything more I should know.
> Cheers
> Stumpy
> --
> Message posted via http://www.droptable.com
>
|||Thanks all for your help, sorry I didn't post the DDL etc, the problem was
ownership of the Database in the end.I did a ChangeDBOwner on all the tables
and the problem went away.
Cheers for all the help..
Lee
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200707/1

Error on Migrating to V2000 SQL from V7

I have just upgraded to SQL 2000 as per the companies allowed versions and
when trying to run an Stored Procedure I am getting the following error.
Syntax error converting the varchar value '2165.05' to a column of data type
int.
The Stored Proc just selects values into a Table, the wierd thing is this
works on v7 (same data / schema everything, but not on 2000) I can code
around it with Convert etc but was wondering if its a common problem and if
there is anything more I should know.
Cheers
Stumpy
Message posted via http://www.droptable.comWithout seeing a repro, I can only guess. It could be that datatype preceden
ce has changed. Say, for
instance, you have a column of datatype varchar and a variable of datatype n
varchar, and then do:
WHERE col = @.a
7.0 would convert the value side to the column sides datatype. But 2000 will
go by the rules
specified in Books Online "Datatype Precedence", and above would result in c
onverting the column
side to the value sides datatype.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"stumpy_uk via droptable.com" <u15773@.uwe> wrote in message news:75df584d107f7@.uwe...[vbcol
=seagreen]
>I have just upgraded to SQL 2000 as per the companies allowed versions and
> when trying to run an Stored Procedure I am getting the following error.
> Syntax error converting the varchar value '2165.05' to a column of data ty
pe
> int.
> The Stored Proc just selects values into a Table, the wierd thing is this
> works on v7 (same data / schema everything, but not on 2000) I can code
> around it with Convert etc but was wondering if its a common problem and i
f
> there is anything more I should know.
> Cheers
> Stumpy
> --
> Message posted via http://www.droptable.com
>[/vbcol]|||MS changed the rules for implicit date type converstion between V7 and 2000.
There is nothing you can do about it.
If you use a char data type in a context in which a numeric type is
required, the char value will be converted to int, unless the context
explicitly implies (sic!) that decimal or float is requied. Since 2165.05 is
not an int, but a decimal, the conversion will fail. Since you fail to
provide the SQL code, there's no chance of my giving more details.
Use CAST (val as decimal (18, 2)) [or whatever data type you want] to
resolve. Note: CONVERT is an MS-specific function, so CAST is preferable.
"stumpy_uk via droptable.com" <u15773@.uwe> wrote in message
news:75df584d107f7@.uwe...
>I have just upgraded to SQL 2000 as per the companies allowed versions and
> when trying to run an Stored Procedure I am getting the following error.
> Syntax error converting the varchar value '2165.05' to a column of data
> type
> int.
> The Stored Proc just selects values into a Table, the wierd thing is this
> works on v7 (same data / schema everything, but not on 2000) I can code
> around it with Convert etc but was wondering if its a common problem and
> if
> there is anything more I should know.
> Cheers
> Stumpy
> --
> Message posted via http://www.droptable.com
>|||Thanks all for your help, sorry I didn't post the DDL etc, the problem was
ownership of the Database in the end.I did a ChangeDBOwner on all the tables
and the problem went away.
Cheers for all the help..
Lee
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200707/1sql

Error on Migrating to V2000 SQL from V7

I have just upgraded to SQL 2000 as per the companies allowed versions and
when trying to run an Stored Procedure I am getting the following error.
Syntax error converting the varchar value '2165.05' to a column of data type
int.
The Stored Proc just selects values into a Table, the wierd thing is this
works on v7 (same data / schema everything, but not on 2000) I can code
around it with Convert etc but was wondering if its a common problem and if
there is anything more I should know.
Cheers
Stumpy
--
Message posted via http://www.sqlmonster.comWithout seeing a repro, I can only guess. It could be that datatype precedence has changed. Say, for
instance, you have a column of datatype varchar and a variable of datatype nvarchar, and then do:
WHERE col = @.a
7.0 would convert the value side to the column sides datatype. But 2000 will go by the rules
specified in Books Online "Datatype Precedence", and above would result in converting the column
side to the value sides datatype.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"stumpy_uk via SQLMonster.com" <u15773@.uwe> wrote in message news:75df584d107f7@.uwe...
>I have just upgraded to SQL 2000 as per the companies allowed versions and
> when trying to run an Stored Procedure I am getting the following error.
> Syntax error converting the varchar value '2165.05' to a column of data type
> int.
> The Stored Proc just selects values into a Table, the wierd thing is this
> works on v7 (same data / schema everything, but not on 2000) I can code
> around it with Convert etc but was wondering if its a common problem and if
> there is anything more I should know.
> Cheers
> Stumpy
> --
> Message posted via http://www.sqlmonster.com
>|||MS changed the rules for implicit date type converstion between V7 and 2000.
There is nothing you can do about it.
If you use a char data type in a context in which a numeric type is
required, the char value will be converted to int, unless the context
explicitly implies (sic!) that decimal or float is requied. Since 2165.05 is
not an int, but a decimal, the conversion will fail. Since you fail to
provide the SQL code, there's no chance of my giving more details.
Use CAST (val as decimal (18, 2)) [or whatever data type you want] to
resolve. Note: CONVERT is an MS-specific function, so CAST is preferable.
"stumpy_uk via SQLMonster.com" <u15773@.uwe> wrote in message
news:75df584d107f7@.uwe...
>I have just upgraded to SQL 2000 as per the companies allowed versions and
> when trying to run an Stored Procedure I am getting the following error.
> Syntax error converting the varchar value '2165.05' to a column of data
> type
> int.
> The Stored Proc just selects values into a Table, the wierd thing is this
> works on v7 (same data / schema everything, but not on 2000) I can code
> around it with Convert etc but was wondering if its a common problem and
> if
> there is anything more I should know.
> Cheers
> Stumpy
> --
> Message posted via http://www.sqlmonster.com
>|||Thanks all for your help, sorry I didn't post the DDL etc, the problem was
ownership of the Database in the end.I did a ChangeDBOwner on all the tables
and the problem went away.
Cheers for all the help..
Lee
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200707/1

Error Message : Your SQL server installation is either corrupt or

Hi all,
I recently upgraded to visual studio 2005 professional from VB6 and sql
server 2000.
I got the latest updates and rebooted my machine and when it boots up i get
the following error message " Your SQL server installation is either corrupt
or has been tampered with (unknown package id). Please rerun setup.
OK - did that. The same error message reappeared. I have then removed visual
studio and sql server 2005 developer edition and sql server 2000 and then
rebooted mahcine. Same error message. Have reinstalled everything and the
same thing keeps reoccuring - DO i need to remove some registry entries or a
file of the machine so that this message dissapears.
TIA JustinOpen up your browser and visit the following site, it'll sove your issue
probably.
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
--
Ekrem Ã?nsoy
MCBDA, MCTS: SQL Server 2005, MCITP:DBA, MCSD.Net, MCSE, MCT
"Justin" <Justin@.discussions.microsoft.com> wrote in message
news:68E56E56-EFF1-4F14-B887-2EE0ED8F5B45@.microsoft.com...
> Hi all,
> I recently upgraded to visual studio 2005 professional from VB6 and sql
> server 2000.
> I got the latest updates and rebooted my machine and when it boots up i
> get
> the following error message " Your SQL server installation is either
> corrupt
> or has been tampered with (unknown package id). Please rerun setup.
> OK - did that. The same error message reappeared. I have then removed
> visual
> studio and sql server 2005 developer edition and sql server 2000 and then
> rebooted mahcine. Same error message. Have reinstalled everything and the
> same thing keeps reoccuring - DO i need to remove some registry entries or
> a
> file of the machine so that this message dissapears.
> TIA Justin