Proclarity - Inatalation 64 bit problem!?

Hi guys...

During the Process of installation of software PROCLARITY Analytics Server 6,3, with a profile of bit schemes in architecture 64. I am with a problem:

"This installation will disable 64-bit Support on Internet Information Services (ISS). Existing 64-bit application will no longer function. Click YES to proceed or NO to cancel the installation."

How I can decide? To install the program without damages for the ISS of architecture 64 bit

I thank attention!

Not all components of SQL Server comes in 64bits but IIS comes in 64bits so I am assuming Proclarity like Reporting services require IIS to run but if it comes only in 32bits then IIS must run in WOW64 to run Proclarity. So if you need IIS in 64bits then you need a separate 32bits box to run SQL Server with Proclarity. Hope this helps.

|||

Hi Diogo,

We are using ProClarity 6.2 on 64-bit IIS boxes and we have to configure IIS to run in 32-bit mode in order to install the ProClarity application. It may be the same for ProClarity 6.3.

This is how you configure IIS to run in 32-bit mode on a 64-bit machine :

How to switch between the 32-bit versions of ASP.NET 1.1 and the 64-bit version of ASP.NET 2.0 on a 64-bit version of Windows

http://support.microsoft.com/default.aspx/kb/894435

Regards,

Paul

|||Did you ever get this problem resolved? When I attempt to install ProClarity Analytics Server 6.4 onto a 64-bit version of Windows, I'm immediately prompted with the following error:

Missing Product Requirements

The following requirements are missing:
- The following IIS Web Service Extensions must be set to allowed (see PAS Setup Guide);

Server Side Includes
Active Server Pages
All Unknown ISAPI Extensions

I'm unable to even begin the installation, never mind complete it.
|||

Hi Brian,

ProClarity does indeed require that you enable Server Side Includes, Active Server Pages and All Unknown ISAPI Extensions for the installation to proceed.

I haven't used version 6.4 but version 6.2 requires that you run IIS in 32-bit mode.

|||

