MSRS Developer Edition on MS SQL 2000 STD

Hello,
I have a client installation I need to load Reporting Services on but
the disk they put into the server is Developer edition rather than
standard. This is a production server. Are their any potential issues I
might encounter?
Any information is greatly appreciated.
Thanks,
HLittle things like licensing issues a concern?
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1164072012.870727.39050@.m73g2000cwd.googlegroups.com...
> Hello,
> I have a client installation I need to load Reporting Services on but
> the disk they put into the server is Developer edition rather than
> standard. This is a production server. Are their any potential issues I
> might encounter?
> Any information is greatly appreciated.
> Thanks,
> H
>

MSRS Developer Edition on MS SQL 2000 STD

Hello,
I have a client installation I need to load Reporting Services on but
the disk they put into the server is Developer edition rather than
standard. This is a production server. Are their any potential issues I
might encounter?
Any information is greatly appreciated.
Thanks,
H
Little things like licensing issues a concern?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1164072012.870727.39050@.m73g2000cwd.googlegro ups.com...
> Hello,
> I have a client installation I need to load Reporting Services on but
> the disk they put into the server is Developer edition rather than
> standard. This is a production server. Are their any potential issues I
> might encounter?
> Any information is greatly appreciated.
> Thanks,
> H
>

MSRS Developer Edition on MS SQL 2000 STD

Hello,
I have a client installation I need to load Reporting Services on but
the disk they put into the server is Developer edition rather than
standard. This is a production server. Are their any potential issues I
might encounter?
Any information is greatly appreciated.
Thanks,
HLittle things like licensing issues a concern?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1164072012.870727.39050@.m73g2000cwd.googlegroups.com...
> Hello,
> I have a client installation I need to load Reporting Services on but
> the disk they put into the server is Developer edition rather than
> standard. This is a production server. Are their any potential issues I
> might encounter?
> Any information is greatly appreciated.
> Thanks,
> H
>

msmdredir.ini can't open of not a disk file.

Hi all,

I am having one problem about the processing cube in SQL 2005 AS.
when cube runs i get this error in log file:

File system error: Error opening file; \Program Files (x86)\Microsoft SQL Server\90\Shared\ASConfig\msmdredir.ini is not a disk file or file is not accessible.

How can i solve this!!

thanks

Does any one have experienced it before with SSAS! how can i resolve lock issues on this file!!

thanks

|||

This file contains the port numbers used by the SSAS instances on the server. I've never heard of a "locking" issue with it so I'll make a couple general suggestions.

First, try cycling (bouncing) the server to see if that clears the issue. If that doesn't work, try temporarily disabling the SQL Browser service. If this second action clears the problem, I wouldn't recommend leaving that service disabled, but at least you'll have a starting point for tech support.

Bryan Smith

|||

Yes, it's real... I've logged it with PSS and have had it now confirmed as a bug introduced in SP2.

While it revolves around named instances, scheduling the processing to happen at different times per instance may not work for you.

From the testing I did prior to logging the call, I found two issues that were introduced with SP2. Together they make the issue very very painful.

1) When you process a database when SP2 is installed, the AS Instance requires Read/write access to the msdmredir.ini file. Prior to SP2 it didn't. I could even make the file read-only, and the processing would take place successfully.

2) the ini file gets updated approximately every 30 sec PER AS INSTANCE INSTALLED. You can see this by checking the timestamp of the file. So if there are two named instances running, it will update 4 times a min (but not every 15 sec, as the instances have different start times etc). Stopping one or more of the instances will reduce the frequency of the update.

Note that the behaviour described in point 2 above did not start straight away, but only after the first time I tried to synchronise a database from one instance to the next. My thought was that I could do all the processing in one instance, then sync it out to the other instances, and avoid the locking issue. But once the behaviour starts, it doesn't go away thereafter.

So, it means that even if you're only processing from one instance, this issue may get you!! If you're lucky and your ini file isn't continuously updating, scheduling each instance to a different time may work.

Regards,

Andrew

MSDTC Resource Group - Physical Disk and Network Name

Article 301600 (http://support.microsoft.com/?kbid=301600) mentions that
MSDTC should be in its own resource group.
- What is the recommended size for the physical disk that needs to be in
this resource group?
- Is it necessary to add the Network Name resource to DNS?
Thank you.
500 MB (meg) or bigger.
You will need an IP and Network Name for it to be on the wire.
If you are running Windows Sever 2003, be sure to follow 817064 FIRST.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"vkb" <vkb@.discussions.microsoft.com> wrote in message
news:48A5C66D-988B-47A1-B638-DA2FC15AEB9B@.microsoft.com...
> Article 301600 (http://support.microsoft.com/?kbid=301600) mentions that
> MSDTC should be in its own resource group.
> - What is the recommended size for the physical disk that needs to be in
> this resource group?
> - Is it necessary to add the Network Name resource to DNS?
> Thank you.

MSDTC cluster resource

I am configuring a two node SQL cluster and i have 5 physical disk arrays and
i intend to use them in the following order
disk array 1 for quorum
disk array 2 for DATA
disk array 3 for backup
disk array 4 for TempDB
disk array 5 create two partition (1 for Tlog and 2 for MDTC disk resorces)
Will there be any probelm or is there anything wrong with creating two
partitions on the disk array 5 to make available two disk resource for those
two resources i have mentioned above e.g the MSDTC resource and the TLOg
storage . Since i want the MSDTC resource to be in its own resource group.
Please any help will be gladly appreciated.
Slawal
Clustering does not understand partitions, only disks. With that said, array
5 should stay one partition. MSDTC is only 4 MB by default. Are you sure you
will even use MSDTC with SQL? If not, you don't have to install it
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"slawal" <slawal@.discussions.microsoft.com> wrote in message
news:4D82411F-5802-4DE7-AF51-62614083B82E@.microsoft.com...
>I am configuring a two node SQL cluster and i have 5 physical disk arrays
>and
> i intend to use them in the following order
> disk array 1 for quorum
> disk array 2 for DATA
> disk array 3 for backup
> disk array 4 for TempDB
> disk array 5 create two partition (1 for Tlog and 2 for MDTC disk
> resorces)
> Will there be any probelm or is there anything wrong with creating two
> partitions on the disk array 5 to make available two disk resource for
> those
> two resources i have mentioned above e.g the MSDTC resource and the TLOg
> storage . Since i want the MSDTC resource to be in its own resource group.
> Please any help will be gladly appreciated.
>
> Slawal
|||While SQL Server does not require MS DTC, MS DTC on a cluster is only
supported when clustered and it is recommended to cluster it.
When clustering MS DTC it is preferred to have it in its own group with its
own resources, This will require your partion to appear as a physical disk
to place the disk in its own group.
Your second choice should be to put it in the cluster group,
use the quorum disk and create MS DTC its own Network Name and IP Address
resources for your MSDTC resource to use and set that resources properties
not to affect the group.
Here are some KB articles on correctly setting this up:
301600 How to configure Microsoft Distributed Transaction Coordinator on a
http://support.microsoft.com/?id=301600
817064 How to enable network DTC access in Windows Server 2003
http://support.microsoft.com/?id=817064
Also this article which may be of interest:
817065 How To Enable Network COM Access in Windows Server 2003
http://support.microsoft.com/?id=817065
Dave Whitney
SQL Support

MSDTC - running but not available - RPC error?

Hi there.
I am having problems with MSDTC on a 2-node clustered server. I currently
have it added as a resource in a group with disk storage, SQL Server, an IP
Address and a Network name. When I look at the status of MSDTC using MSSQL
Enterprise Manager on either node, it seems to be running Ok (after I select
"bring online" in cluster admin).
I have a non-clustered SQL Server from which I'd like to call stored
procedures on my clustered server (hence I need MSDTC running). However, on
running these queries, I am seeing problems like this:
select * from CLUSTER.MyDB.dbo.MyTable --this works fine BUT
BEGIN DISTRIBUTED TRANSACTION
select * from CLUSTER.MyDB.dbo.MyTable
COMMIT TRANSACTION
returns errors like
'MSDTC on server unavailable' and my stored procedure calls return errors
like:
'OLE DB error trace - ITransactionJoin::JoinTransaction returned 0x8004d00a'
I have performed some configuration according to
http://support.microsoft.com/kb/817064
and
http://support.microsoft.com/kb/301600
but to no avail.
Any ideas? We tried using DTCPing to obtain more detailed errors and what we
saw were 'RPC' errors (the cluster was unable to ping the other linked server)
Any help would be appreciated!
P.S: A constraint I have is that I can't assign a new IPAddress for MSDTC...
|||Hello,
Is your MSDTC the one from Windows 2003?
/Patrice
|||Yes - it's 2003 - sorry for leaving this out (I've ust gone a bit dizzy from
trying to fix this!)
"Patrice" wrote:

> Hello,
> Is your MSDTC the one from Windows 2003?
> /Patrice
>
|||Hello,
Is it possible for you to do the following test...
Cound you call your SP after
(a) you bring SQL online only after MSDTC was fully up and running
(b) you (try to) bring SQL online before MSDTC was fully up and
running
It would be interesting to notice that everything is fine with (a), and
that you got an "MSDTC on server unavailable" error message with (b).
If it is the case it will mean that you are experiencing the same
problem than the one I experienced a couple of months ago ;-)
/Patrice
|||Hello "Len",
Are you able to do the test I have proposed? Should I continue to
monitor this topic?
Thanks in advance for your reply.
/Patrice
|||If Patrice's test works you should contact Microsoft Product Support and
request the hotfix associated with this KB article:
883955 Availability of Windows Server 2003 COM 1.5 Rollup Package 3
http://support.microsoft.com/?id=883955
Dave Whitney
SQL Support