I am running IIS 6.0 in 32-bit mode (per the methods described in these postings, as well as having enabled the three web extensions asked for. The odd part is, I attempted this install on a clean 32-bit Windows Server 2003 installation and received the same error. There must be something else that I'm missing in the installation process, but for the life of my, I can't figure it out. I even followed the step-by-step instructions as detailed in the ProClarity setup guide and can't get it to install.

|||

Brian,

OK, going back to the 64-bit installation, where exactly does the installation fail and with what error message ?

Have you enabled the 32-bit Asp.Net 2.0 web service extension ?

Paul

|||

I'm running "setup.exe" from within the \INSTALL\PAS folder, by I've also tried it from running "setup.exe" at the root of the ProClarity CD. It is failing as soon as I click "Next" when I choose to install:

Full product, which includes:

- Analytics Server software

- Analytics Server database

- Administration Tool

The error message is exactly:

Missing Product Requirements

The following requirements are missing:
- The following IIS Web Service Extensions must be set to allowed (see PAS Setup Guide);

Server Side Includes
Active Server Pages
All Unknown ISAPI Extensions

My only option at that point is to click the "Back" or "Finish" button.

I've enabled the 32-bit ASP.NET 2.0 web service extension as detailed in http://support.microsoft.com/default.aspx/kb/894435, as well as the the extensions listed in the error message.

|||

Brian,

Dumb question (but I've got to ask it) - are those extensions actually enabled in IIS ?

Is the status set to Allowed as opposed to Prohibited ?

I have seen this error message before during an installation but it was because the extensions weren't enabled.

Paul

|||

They are set to "Allowed".

|||

Hi Guys...

On the problem in the installation of the Proclarity in the environment 64bit′s (where the Proclarity automatically converts the IIS for 32bit′s), the only alternative was the creation of a virtual machine with the application all installed in 32bit′s.

Thanks for Attention ....

|||

Unfortunately I received nearly the same error message on just such a machine (a Windows Server 2003 R2 Standard OS installed in VMWare):

Missing Product Requirements

The following requirements are missing:
- The following IIS Web Service Extensions must be set to allowed (see PAS Setup Guide);

Server Side Includes
Active Server Pages

|||

Hi Brian,

This is not related to Proclarity but Win2003 installs IIS that can only render HTML by default so you need to remove the one you have added and when you add it the next time click on details and you will see most of the other Asp.net related components. If you did not see the Web Service stuff click on details again and you will see them. Hope this helps.

|||

I removed IIS from the 32-bit machine and reinstalled, making sure this time to select all of the components of IIS. After the installation, I checked the web service extensions and confirmed that they are all set to "Allowed". When I attempt to install ProClarity Analytics Server 6.3, I still get the same error message.

Scratching my head on this one. I have PAS 6.2 installed on another system (Win2003 R2 Standard 32-bit) and never had this issue. Could there be something wrong with the 6.3 version I downloaded from the MSDN site? I can understand this issue occurring on the 64-bit OS, but it should work just fine on the 32-bit one.

|||

Hi Brian,

If your virtual machine is Win2003 32bits as Diogo A. Di Pietro then I don't think allowed is needed because both are 32bits. Just a thought you may remove the allowed and try the installation again.

sql

Proclarity - Inatalation 64 bit problem!?

Hi guys...

During the Process of installation of software PROCLARITY Analytics Server 6,3, with a profile of bit schemes in architecture 64. I am with a problem:

"This installation will disable 64-bit Support on Internet Information Services (ISS). Existing 64-bit application will no longer function. Click YES to proceed or NO to cancel the installation."

How I can decide? To install the program without damages for the ISS of architecture 64 bit

I thank attention!

Not all components of SQL Server comes in 64bits but IIS comes in 64bits so I am assuming Proclarity like Reporting services require IIS to run but if it comes only in 32bits then IIS must run in WOW64 to run Proclarity. So if you need IIS in 64bits then you need a separate 32bits box to run SQL Server with Proclarity. Hope this helps.

|||

Hi Diogo,

We are using ProClarity 6.2 on 64-bit IIS boxes and we have to configure IIS to run in 32-bit mode in order to install the ProClarity application. It may be the same for ProClarity 6.3.

This is how you configure IIS to run in 32-bit mode on a 64-bit machine :

How to switch between the 32-bit versions of ASP.NET 1.1 and the 64-bit version of ASP.NET 2.0 on a 64-bit version of Windows

http://support.microsoft.com/default.aspx/kb/894435

Regards,

Paul

|||Did you ever get this problem resolved? When I attempt to install ProClarity Analytics Server 6.4 onto a 64-bit version of Windows, I'm immediately prompted with the following error:

Missing Product Requirements

The following requirements are missing:
- The following IIS Web Service Extensions must be set to allowed (see PAS Setup Guide);

Server Side Includes
Active Server Pages
All Unknown ISAPI Extensions

I'm unable to even begin the installation, never mind complete it.
|||

Hi Brian,

ProClarity does indeed require that you enable Server Side Includes, Active Server Pages and All Unknown ISAPI Extensions for the installation to proceed.

I haven't used version 6.4 but version 6.2 requires that you run IIS in 32-bit mode.

|||

I am running IIS 6.0 in 32-bit mode (per the methods described in these postings, as well as having enabled the three web extensions asked for. The odd part is, I attempted this install on a clean 32-bit Windows Server 2003 installation and received the same error. There must be something else that I'm missing in the installation process, but for the life of my, I can't figure it out. I even followed the step-by-step instructions as detailed in the ProClarity setup guide and can't get it to install.

|||

Brian,

OK, going back to the 64-bit installation, where exactly does the installation fail and with what error message ?

Have you enabled the 32-bit Asp.Net 2.0 web service extension ?

Paul

|||

I'm running "setup.exe" from within the \INSTALL\PAS folder, by I've also tried it from running "setup.exe" at the root of the ProClarity CD. It is failing as soon as I click "Next" when I choose to install:

Full product, which includes:

- Analytics Server software

- Analytics Server database

- Administration Tool

The error message is exactly:

Missing Product Requirements

The following requirements are missing:
- The following IIS Web Service Extensions must be set to allowed (see PAS Setup Guide);

Server Side Includes
Active Server Pages
All Unknown ISAPI Extensions

My only option at that point is to click the "Back" or "Finish" button.

I've enabled the 32-bit ASP.NET 2.0 web service extension as detailed in http://support.microsoft.com/default.aspx/kb/894435, as well as the the extensions listed in the error message.

|||

Brian,

Dumb question (but I've got to ask it) - are those extensions actually enabled in IIS ?

Is the status set to Allowed as opposed to Prohibited ?

I have seen this error message before during an installation but it was because the extensions weren't enabled.

Paul

|||

They are set to "Allowed".

|||

Hi Guys...

On the problem in the installation of the Proclarity in the environment 64bit′s (where the Proclarity automatically converts the IIS for 32bit′s), the only alternative was the creation of a virtual machine with the application all installed in 32bit′s.

Thanks for Attention ....

|||

Unfortunately I received nearly the same error message on just such a machine (a Windows Server 2003 R2 Standard OS installed in VMWare):

Missing Product Requirements

The following requirements are missing:
- The following IIS Web Service Extensions must be set to allowed (see PAS Setup Guide);

Server Side Includes
Active Server Pages

|||

Hi Brian,

This is not related to Proclarity but Win2003 installs IIS that can only render HTML by default so you need to remove the one you have added and when you add it the next time click on details and you will see most of the other Asp.net related components. If you did not see the Web Service stuff click on details again and you will see them. Hope this helps.

|||

I removed IIS from the 32-bit machine and reinstalled, making sure this time to select all of the components of IIS. After the installation, I checked the web service extensions and confirmed that they are all set to "Allowed". When I attempt to install ProClarity Analytics Server 6.3, I still get the same error message.

Scratching my head on this one. I have PAS 6.2 installed on another system (Win2003 R2 Standard 32-bit) and never had this issue. Could there be something wrong with the 6.3 version I downloaded from the MSDN site? I can understand this issue occurring on the 64-bit OS, but it should work just fine on the 32-bit one.

|||

Hi Brian,

If your virtual machine is Win2003 32bits as Diogo A. Di Pietro then I don't think allowed is needed because both are 32bits. Just a thought you may remove the allowed and try the installation again.

Processor + Memory

Hi,
Can anybody direct me to an article or an white paper, which explains SQL Server 2000 Processor and Memory architecture and how they work together
Lets take a scenario
SQL Server 2000 Enterprise edition, 8GB of physical memory and 4 processors (same server) are available.
So some of the questions that I have in my mind are
(a) How can we distribute 8GB of memory across these 4 processor. How do we configure it
(b) Can we control, the size of memory distributed across these processor. That is, can I configure 5 GB of memory to one processor and the rest equally distributed to other processors? If yes, how do we go about it
(c) How does SQL Server parallel processing works
(d) I understand that AWE is used to increase the memory capacity for sql server app, if the memory of the server is more than 4 GB, but how exactly is this done?
Would really appreciate, if someone can provide me the link to the right article or if someone can take sometime to explain me this
Thanks very muc
GYKGYK wrote:
> Hi,
> Can anybody direct me to an article or an white paper, which explains SQL Server 2000 Processor and Memory architecture and how they work together?
No link, but the book Inside SQL-Server 2000 by Kalen Delaney explains
in great detail the internals of SQL-Server.
> Lets take a scenario;
> SQL Server 2000 Enterprise edition, 8GB of physical memory and 4 processors (same server) are available.
> So some of the questions that I have in my mind are;
> (a) How can we distribute 8GB of memory across these 4 processor. How do we configure it?
IFAIK you can't. This is done automatically and dynamically by
SQL-Server. These sound like features you might find in an Operating
System, not in a RDBMS. There is only one setting you can make: you can
determine the amount of memory that is available to SQL-Server (in
total).
> (b) Can we control, the size of memory distributed across these processor. That is, can I configure 5 GB of memory to one processor and the rest equally distributed to other processors? If yes, how do we go about it?
Not with SQL-Server. This would be an OS requirement. The memory
SQL-Server uses is exclusively reserved for SQL-Server, and not shared
with other applications. Since SQL-Server manages its memory, it doesn't
make sense to assign individual blocks of memory to individual CPU's.
> (c) How does SQL Server parallel processing works?
In a nutshell: by having multiple threads working on a query, where each
thread is handled by a different CPU. It will be used if SQL-Server
estimates it will decrease the total elapsed time of the query.
> (d) I understand that AWE is used to increase the memory capacity for sql server app, if the memory of the server is more than 4 GB, but how exactly is this done?
> Would really appreciate, if someone can provide me the link to the right article or if someone can take sometime to explain me this.
> Thanks very much
> GYK
Hope this helps,
Gert-Jan|||In addition to Kalen's excellent "Inside SQL Server 2000" there's also a
fair bit on memory architecture in BOL plus there's also Ken Hendersons new
book "The Guru's Guide to SQL Server Architecture and Internals" that really
gets into the nitty gritty of UMS and memory architecture including AWE
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"GYK" <anonymous@.discussions.microsoft.com> wrote in message
news:439E3FF7-340A-4A35-8BFE-93C26F570BAB@.microsoft.com...
> Hi,
> Can anybody direct me to an article or an white paper, which explains SQL
Server 2000 Processor and Memory architecture and how they work together?
> Lets take a scenario;
> SQL Server 2000 Enterprise edition, 8GB of physical memory and 4
processors (same server) are available.
> So some of the questions that I have in my mind are;
> (a) How can we distribute 8GB of memory across these 4 processor. How do
we configure it?
> (b) Can we control, the size of memory distributed across these processor.
That is, can I configure 5 GB of memory to one processor and the rest
equally distributed to other processors? If yes, how do we go about it?
> (c) How does SQL Server parallel processing works?
> (d) I understand that AWE is used to increase the memory capacity for sql
server app, if the memory of the server is more than 4 GB, but how exactly
is this done?
> Would really appreciate, if someone can provide me the link to the right
article or if someone can take sometime to explain me this.
> Thanks very much
> GYK|||Absolutely! Ken's book goes into the next level down from mine, discussing
the details of the OS architecture that allow SQL Server to do what it does.
I'm only in the middle of the third chapter, and I've learned a lot!
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:ONkNv8kxDHA.3744@.TK2MSFTNGP11.phx.gbl...
> In addition to Kalen's excellent "Inside SQL Server 2000" there's also a
> fair bit on memory architecture in BOL plus there's also Ken Hendersons
new
> book "The Guru's Guide to SQL Server Architecture and Internals" that
really
> gets into the nitty gritty of UMS and memory architecture including AWE
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> "GYK" <anonymous@.discussions.microsoft.com> wrote in message
> news:439E3FF7-340A-4A35-8BFE-93C26F570BAB@.microsoft.com...
> > Hi,
> >
> > Can anybody direct me to an article or an white paper, which explains
SQL
> Server 2000 Processor and Memory architecture and how they work together?
> >
> > Lets take a scenario;
> > SQL Server 2000 Enterprise edition, 8GB of physical memory and 4
> processors (same server) are available.
> >
> > So some of the questions that I have in my mind are;
> > (a) How can we distribute 8GB of memory across these 4 processor. How do
> we configure it?
> > (b) Can we control, the size of memory distributed across these
processor.
> That is, can I configure 5 GB of memory to one processor and the rest
> equally distributed to other processors? If yes, how do we go about it?
> > (c) How does SQL Server parallel processing works?
> > (d) I understand that AWE is used to increase the memory capacity for
sql
> server app, if the memory of the server is more than 4 GB, but how exactly
> is this done?
> >
> > Would really appreciate, if someone can provide me the link to the right
> article or if someone can take sometime to explain me this.
> >
> > Thanks very much
> > GYK
>

Processing cubes on a different server, using SSIS package run by a SQL Agent job from another s

Hi,

I am faced with this issue in a production environment. I have to implement an architecture where the Analysis Services database is in a server different from the server on which the SQL Serever database it accesses for data is.

I have changed the connection string for the data source in the Analysis Services database to point to the other server's SQL Server database. Log on to this server has been set to use SQL Server Authentication.

Then I created an SSIS package on the server containing SQL Server database, to process a dimension in the other server's Analysis Services database. The Analysis Services connection manager in this package was set to log on to the Analysis Services database on the other server using 'Specific User name and Password'. This user is a part of the administrator group on the server containing Analysis Services database. The package executed fine when executed from the Business Intelligence Studio.

The problem came when I tried to execute this package through a SQL agent job. The job is created on the server containing the SQL Server database. The step in the job meant to execute the package uses 'SQL Agent Service Account' for the 'Run as' option. The package was deployed as 'File System'.

I missed out posting the error message I am getting. It is as follows:

Code: 0x00000000 Description: A connection cannot be made. Ensure that the server is running.

Hope this helps to give a better understanding of the problem.

Thanks.

|||

Hi,

The problem was resolved by changing the LOG ON for the SSIS service to that of an user who is administrator on both the machines.

|||

Did you have to create a Credential and Proxy? I had to create one and set the Run As parameter for the step in Agent to the Proxy name. The job has to write a file to a network directory and from what I read it seems that the only way for an SSIS job to access anything outside SQL Server was by using a proxy. I am not sure if the same applied in your situation.

|||

Hmm.... I was helped by the fact that the OS was installed with a network administrator id. So no new credentials or proxy was required. The run as parameter for my job's step remained as "SQL Agent Service Account" and changed the Log On for SSIS service to use network administrator account. Hope this helps.

I would like to know how you created a proxy and made the Run As parameter to point to it.

Regards,

Emil

Processing cubes on a different server, using SSIS package run by a SQL Agent job from another s

Hi,

I am faced with this issue in a production environment. I have to implement an architecture where the Analysis Services database is in a server different from the server on which the SQL Serever database it accesses for data is.

I have changed the connection string for the data source in the Analysis Services database to point to the other server's SQL Server database. Log on to this server has been set to use SQL Server Authentication.

Then I created an SSIS package on the server containing SQL Server database, to process a dimension in the other server's Analysis Services database. The Analysis Services connection manager in this package was set to log on to the Analysis Services database on the other server using 'Specific User name and Password'. This user is a part of the administrator group on the server containing Analysis Services database. The package executed fine when executed from the Business Intelligence Studio.

The problem came when I tried to execute this package through a SQL agent job. The job is created on the server containing the SQL Server database. The step in the job meant to execute the package uses 'SQL Agent Service Account' for the 'Run as' option. The package was deployed as 'File System'.

I missed out posting the error message I am getting. It is as follows:

Code: 0x00000000 Description: A connection cannot be made. Ensure that the server is running.

Hope this helps to give a better understanding of the problem.

Thanks.

|||

Hi,

The problem was resolved by changing the LOG ON for the SSIS service to that of an user who is administrator on both the machines.

|||

Did you have to create a Credential and Proxy? I had to create one and set the Run As parameter for the step in Agent to the Proxy name. The job has to write a file to a network directory and from what I read it seems that the only way for an SSIS job to access anything outside SQL Server was by using a proxy. I am not sure if the same applied in your situation.

|||

Hmm.... I was helped by the fact that the OS was installed with a network administrator id. So no new credentials or proxy was required. The run as parameter for my job's step remained as "SQL Agent Service Account" and changed the Log On for SSIS service to use network administrator account. Hope this helps.

I would like to know how you created a proxy and made the Run As parameter to point to it.

Regards,

Emil

Processing cubes on a different server, using SSIS package run by a SQL Agent job from another s

Hi,

I am faced with this issue in a production environment. I have to implement an architecture where the Analysis Services database is in a server different from the server on which the SQL Serever database it accesses for data is.

I have changed the connection string for the data source in the Analysis Services database to point to the other server's SQL Server database. Log on to this server has been set to use SQL Server Authentication.

Then I created an SSIS package on the server containing SQL Server database, to process a dimension in the other server's Analysis Services database. The Analysis Services connection manager in this package was set to log on to the Analysis Services database on the other server using 'Specific User name and Password'. This user is a part of the administrator group on the server containing Analysis Services database. The package executed fine when executed from the Business Intelligence Studio.

The problem came when I tried to execute this package through a SQL agent job. The job is created on the server containing the SQL Server database. The step in the job meant to execute the package uses 'SQL Agent Service Account' for the 'Run as' option. The package was deployed as 'File System'.

I missed out posting the error message I am getting. It is as follows:

Code: 0x00000000 Description: A connection cannot be made. Ensure that the server is running.

Hope this helps to give a better understanding of the problem.

Thanks.

|||

Hi,

The problem was resolved by changing the LOG ON for the SSIS service to that of an user who is administrator on both the machines.

|||

Did you have to create a Credential and Proxy? I had to create one and set the Run As parameter for the step in Agent to the Proxy name. The job has to write a file to a network directory and from what I read it seems that the only way for an SSIS job to access anything outside SQL Server was by using a proxy. I am not sure if the same applied in your situation.

|||

Hmm.... I was helped by the fact that the OS was installed with a network administrator id. So no new credentials or proxy was required. The run as parameter for my job's step remained as "SQL Agent Service Account" and changed the Log On for SSIS service to use network administrator account. Hope this helps.

I would like to know how you created a proxy and made the Run As parameter to point to it.

Regards,

Emil