Friday, March 30, 2012
I'd changed the server name, sql server can't start
can not start now, how can I restore the config? I don't want to reinstall
the sql server, thanks.Hi Tigershome,
To solve this, register your server again. Enter Enterprise Manager,
right-click on your SQL Server Group, then select New SQL Server
Registration... Follow the wizard and when it asks you for the server, type
the name of your new Windows 2K server. Continue and finish the wizard, and
your SQL Server will be up and running. If not, please post again.
Jerome Smith
"tigershome" <tigershome@.etang.com> wrote in message
news:OlLC7FZqDHA.2488@.TK2MSFTNGP12.phx.gbl...
> hi, I have changed the host name of windows 2K server , then sql server
2000
> can not start now, how can I restore the config? I don't want to reinstall
> the sql server, thanks.
>
>
ICF, SQL SERVER 2000 and Windows 2003
firewall) to allow remote connection of EM (enterprise manager) to SQL
Server 2000? I tried creating 2 new "applications" on port 1433 TCP and
1433 UDP, and was unable to connect. Disabling ICF does allow EM to
connect and function.
Tia - MarkCheck your firewall log to see what is being blocked.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
IBMDASQL OLEDB linked server "access denied" using Windows Authentication
I have a linked server defined on a SQL Server 2005 SP2 standard edition server using the IBMDASQL OLEDB driver. The linked server has been defined and working for months when used from a SQL Server authenticated session. I started converting our developers to Windows Authentication and access to the linked server is denied when used from a Windows Authenticated session. Here are the error messages:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "IBMDASQL" for linked server "DB2ARUBA" reported an error. Access denied.
Msg 7350, Level 16, State 2, Line 1
Cannot get the column information from OLE DB provider "IBMDASQL" for linked server "DB2ARUBA".
The linked server security is defined to login to the IBM iSeries using a fixed user and password regardless of the login using the linked server.
In order to analyze the problem, I created one sysadmin SQL Server authenticated login and one sysadmin Windows Authenticated login. The Windows Authenticated login refers to a domain login having administrator priviledges on the local SQL Server box.
So, when I connect to SQL Server using the SQL Authenticated login, a query against the linked server works. When I connect to SQL Server using the Windows Authenticated login, the exact same query against the linked server fails with the messages above.
Does anyone know why?
I had the same problem and here is how I fixed it:
Following the advice from another post, ensure "Allow inprocess" is selected for the linked server provider:
Can you make sure that you have allowed inproc access in SQL Server for the
MSOLAP provider?:
1.. In SQL Mgmt Studio, connect to the SQL Server Database Engine and go
to Server Objects->Linked Server->Providers in the Object Explorer.
2.. Right-click on MSOLAP and select Properties. Check the "Allow
inprocess" box in the Provider Options dialog that comes up
--
Ensure the ID has permission to use the linked server (try with sysadmin for starters)
Ensure the security tab of the linked server is using an AS400 ID and password
I also noticed that my default database as my login ID was tempdb. If I changed my context to master, it ran without giving me the permission error.
Hope this helps!
|||Lexner55 -
That fixed it for me. Thanks very much. FYI, I am using the IBMDASQL provider.
|||I am actually not using the IBMDASQL driver anymore for my servers as I noticed there was quite a difference in response time versus using ODBC (which as a side note is not available in 64 bit servers).
I tested the difference between the two drivers by doing a select * on a large table and compared the time it took to complete using the IBMDASQL driver versus the ODBC driver. It took the ODBC driver a little over 3 minutes to call the 91000 rows whereas it took the IBMDASQL driver over 7 minutes running the same query. With a 64 bit server, I am using the OLE for DB2 driver provided by Microsoft and it's comparable to the ODBC driver.
For the record, I am not saying IBMDASQL should not be used. If you do not need to call large data sets from the AS400, this driver will be fine (in production scenarios as we all know, it's not best practice to select * anyways). It could also be an issue with how our AS400 server is configured or some other setting I may be missing. Regardless, you might want to run some tests and compare the different drivers.
I'm glad to hear you got it working though. Thanks for letting me know.
|||Lexner55 -
We had similar performance issues when we converted from ODBC to OLE using the IBMDASQL driver. We got around the major performance issues by using OPENQUERY instead of direct SQL, although we are still not very happy with the performance. I believe the reason for the improvement using OPENQUERY is that OPENQUERY ships the query to DB2 and lets DB2 optimize and execute it whereas a direct query ( using 4 part names ) pulls all tables involved over to SQL Server and then optimizes and exeutes the query on SQL Server. I could be wrong about that but that's the way it looks to me.
In our 64 bit environment, since the ODBC driver is no longer available, we are using the IBMDASQL OLE driver. Where did you get the OLE for DB2 driver that you referred to? I don't see it in my list of providers when I look in Management Studio.
|||Lexner55 -
I found the DB2OLEDB driver in the feature pack. So, thank again.
IBMDASQL OLEDB linked server "access denied" using Windows Authentication
I have a linked server defined on a SQL Server 2005 SP2 standard edition server using the IBMDASQL OLEDB driver. The linked server has been defined and working for months when used from a SQL Server authenticated session. I started converting our developers to Windows Authentication and access to the linked server is denied when used from a Windows Authenticated session. Here are the error messages:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "IBMDASQL" for linked server "DB2ARUBA" reported an error. Access denied.
Msg 7350, Level 16, State 2, Line 1
Cannot get the column information from OLE DB provider "IBMDASQL" for linked server "DB2ARUBA".
The linked server security is defined to login to the IBM iSeries using a fixed user and password regardless of the login using the linked server.
In order to analyze the problem, I created one sysadmin SQL Server authenticated login and one sysadmin Windows Authenticated login. The Windows Authenticated login refers to a domain login having administrator priviledges on the local SQL Server box.
So, when I connect to SQL Server using the SQL Authenticated login, a query against the linked server works. When I connect to SQL Server using the Windows Authenticated login, the exact same query against the linked server fails with the messages above.
Does anyone know why?
I had the same problem and here is how I fixed it:
Following the advice from another post, ensure "Allow inprocess" is selected for the linked server provider:
Can you make sure that you have allowed inproc access in SQL Server for the
MSOLAP provider?:
1.. In SQL Mgmt Studio, connect to the SQL Server Database Engine and go
to Server Objects->Linked Server->Providers in the Object Explorer.
2.. Right-click on MSOLAP and select Properties. Check the "Allow
inprocess" box in the Provider Options dialog that comes up
--
Ensure the ID has permission to use the linked server (try with sysadmin for starters)
Ensure the security tab of the linked server is using an AS400 ID and password
I also noticed that my default database as my login ID was tempdb. If I changed my context to master, it ran without giving me the permission error.
Hope this helps!
|||Lexner55 -
That fixed it for me. Thanks very much. FYI, I am using the IBMDASQL provider.
|||I am actually not using the IBMDASQL driver anymore for my servers as I noticed there was quite a difference in response time versus using ODBC (which as a side note is not available in 64 bit servers).
I tested the difference between the two drivers by doing a select * on a large table and compared the time it took to complete using the IBMDASQL driver versus the ODBC driver. It took the ODBC driver a little over 3 minutes to call the 91000 rows whereas it took the IBMDASQL driver over 7 minutes running the same query. With a 64 bit server, I am using the OLE for DB2 driver provided by Microsoft and it's comparable to the ODBC driver.
For the record, I am not saying IBMDASQL should not be used. If you do not need to call large data sets from the AS400, this driver will be fine (in production scenarios as we all know, it's not best practice to select * anyways). It could also be an issue with how our AS400 server is configured or some other setting I may be missing. Regardless, you might want to run some tests and compare the different drivers.
I'm glad to hear you got it working though. Thanks for letting me know.
|||Lexner55 -
We had similar performance issues when we converted from ODBC to OLE using the IBMDASQL driver. We got around the major performance issues by using OPENQUERY instead of direct SQL, although we are still not very happy with the performance. I believe the reason for the improvement using OPENQUERY is that OPENQUERY ships the query to DB2 and lets DB2 optimize and execute it whereas a direct query ( using 4 part names ) pulls all tables involved over to SQL Server and then optimizes and exeutes the query on SQL Server. I could be wrong about that but that's the way it looks to me.
In our 64 bit environment, since the ODBC driver is no longer available, we are using the IBMDASQL OLE driver. Where did you get the OLE for DB2 driver that you referred to? I don't see it in my list of providers when I look in Management Studio.
|||Lexner55 -
I found the DB2OLEDB driver in the feature pack. So, thank again.
Wednesday, March 28, 2012
I/O size
Following is my understanding when sql needs anythings reads from disk it
request to Windows which do 64 k read even though sqlserver has only
requested single record? Am I right?
how sql handle the I/O request when it reads from RAM (data cache)?
Thanks.
Farhan
I/O refers to an actual read from the I/O device. So if a data page is
in the SQL Server Data Cache, then there is no I/O.
So really, it is the other way 'round. During execution, data is
requested from the Storage Engine. The Storage Engine will check if the
required data page is in cache. If it is not, then the page is read from
disk (the I/O device) which will almost certainly cause I/O. It could
also trigger the storage engine into reading multiple consecutive pages
(Read Ahead) from disk and (temporarily) stored in the Data Cache.
Gert-Jan
Farhan wrote:
> Hello,
> Following is my understanding when sql needs anythings reads from disk it
> request to Windows which do 64 k read even though sqlserver has only
> requested single record? Am I right?
> how sql handle the I/O request when it reads from RAM (data cache)?
> Thanks.
> --
> Farhan
|||Gert,
I am looking for the size of I/O id sqlserver misses the cache hit?
Here is what I got from search
"
IO size depends on what the operations is and we try to do a good job
of
balacing various facotrs to achieve optimal performance. The following
is
not a complete list but I hope it helps explain the situation:
Operation Random / Sequential Read / Write Size Range (per I/O)
========= =================== ============ ====================
OLTP - Log Sequential Write 512 bytes - 64KB
OLTP - Data Random Read/Write 8K
Bulk Insert Sequential Write 8~128 KB
Read Ahead Sequential Read 8KB - any multiple of 8KB up to 256K
We use non-buffered IO on files so that means the windows operating
system
pass those directly to the disk subsystem. If you use RAID, then it
depends
on configuration parameters such as stripe size.
Wei Xiao
SQL Server Storage Engine Development
"
"Gert-Jan Strik" wrote:
> I/O refers to an actual read from the I/O device. So if a data page is
> in the SQL Server Data Cache, then there is no I/O.
> So really, it is the other way 'round. During execution, data is
> requested from the Storage Engine. The Storage Engine will check if the
> required data page is in cache. If it is not, then the page is read from
> disk (the I/O device) which will almost certainly cause I/O. It could
> also trigger the storage engine into reading multiple consecutive pages
> (Read Ahead) from disk and (temporarily) stored in the Data Cache.
> Gert-Jan
>
> Farhan wrote:
>
|||I don't think there are exact numbers, because it will depend on the
situation, the logic is internal (to the Storage Engine) and might
change with every hotfix or service pack.
Why do you want to know the I/O size?
Because it is even more 'unpredictable' then the story below suggests,
because a data cache miss can trigger multiple Read Aheads. According to
Inside SQL Server 2000 (a book I can recommend)
" Up to 32 extents of read ahead are outstanding at a time.
Four extents (32 pages) at a time are read with a single 256-KB
scatter read. "
The book also describes the read ahead behavior with respect to multiple
files, and the enhancements of Enterprise Edition (versus Standard
Edition) such as the "Merry-Go-Round" optimization.
Gert-Jan
Farhan wrote:[vbcol=seagreen]
> Gert,
> I am looking for the size of I/O id sqlserver misses the cache hit?
> Here is what I got from search
> "
> IO size depends on what the operations is and we try to do a good job
> of
> balacing various facotrs to achieve optimal performance. The following
> is
> not a complete list but I hope it helps explain the situation:
> Operation Random / Sequential Read / Write Size Range (per I/O)
> ========= =================== ============ ====================
> OLTP - Log Sequential Write 512 bytes - 64KB
> OLTP - Data Random Read/Write 8K
> Bulk Insert Sequential Write 8~128 KB
> Read Ahead Sequential Read 8KB - any multiple of 8KB up to 256K
> We use non-buffered IO on files so that means the windows operating
> system
> pass those directly to the disk subsystem. If you use RAID, then it
> depends
> on configuration parameters such as stripe size.
> --
> Wei Xiao
> SQL Server Storage Engine Development
> "
> "Gert-Jan Strik" wrote:
I/O size
Following is my understanding when sql needs anythings reads from disk it
request to Windows which do 64 k read even though sqlserver has only
requested single record' Am I right?
how sql handle the I/O request when it reads from RAM (data cache)?
Thanks.
--
FarhanI/O refers to an actual read from the I/O device. So if a data page is
in the SQL Server Data Cache, then there is no I/O.
So really, it is the other way 'round. During execution, data is
requested from the Storage Engine. The Storage Engine will check if the
required data page is in cache. If it is not, then the page is read from
disk (the I/O device) which will almost certainly cause I/O. It could
also trigger the storage engine into reading multiple consecutive pages
(Read Ahead) from disk and (temporarily) stored in the Data Cache.
Gert-Jan
Farhan wrote:
> Hello,
> Following is my understanding when sql needs anythings reads from disk it
> request to Windows which do 64 k read even though sqlserver has only
> requested single record' Am I right?
> how sql handle the I/O request when it reads from RAM (data cache)?
> Thanks.
> --
> Farhan|||Gert,
I am looking for the size of I/O id sqlserver misses the cache hit?
Here is what I got from search
"
IO size depends on what the operations is and we try to do a good job
of
balacing various facotrs to achieve optimal performance. The following
is
not a complete list but I hope it helps explain the situation:
Operation Random / Sequential Read / Write Size Range (per I/O)
========= =================== ============ ====================
OLTP - Log Sequential Write 512 bytes - 64KB
OLTP - Data Random Read/Write 8K
Bulk Insert Sequential Write 8~128 KB
Read Ahead Sequential Read 8KB - any multiple of 8KB up to 256K
We use non-buffered IO on files so that means the windows operating
system
pass those directly to the disk subsystem. If you use RAID, then it
depends
on configuration parameters such as stripe size.
Wei Xiao
SQL Server Storage Engine Development
"
"Gert-Jan Strik" wrote:
> I/O refers to an actual read from the I/O device. So if a data page is
> in the SQL Server Data Cache, then there is no I/O.
> So really, it is the other way 'round. During execution, data is
> requested from the Storage Engine. The Storage Engine will check if the
> required data page is in cache. If it is not, then the page is read from
> disk (the I/O device) which will almost certainly cause I/O. It could
> also trigger the storage engine into reading multiple consecutive pages
> (Read Ahead) from disk and (temporarily) stored in the Data Cache.
> Gert-Jan
>
> Farhan wrote:
>|||I don't think there are exact numbers, because it will depend on the
situation, the logic is internal (to the Storage Engine) and might
change with every hotfix or service pack.
Why do you want to know the I/O size?
Because it is even more 'unpredictable' then the story below suggests,
because a data cache miss can trigger multiple Read Aheads. According to
Inside SQL Server 2000 (a book I can recommend)
" Up to 32 extents of read ahead are outstanding at a time.
Four extents (32 pages) at a time are read with a single 256-KB
scatter read. "
The book also describes the read ahead behavior with respect to multiple
files, and the enhancements of Enterprise Edition (versus Standard
Edition) such as the "Merry-Go-Round" optimization.
Gert-Jan
Farhan wrote:[vbcol=seagreen]
> Gert,
> I am looking for the size of I/O id sqlserver misses the cache hit?
> Here is what I got from search
> "
> IO size depends on what the operations is and we try to do a good job
> of
> balacing various facotrs to achieve optimal performance. The following
> is
> not a complete list but I hope it helps explain the situation:
> Operation Random / Sequential Read / Write Size Range (per I/O)
> ========= =================== ============ ====================
> OLTP - Log Sequential Write 512 bytes - 64KB
> OLTP - Data Random Read/Write 8K
> Bulk Insert Sequential Write 8~128 KB
> Read Ahead Sequential Read 8KB - any multiple of 8KB up to 256K
> We use non-buffered IO on files so that means the windows operating
> system
> pass those directly to the disk subsystem. If you use RAID, then it
> depends
> on configuration parameters such as stripe size.
> --
> Wei Xiao
> SQL Server Storage Engine Development
> "
> "Gert-Jan Strik" wrote:
>
I/O size
Following is my understanding when sql needs anythings reads from disk it
request to Windows which do 64 k read even though sqlserver has only
requested single record' Am I right?
how sql handle the I/O request when it reads from RAM (data cache)?
Thanks.
--
FarhanI/O refers to an actual read from the I/O device. So if a data page is
in the SQL Server Data Cache, then there is no I/O.
So really, it is the other way 'round. During execution, data is
requested from the Storage Engine. The Storage Engine will check if the
required data page is in cache. If it is not, then the page is read from
disk (the I/O device) which will almost certainly cause I/O. It could
also trigger the storage engine into reading multiple consecutive pages
(Read Ahead) from disk and (temporarily) stored in the Data Cache.
Gert-Jan
Farhan wrote:
> Hello,
> Following is my understanding when sql needs anythings reads from disk it
> request to Windows which do 64 k read even though sqlserver has only
> requested single record' Am I right?
> how sql handle the I/O request when it reads from RAM (data cache)?
> Thanks.
> --
> Farhan|||Gert,
I am looking for the size of I/O id sqlserver misses the cache hit?
Here is what I got from search
"
IO size depends on what the operations is and we try to do a good job
of
balacing various facotrs to achieve optimal performance. The following
is
not a complete list but I hope it helps explain the situation:
Operation Random / Sequential Read / Write Size Range (per I/O)
========= =================== ============ ====================OLTP - Log Sequential Write 512 bytes - 64KB
OLTP - Data Random Read/Write 8K
Bulk Insert Sequential Write 8~128 KB
Read Ahead Sequential Read 8KB - any multiple of 8KB up to 256K
We use non-buffered IO on files so that means the windows operating
system
pass those directly to the disk subsystem. If you use RAID, then it
depends
on configuration parameters such as stripe size.
--
Wei Xiao
SQL Server Storage Engine Development
"
"Gert-Jan Strik" wrote:
> I/O refers to an actual read from the I/O device. So if a data page is
> in the SQL Server Data Cache, then there is no I/O.
> So really, it is the other way 'round. During execution, data is
> requested from the Storage Engine. The Storage Engine will check if the
> required data page is in cache. If it is not, then the page is read from
> disk (the I/O device) which will almost certainly cause I/O. It could
> also trigger the storage engine into reading multiple consecutive pages
> (Read Ahead) from disk and (temporarily) stored in the Data Cache.
> Gert-Jan
>
> Farhan wrote:
> >
> > Hello,
> > Following is my understanding when sql needs anythings reads from disk it
> > request to Windows which do 64 k read even though sqlserver has only
> > requested single record' Am I right?
> > how sql handle the I/O request when it reads from RAM (data cache)?
> > Thanks.
> > --
> > Farhan
>|||I don't think there are exact numbers, because it will depend on the
situation, the logic is internal (to the Storage Engine) and might
change with every hotfix or service pack.
Why do you want to know the I/O size?
Because it is even more 'unpredictable' then the story below suggests,
because a data cache miss can trigger multiple Read Aheads. According to
Inside SQL Server 2000 (a book I can recommend)
" Up to 32 extents of read ahead are outstanding at a time.
Four extents (32 pages) at a time are read with a single 256-KB
scatter read. "
The book also describes the read ahead behavior with respect to multiple
files, and the enhancements of Enterprise Edition (versus Standard
Edition) such as the "Merry-Go-Round" optimization.
Gert-Jan
Farhan wrote:
> Gert,
> I am looking for the size of I/O id sqlserver misses the cache hit?
> Here is what I got from search
> "
> IO size depends on what the operations is and we try to do a good job
> of
> balacing various facotrs to achieve optimal performance. The following
> is
> not a complete list but I hope it helps explain the situation:
> Operation Random / Sequential Read / Write Size Range (per I/O)
> ========= =================== ============ ====================> OLTP - Log Sequential Write 512 bytes - 64KB
> OLTP - Data Random Read/Write 8K
> Bulk Insert Sequential Write 8~128 KB
> Read Ahead Sequential Read 8KB - any multiple of 8KB up to 256K
> We use non-buffered IO on files so that means the windows operating
> system
> pass those directly to the disk subsystem. If you use RAID, then it
> depends
> on configuration parameters such as stripe size.
> --
> Wei Xiao
> SQL Server Storage Engine Development
> "
> "Gert-Jan Strik" wrote:
> > I/O refers to an actual read from the I/O device. So if a data page is
> > in the SQL Server Data Cache, then there is no I/O.
> >
> > So really, it is the other way 'round. During execution, data is
> > requested from the Storage Engine. The Storage Engine will check if the
> > required data page is in cache. If it is not, then the page is read from
> > disk (the I/O device) which will almost certainly cause I/O. It could
> > also trigger the storage engine into reading multiple consecutive pages
> > (Read Ahead) from disk and (temporarily) stored in the Data Cache.
> >
> > Gert-Jan
> >
> >
> > Farhan wrote:
> > >
> > > Hello,
> > > Following is my understanding when sql needs anythings reads from disk it
> > > request to Windows which do 64 k read even though sqlserver has only
> > > requested single record' Am I right?
> > > how sql handle the I/O request when it reads from RAM (data cache)?
> > > Thanks.
> > > --
> > > Farhan
> >
I/O requests taking longer than 15 seconds to complete
windows 2000 advanced servers clusterring.
SQL Server has encountered 16 occurrence(s) of I/O requests taking longer
than 15 seconds to complete on file [Y:\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2). The OS file
handle is 0x00000768. The offset of the latest long I/O is: 0x00000000652000
.
what is the cause and solution ?
NOTE:- 1- there are no sql 2005 service packs installed.
2- all HP Servers hardwares and HP SAN Storage drivers and firmwares are
updated upto date .
3- this error is generated on application peak hours .This blog entry explains the error and offers suggestions
for addressing the issue:
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/21/642314.aspx
-Sue
On Mon, 19 Mar 2007 03:02:11 -0700, maslooki
<maslooki@.discussions.microsoft.com> wrote:
>We get below error in MS SQL 2005 server which is fail over virtual server on
>windows 2000 advanced servers clusterring.
>SQL Server has encountered 16 occurrence(s) of I/O requests taking longer
>than 15 seconds to complete on file [Y:\Microsoft SQL
>Server\MSSQL.1\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2). The OS file
>handle is 0x00000768. The offset of the latest long I/O is: 0x00000000652000
>.
>what is the cause and solution ?
>NOTE:- 1- there are no sql 2005 service packs installed.
>2- all HP Servers hardwares and HP SAN Storage drivers and firmwares are
>updated upto date .
>3- this error is generated on application peak hours .
>|||Thank you MR.Sue Hoegemeier for reply
We also get the below error on the application side :-
" Transaction (Process ID 57) was deadlocked on lock resources with another
process and has been chosen as the deadlock victim. Return the transaction. "
Please again what is the cause and solution for this error ?
Note :- This happens on peak hours when they generate Reports and upload
transactions .
Thanks for cooperation
"Sue Hoegemeier" wrote:
> This blog entry explains the error and offers suggestions
> for addressing the issue:
> http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/21/642314.aspx
> -Sue
> On Mon, 19 Mar 2007 03:02:11 -0700, maslooki
> <maslooki@.discussions.microsoft.com> wrote:
> >We get below error in MS SQL 2005 server which is fail over virtual server on
> >windows 2000 advanced servers clusterring.
> >
> >SQL Server has encountered 16 occurrence(s) of I/O requests taking longer
> >than 15 seconds to complete on file [Y:\Microsoft SQL
> >Server\MSSQL.1\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2). The OS file
> >handle is 0x00000768. The offset of the latest long I/O is: 0x00000000652000
> >.
> >
> >what is the cause and solution ?
> >
> >NOTE:- 1- there are no sql 2005 service packs installed.
> >2- all HP Servers hardwares and HP SAN Storage drivers and firmwares are
> >updated upto date .
> >3- this error is generated on application peak hours .
> >
>|||You may consider ensuring that your reporting queries (I assume SELECT only)
use snapshot isolation level. Better still would be to replicate or mirror
to a reporting server which will handle the queries independent of the true
OLTP activity.
--
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
"maslooki" <maslooki@.discussions.microsoft.com> wrote in message
news:1D25A567-53FF-4667-9D3D-39F50D1F7FD7@.microsoft.com...
> Thank you MR.Sue Hoegemeier for reply
> We also get the below error on the application side :-
> " Transaction (Process ID 57) was deadlocked on lock resources with
> another
> process and has been chosen as the deadlock victim. Return the
> transaction. "
> Please again what is the cause and solution for this error ?
> Note :- This happens on peak hours when they generate Reports and upload
> transactions .
> Thanks for cooperation
> "Sue Hoegemeier" wrote:
>> This blog entry explains the error and offers suggestions
>> for addressing the issue:
>> http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/21/642314.aspx
>> -Sue
>> On Mon, 19 Mar 2007 03:02:11 -0700, maslooki
>> <maslooki@.discussions.microsoft.com> wrote:
>> >We get below error in MS SQL 2005 server which is fail over virtual
>> >server on
>> >windows 2000 advanced servers clusterring.
>> >
>> >SQL Server has encountered 16 occurrence(s) of I/O requests taking
>> >longer
>> >than 15 seconds to complete on file [Y:\Microsoft SQL
>> >Server\MSSQL.1\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2). The OS
>> >file
>> >handle is 0x00000768. The offset of the latest long I/O is:
>> >0x00000000652000
>> >.
>> >
>> >what is the cause and solution ?
>> >
>> >NOTE:- 1- there are no sql 2005 service packs installed.
>> >2- all HP Servers hardwares and HP SAN Storage drivers and firmwares are
>> >updated upto date .
>> >3- this error is generated on application peak hours .
>> >
>>|||Thank you all,
Our programmers are working on it.
"Aaron Bertrand [SQL Server MVP]" wrote:
> You may consider ensuring that your reporting queries (I assume SELECT only)
> use snapshot isolation level. Better still would be to replicate or mirror
> to a reporting server which will handle the queries independent of the true
> OLTP activity.
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.sqlblog.com/
> http://www.aspfaq.com/5006
>
>
> "maslooki" <maslooki@.discussions.microsoft.com> wrote in message
> news:1D25A567-53FF-4667-9D3D-39F50D1F7FD7@.microsoft.com...
> > Thank you MR.Sue Hoegemeier for reply
> >
> > We also get the below error on the application side :-
> > " Transaction (Process ID 57) was deadlocked on lock resources with
> > another
> > process and has been chosen as the deadlock victim. Return the
> > transaction. "
> >
> > Please again what is the cause and solution for this error ?
> >
> > Note :- This happens on peak hours when they generate Reports and upload
> > transactions .
> >
> > Thanks for cooperation
> >
> > "Sue Hoegemeier" wrote:
> >
> >> This blog entry explains the error and offers suggestions
> >> for addressing the issue:
> >> http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/21/642314.aspx
> >>
> >> -Sue
> >>
> >> On Mon, 19 Mar 2007 03:02:11 -0700, maslooki
> >> <maslooki@.discussions.microsoft.com> wrote:
> >>
> >> >We get below error in MS SQL 2005 server which is fail over virtual
> >> >server on
> >> >windows 2000 advanced servers clusterring.
> >> >
> >> >SQL Server has encountered 16 occurrence(s) of I/O requests taking
> >> >longer
> >> >than 15 seconds to complete on file [Y:\Microsoft SQL
> >> >Server\MSSQL.1\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2). The OS
> >> >file
> >> >handle is 0x00000768. The offset of the latest long I/O is:
> >> >0x00000000652000
> >> >.
> >> >
> >> >what is the cause and solution ?
> >> >
> >> >NOTE:- 1- there are no sql 2005 service packs installed.
> >> >2- all HP Servers hardwares and HP SAN Storage drivers and firmwares are
> >> >updated upto date .
> >> >3- this error is generated on application peak hours .
> >> >
> >>
> >>
>
>
Monday, March 26, 2012
I wonder which fixes I should apply to the SQL Server.
As the subject mentioned, I don't know what to apply to the SQL Server 2000.
In Windows, there is 'Windows Update' which informs the administrators what
to apply.
But in SQL Server, there is no one like 'Windows Update'
Today I found that MS had released the new cumulative patch for SQL Server.
I read carefully documentation and found that this patch does not include
fixes for MDAC or OLAP.
It listed a list of fixes, and I read the documentation about the patches.
The document said that it would be included
in the future service packs.
I'm puzzled that if I should apply patches which had been released before
Service Pack 3.
What should I do?Kim,
>> I'm puzzled that if I should apply patches which had been released
before
> Service Pack 3.
No need.If you are going to apply SP3(or SP3a), that should suffice.For
security patches after that, you may need to read the documentation or use
suggestions by a tool called Baseline Security Analyzer.Here are more
details:
Microsoft Baseline Security Analyzer (MBSA) Version 1.1.1 Is Available
http://support.microsoft.com/?id=320454
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Kim, KeukTae" <zyuuzika@.korea.com> wrote in message
news:exBGVfgZDHA.1940@.TK2MSFTNGP10.phx.gbl...
> Hi, all.
> As the subject mentioned, I don't know what to apply to the SQL Server
2000.
> In Windows, there is 'Windows Update' which informs the administrators
what
> to apply.
> But in SQL Server, there is no one like 'Windows Update'
> Today I found that MS had released the new cumulative patch for SQL
Server.
> I read carefully documentation and found that this patch does not include
> fixes for MDAC or OLAP.
> It listed a list of fixes, and I read the documentation about the patches.
> The document said that it would be included
> in the future service packs.
> I'm puzzled that if I should apply patches which had been released before
> Service Pack 3.
> What should I do?
>
>
I was getting an unspecified error....
Monday, March 12, 2012
I think I found the solution
I recently (yesterday) installed a fresh copy of Windows XP with Service Pack 2 applied.
I proceeded with Visual Studio 2005 Express Editions installation straight away.
But I cannot install Microsoft SQL Server 2005 Express Edition x86.
I choose to install Microsoft SQL Server 2005 Express Edition x86 component along with every component of visual studio but it simply would not install.
In the end, after the installation of each complete is complete, I simply get an error message saying that Microsoft SQL Server 2005 Express Edition x86 failed to install.
What is the problem?
First take a look at the following file: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\summary.txt. This should point you to which component failed and the specific log file for the component. When you open the component log file search for "Value 3" (this is a Windows Installer code for the error section). Take a look at +/- 10 lines for the error.
If the summary.txt file doesn't provide any clues, take a look at: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files\*_core(local).txt - open the most recent one if there are multiple. Go to the end of the file and you should find some clues as to why the installation failed.
|||I looked. There were three errors and all of them said that installation cannot be done to a compressed drive
--
Error : SQL Server Setup cannot install files to the compressed or encrypted folder: C:\Program Files\Microsoft SQL Server\. To continue, make sure that your installation directories are not compressed or encrypted, or specify a different directory, and then run SQL Server Setup again.
--
I'll remove drive compression and try again.
Thanks for help!
|||I am having the same problem - cannot install SQL Server Express, I looked in the file you mentioned to the other fellow and it says:
D43QNW81 : SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
but I HAVE removed all components except a thing called Enterprise Library June 2005, and thaat one will not un-install without dot net framework 1.1
is that it? do I have to go ALL the way back?
any help will be much appreciated, I installed the whole works in a Virutal machine and now I am trying to install it on my base machine (because the Virtual one is too slow)
David,
You can take a look at the latest *_core(local).log file to see which old component it's detecting. The log files can be found here: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files
If you email me directly at dtjones@.microsoft.com I can send you a clean up script. The script isn't supported but we've had good luck with it.
Cheers,
Dan
Friday, March 9, 2012
I need to uninstall Instance2 on the server keeping 1 and 3
Installed 3 instances of SQL Server 2005 on a single server (windows
2003 standard) say Instance1, instance2 and Instance3.
I need to uninstall Instance2 on the server keeping 1 and 3 .
Any tools to achieve this or any scripts to write ...
Karan LobanaInstallation and uninstallation is done at the instance level. So you should be able to uninstall
only instance 2, and then install it again.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<karanlobana@.gmail.com> wrote in message
news:1181236891.209440.200070@.k79g2000hse.googlegroups.com...
> Here is the scenario.
> Installed 3 instances of SQL Server 2005 on a single server (windows
> 2003 standard) say Instance1, instance2 and Instance3.
> I need to uninstall Instance2 on the server keeping 1 and 3 .
> Any tools to achieve this or any scripts to write ...
> Karan Lobana
>|||On Jun 7, 1:05 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Installation and uninstallation is done at the instance level. So you should be able to uninstall
> only instance 2, and then install it again.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> <karanlob...@.gmail.com> wrote in message
> news:1181236891.209440.200070@.k79g2000hse.googlegroups.com...
>
> > Here is the scenario.
> > Installed 3 instances of SQL Server 2005 on a single server (windows
> > 2003 standard) say Instance1, instance2 and Instance3.
> > I need to uninstall Instance2 on the server keeping 1 and 3 .
> > Any tools to achieve this or any scripts to write ...
> > Karan Lobana- Hide quoted text -
> - Show quoted text -
The tool is Add\Remove programs. Select SQL Server 2005 and you will
be prompted to remove only the instance(s) desired. In earlier
version, each instance is listed seperatley in Add\Remove programs.
Terry
I need to startup a windows application with parameters passed from SRS
report. I know its a long shot but I am sure somebody knows how to do this.
--
Gene Hunter
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200508/1Sure.
Write some custom code in an assembly that you link to your report. Then in
your report call a function on the assembly to run your app. Since this is
.NET code, you have access to the Process object which you can use to start
the process.
"gene hunter via SQLMonster.com" wrote:
> Is there any way to start up a windows application and pass parameters from a
> report. I know its a long shot but I am sure somebody knows how to do this.
> --
> Gene Hunter
>
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200508/1
>
I need to Give DBA full admin rights to SQL 2005 without OS windows rights, can anyone help plea
The DBA at our location is demanding local admin (windows) right's to the box so he can function. Right now when he logs in i have given him right's to the inetpub directory, sql directory, i have set him as a sysadmin on sql2005 and gone into the http:\\localhost\reports and set him up as a system manager and under site priveledges set him as a sys admin. When he tries to login and configure the report server he gets the following error:
Title-Reporting services configuration manager
Error-There was an error refreshing the UI. bla bla bla
A WMI error has occurred and no additional error information is availiable
Title-Reporting services configuration manager
Error-There was an error while switching panels. The most likely cause is an error retrieving WMI properties. bla bla bla
A WMI error has occurred and no additional error information is availiable
then when he's in sql server 2005 surface area configuation
Title-Surface Area Configuration
Error-Access denied (system.management)
Is there any documentation or anythign anyone can tell me that i can do to give this DBA full access to configure and admin the SQL portion of his system without giving him admin rights to the OS?
Please help!!
Thanks for any time anyone has taken to review this thread!!
There's no issue in giving him/her admin rights to the box. In most cases, he'll/she'll need it. Don't confuse local admin on the box with network admin rights.
Adamus
|||That's the problem in my environment i cant give local admin rights to any box. This is per PCI requirements which is a credit card VISA format amongst other regulations i'm under.
Do you have any other info that can provide assistance?
|||IThe DBA at our location is demanding local admin (windows) right's to the box so he can function. Right now when he logs in i have given him right's to the inetpub directory, sql directory, i have set him as a sysadmin on sql2005 and gone into the http:\\localhost\reports and set him up as a system manager and under site priveledges set him as a sys admin. When he tries to login and configure the report server he gets the following error:
Title-Reporting services configuration manager
Error-There was an error refreshing the UI. bla bla bla
A WMI error has occurred and no additional error information is availiable
Title-Reporting services configuration manager
Error-There was an error while switching panels. The most likely cause is an error retrieving WMI properties. bla bla bla
A WMI error has occurred and no additional error information is availiable
then when he's in sql server 2005 surface area configuation
Title-Surface Area Configuration
Error-Access denied (system.management)
Is there any documentation or anythign anyone can tell me that i can do to give this DBA full access to configure and admin the SQL portion of his system without giving him admin rights to the OS?
|||Moving to the SQL Server Security Forum.|||ok i think i figured out the surface area config issue, theres a link that states : Add new administrator in which i did and i can access all pages now, but it wont obviously let a non admin restart services, since there's a handful of services i think i'll just have/set the services under the SQL admins credentials, unless someone knows of a better way, in which i can allow the sql admin to restart services?
On the other issue i still cant access the reporting service configuration page, still recieving a WMI error?//
Please anyone HELP!!
|||These sources should help you understand and configure the appropriate account/security for your DBA.
Configuration -Service Accounts, SQL Server 2005 - Setting Up Windows Service Accounts
http://msdn2.microsoft.com/en-us/library/ms143691.aspx
http://msdn2.microsoft.com/en-us/library/ms143504.aspx
Configuration -Service Accounts, SQL Server or SQL Server Agent service account
http://support.microsoft.com/kb/283811/en-us
http://msdn2.microsoft.com/en-us/library/ms143691.aspx
Configuration -Service Accounts,Selecting an Account for the SQL Server Agent Service
http://msdn2.microsoft.com/en-us/library/ms191543.aspx
http://support.microsoft.com/kb/907557
Ok i was looking over the attached documents. It pretty much looks from what you've given me, if i setup the services on the local machine to run under the SQL DBA's credentials that i wont need to do anything further, this will in turn give the SQL DBA access without any errors?
Personally i dont think the service items are the issues but if you're positive this will do what i dneed to do i'll try it. Please reconfirm my understanding of the situation before i attempt to run changes please.
Again thanks for your assistance.
Wednesday, March 7, 2012
I need some serious help here
I upgraded my computer from Windows 2000 to 2003 and after a day or two
realized RS would not run, but it could have expired.
I upgraded my RS from the evaluation version to the release version,
choosing "upgrade". After the upgrade at first it wouldn't allow access to
the virtual dirs (eventually I hard-coded the Admin name/password in the
impersonation line in web.config which fixed it) and after that it
complained about unable to connect to the database. I tried the rsconfig
utility, then it complained about unable to decrypt a key pair and it
suggested restoring the default, which of course I did not have (it really
surprised me there).
I un-installed RS and started a fresh install. Now it says "The edition of
the Report Server Database is not supported on the edition of SQL Server
2000 you have chosen".
Both SQL 2000 and RS are Enterprise, and the evaluation was quite happy
using my SQL Server version (my machine was still Win 2000 though).
I have been fighting this install for about 7 hours now (on a Sunday),
googled, newsgroups, used bad language, etc, etc.
I am (or was) going to demo some (beautiful) reports to a client tomorrow.Do you have SP3a installed on your SQL2K enterprise?
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
>I had the evaluation version running, generated beautiful reports.
> I upgraded my computer from Windows 2000 to 2003 and after a day or two
> realized RS would not run, but it could have expired.
> I upgraded my RS from the evaluation version to the release version,
> choosing "upgrade". After the upgrade at first it wouldn't allow access to
> the virtual dirs (eventually I hard-coded the Admin name/password in the
> impersonation line in web.config which fixed it) and after that it
> complained about unable to connect to the database. I tried the rsconfig
> utility, then it complained about unable to decrypt a key pair and it
> suggested restoring the default, which of course I did not have (it really
> surprised me there).
> I un-installed RS and started a fresh install. Now it says "The edition of
> the Report Server Database is not supported on the edition of SQL Server
> 2000 you have chosen".
> Both SQL 2000 and RS are Enterprise, and the evaluation was quite happy
> using my SQL Server version (my machine was still Win 2000 though).
> I have been fighting this install for about 7 hours now (on a Sunday),
> googled, newsgroups, used bad language, etc, etc.
> I am (or was) going to demo some (beautiful) reports to a client tomorrow.
>|||Hi Brian,
I had SP3 and upgraded to SP3a yesterday as well. What is RS looking at when
it decides that this is the wrong version?
I guess I can backup all databases and re-install SQL Server if you think
that should do it. I gave that a thought already, but then it came to mind
what if it is something else and I went through that exercise for nothing.
Thanks for your ideas,
Chris.
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> Do you have SP3a installed on your SQL2K enterprise?
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> >I had the evaluation version running, generated beautiful reports.
> > I upgraded my computer from Windows 2000 to 2003 and after a day or two
> > realized RS would not run, but it could have expired.
> > I upgraded my RS from the evaluation version to the release version,
> > choosing "upgrade". After the upgrade at first it wouldn't allow access
to
> > the virtual dirs (eventually I hard-coded the Admin name/password in the
> > impersonation line in web.config which fixed it) and after that it
> > complained about unable to connect to the database. I tried the rsconfig
> > utility, then it complained about unable to decrypt a key pair and it
> > suggested restoring the default, which of course I did not have (it
really
> > surprised me there).
> > I un-installed RS and started a fresh install. Now it says "The edition
of
> > the Report Server Database is not supported on the edition of SQL Server
> > 2000 you have chosen".
> > Both SQL 2000 and RS are Enterprise, and the evaluation was quite happy
> > using my SQL Server version (my machine was still Win 2000 though).
> > I have been fighting this install for about 7 hours now (on a Sunday),
> > googled, newsgroups, used bad language, etc, etc.
> > I am (or was) going to demo some (beautiful) reports to a client
tomorrow.
> >
> >
>|||I just looked at my notes from my install on Windows 2003. For Windows 2003
only, you need a hotfix for SQL Server. Seems strange that SQL Server needs
it but only on 2003 but there you are. It is in the installation notes for
the install. Besides SP3a you need hotfix 859.
Your situation is a bit different. Only RS is on 2003 and your SQL Server is
still on 2000 so it seems like you wouldn't need the hotfix but you are
accessing it from Windows 2003 so maybe that is the key point. In my case
SQL Server and RS are both on Windows 2003.
In any case, it won't hurt anything and it might fix your problem so I
suggest installing the hotfix and see if that helps.
Hope that helps.
"Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
news:uETJr%23RXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Hi Brian,
> I had SP3 and upgraded to SP3a yesterday as well. What is RS looking at
when
> it decides that this is the wrong version?
> I guess I can backup all databases and re-install SQL Server if you think
> that should do it. I gave that a thought already, but then it came to mind
> what if it is something else and I went through that exercise for nothing.
> Thanks for your ideas,
> Chris.
> "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
> news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> > Do you have SP3a installed on your SQL2K enterprise?
> >
> > --
> > Brian Welcker
> > Group Program Manager
> > SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> > >I had the evaluation version running, generated beautiful reports.
> > > I upgraded my computer from Windows 2000 to 2003 and after a day or
two
> > > realized RS would not run, but it could have expired.
> > > I upgraded my RS from the evaluation version to the release version,
> > > choosing "upgrade". After the upgrade at first it wouldn't allow
access
> to
> > > the virtual dirs (eventually I hard-coded the Admin name/password in
the
> > > impersonation line in web.config which fixed it) and after that it
> > > complained about unable to connect to the database. I tried the
rsconfig
> > > utility, then it complained about unable to decrypt a key pair and it
> > > suggested restoring the default, which of course I did not have (it
> really
> > > surprised me there).
> > > I un-installed RS and started a fresh install. Now it says "The
edition
> of
> > > the Report Server Database is not supported on the edition of SQL
Server
> > > 2000 you have chosen".
> > > Both SQL 2000 and RS are Enterprise, and the evaluation was quite
happy
> > > using my SQL Server version (my machine was still Win 2000 though).
> > > I have been fighting this install for about 7 hours now (on a Sunday),
> > > googled, newsgroups, used bad language, etc, etc.
> > > I am (or was) going to demo some (beautiful) reports to a client
> tomorrow.
> > >
> > >
> >
> >
>|||Hi Bruce,
I have both SQL Server and RS running on the same 2003 machine, upgraded
from Win 2000 to 2003.
I am now attempting to locate hotfix 859, if you know the URL drop it here.
Thanks.
"Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:OLbvvSSXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> I just looked at my notes from my install on Windows 2003. For Windows
2003
> only, you need a hotfix for SQL Server. Seems strange that SQL Server
needs
> it but only on 2003 but there you are. It is in the installation notes for
> the install. Besides SP3a you need hotfix 859.
> Your situation is a bit different. Only RS is on 2003 and your SQL Server
is
> still on 2000 so it seems like you wouldn't need the hotfix but you are
> accessing it from Windows 2003 so maybe that is the key point. In my case
> SQL Server and RS are both on Windows 2003.
> In any case, it won't hurt anything and it might fix your problem so I
> suggest installing the hotfix and see if that helps.
> Hope that helps.
> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> news:uETJr%23RXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > Hi Brian,
> >
> > I had SP3 and upgraded to SP3a yesterday as well. What is RS looking at
> when
> > it decides that this is the wrong version?
> > I guess I can backup all databases and re-install SQL Server if you
think
> > that should do it. I gave that a thought already, but then it came to
mind
> > what if it is something else and I went through that exercise for
nothing.
> >
> > Thanks for your ideas,
> >
> > Chris.
> >
> > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
> > news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> > > Do you have SP3a installed on your SQL2K enterprise?
> > >
> > > --
> > > Brian Welcker
> > > Group Program Manager
> > > SQL Server Reporting Services
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> > > >I had the evaluation version running, generated beautiful reports.
> > > > I upgraded my computer from Windows 2000 to 2003 and after a day or
> two
> > > > realized RS would not run, but it could have expired.
> > > > I upgraded my RS from the evaluation version to the release version,
> > > > choosing "upgrade". After the upgrade at first it wouldn't allow
> access
> > to
> > > > the virtual dirs (eventually I hard-coded the Admin name/password in
> the
> > > > impersonation line in web.config which fixed it) and after that it
> > > > complained about unable to connect to the database. I tried the
> rsconfig
> > > > utility, then it complained about unable to decrypt a key pair and
it
> > > > suggested restoring the default, which of course I did not have (it
> > really
> > > > surprised me there).
> > > > I un-installed RS and started a fresh install. Now it says "The
> edition
> > of
> > > > the Report Server Database is not supported on the edition of SQL
> Server
> > > > 2000 you have chosen".
> > > > Both SQL 2000 and RS are Enterprise, and the evaluation was quite
> happy
> > > > using my SQL Server version (my machine was still Win 2000 though).
> > > > I have been fighting this install for about 7 hours now (on a
Sunday),
> > > > googled, newsgroups, used bad language, etc, etc.
> > > > I am (or was) going to demo some (beautiful) reports to a client
> > tomorrow.
> > > >
> > > >
> > >
> > >
> >
> >
>|||Nope, did not help if this was the correct hotfix, downloaded from
http://support.microsoft.com/default.aspx?scid=kb;en-us;821334
Thanks in any case.
"Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
news:Orv6o6SXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> Hi Bruce,
> I have both SQL Server and RS running on the same 2003 machine, upgraded
> from Win 2000 to 2003.
> I am now attempting to locate hotfix 859, if you know the URL drop it
here.
> Thanks.
> "Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:OLbvvSSXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > I just looked at my notes from my install on Windows 2003. For Windows
> 2003
> > only, you need a hotfix for SQL Server. Seems strange that SQL Server
> needs
> > it but only on 2003 but there you are. It is in the installation notes
for
> > the install. Besides SP3a you need hotfix 859.
> >
> > Your situation is a bit different. Only RS is on 2003 and your SQL
Server
> is
> > still on 2000 so it seems like you wouldn't need the hotfix but you are
> > accessing it from Windows 2003 so maybe that is the key point. In my
case
> > SQL Server and RS are both on Windows 2003.
> >
> > In any case, it won't hurt anything and it might fix your problem so I
> > suggest installing the hotfix and see if that helps.
> >
> > Hope that helps.
> >
> > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > news:uETJr%23RXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > Hi Brian,
> > >
> > > I had SP3 and upgraded to SP3a yesterday as well. What is RS looking
at
> > when
> > > it decides that this is the wrong version?
> > > I guess I can backup all databases and re-install SQL Server if you
> think
> > > that should do it. I gave that a thought already, but then it came to
> mind
> > > what if it is something else and I went through that exercise for
> nothing.
> > >
> > > Thanks for your ideas,
> > >
> > > Chris.
> > >
> > > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in
message
> > > news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> > > > Do you have SP3a installed on your SQL2K enterprise?
> > > >
> > > > --
> > > > Brian Welcker
> > > > Group Program Manager
> > > > SQL Server Reporting Services
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > >
> > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > > news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> > > > >I had the evaluation version running, generated beautiful reports.
> > > > > I upgraded my computer from Windows 2000 to 2003 and after a day
or
> > two
> > > > > realized RS would not run, but it could have expired.
> > > > > I upgraded my RS from the evaluation version to the release
version,
> > > > > choosing "upgrade". After the upgrade at first it wouldn't allow
> > access
> > > to
> > > > > the virtual dirs (eventually I hard-coded the Admin name/password
in
> > the
> > > > > impersonation line in web.config which fixed it) and after that it
> > > > > complained about unable to connect to the database. I tried the
> > rsconfig
> > > > > utility, then it complained about unable to decrypt a key pair and
> it
> > > > > suggested restoring the default, which of course I did not have
(it
> > > really
> > > > > surprised me there).
> > > > > I un-installed RS and started a fresh install. Now it says "The
> > edition
> > > of
> > > > > the Report Server Database is not supported on the edition of SQL
> > Server
> > > > > 2000 you have chosen".
> > > > > Both SQL 2000 and RS are Enterprise, and the evaluation was quite
> > happy
> > > > > using my SQL Server version (my machine was still Win 2000
though).
> > > > > I have been fighting this install for about 7 hours now (on a
> Sunday),
> > > > > googled, newsgroups, used bad language, etc, etc.
> > > > > I am (or was) going to demo some (beautiful) reports to a client
> > > tomorrow.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||OK, just in case any of the following might help you. There were several
things I had to do different under 2003 Server.
1. Hotfix 859
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSUIREF/htm/f1_rsc_installation_v1_036u.asp
2. Configure server with application server, asp.net (two distinct
activities). Seems if this was an issue you would get a different error
message
3. I selected built-in account. Two choices: network and system. It defaults
to network. I wanted system (which is how my previous configurations were
configured).
Other than these my installation went smoothly but then I had a clean
install of Windows 2003 Advanced Server and SQL Server Enterprise.
What do you get when you do a select @.@.version? I get this:
Microsoft SQL Server 2000 - 8.00.859 (Intel X86) Sep 18 2003 12:53:45
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: )
Bruce L-C
"Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
news:ePWpOETXEHA.644@.tk2msftngp13.phx.gbl...
> Nope, did not help if this was the correct hotfix, downloaded from
> http://support.microsoft.com/default.aspx?scid=kb;en-us;821334
> Thanks in any case.
> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> news:Orv6o6SXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > Hi Bruce,
> >
> > I have both SQL Server and RS running on the same 2003 machine, upgraded
> > from Win 2000 to 2003.
> > I am now attempting to locate hotfix 859, if you know the URL drop it
> here.
> >
> > Thanks.
> >
> > "Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > news:OLbvvSSXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > > I just looked at my notes from my install on Windows 2003. For Windows
> > 2003
> > > only, you need a hotfix for SQL Server. Seems strange that SQL Server
> > needs
> > > it but only on 2003 but there you are. It is in the installation notes
> for
> > > the install. Besides SP3a you need hotfix 859.
> > >
> > > Your situation is a bit different. Only RS is on 2003 and your SQL
> Server
> > is
> > > still on 2000 so it seems like you wouldn't need the hotfix but you
are
> > > accessing it from Windows 2003 so maybe that is the key point. In my
> case
> > > SQL Server and RS are both on Windows 2003.
> > >
> > > In any case, it won't hurt anything and it might fix your problem so I
> > > suggest installing the hotfix and see if that helps.
> > >
> > > Hope that helps.
> > >
> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > news:uETJr%23RXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > > Hi Brian,
> > > >
> > > > I had SP3 and upgraded to SP3a yesterday as well. What is RS looking
> at
> > > when
> > > > it decides that this is the wrong version?
> > > > I guess I can backup all databases and re-install SQL Server if you
> > think
> > > > that should do it. I gave that a thought already, but then it came
to
> > mind
> > > > what if it is something else and I went through that exercise for
> > nothing.
> > > >
> > > > Thanks for your ideas,
> > > >
> > > > Chris.
> > > >
> > > > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in
> message
> > > > news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> > > > > Do you have SP3a installed on your SQL2K enterprise?
> > > > >
> > > > > --
> > > > > Brian Welcker
> > > > > Group Program Manager
> > > > > SQL Server Reporting Services
> > > > >
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > >
> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
message
> > > > > news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> > > > > >I had the evaluation version running, generated beautiful
reports.
> > > > > > I upgraded my computer from Windows 2000 to 2003 and after a day
> or
> > > two
> > > > > > realized RS would not run, but it could have expired.
> > > > > > I upgraded my RS from the evaluation version to the release
> version,
> > > > > > choosing "upgrade". After the upgrade at first it wouldn't allow
> > > access
> > > > to
> > > > > > the virtual dirs (eventually I hard-coded the Admin
name/password
> in
> > > the
> > > > > > impersonation line in web.config which fixed it) and after that
it
> > > > > > complained about unable to connect to the database. I tried the
> > > rsconfig
> > > > > > utility, then it complained about unable to decrypt a key pair
and
> > it
> > > > > > suggested restoring the default, which of course I did not have
> (it
> > > > really
> > > > > > surprised me there).
> > > > > > I un-installed RS and started a fresh install. Now it says "The
> > > edition
> > > > of
> > > > > > the Report Server Database is not supported on the edition of
SQL
> > > Server
> > > > > > 2000 you have chosen".
> > > > > > Both SQL 2000 and RS are Enterprise, and the evaluation was
quite
> > > happy
> > > > > > using my SQL Server version (my machine was still Win 2000
> though).
> > > > > > I have been fighting this install for about 7 hours now (on a
> > Sunday),
> > > > > > googled, newsgroups, used bad language, etc, etc.
> > > > > > I am (or was) going to demo some (beautiful) reports to a client
> > > > tomorrow.
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||DAMN, my @.@.version is exactly the same, word for word, except for one word,
where yours says "Enterprise" mine says "Developer". It was installed close
to 3 years ago and I could swear by it that it was the Enterprise. The
evaluation version was happy, what a shame the release is not happy.
Bruce, thanks for your help.
Now I am sitting here with the Enterprise Edition CD in my hand, wondering
what will happen if I install it over the Developers.
I am going to post this question in the SQL Server newsgroup as well, if you
know the answer though, drop it here. Thanks again.
"Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:##mhJXTXEHA.2520@.TK2MSFTNGP12.phx.gbl...
> OK, just in case any of the following might help you. There were several
> things I had to do different under 2003 Server.
> 1. Hotfix 859
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSUIREF/htm/f1_rsc_installation_v1_036u.asp
> 2. Configure server with application server, asp.net (two distinct
> activities). Seems if this was an issue you would get a different error
> message
> 3. I selected built-in account. Two choices: network and system. It
defaults
> to network. I wanted system (which is how my previous configurations were
> configured).
> Other than these my installation went smoothly but then I had a clean
> install of Windows 2003 Advanced Server and SQL Server Enterprise.
> What do you get when you do a select @.@.version? I get this:
> Microsoft SQL Server 2000 - 8.00.859 (Intel X86) Sep 18 2003 12:53:45
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
Windows
> NT 5.2 (Build 3790: )
> Bruce L-C
> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> news:ePWpOETXEHA.644@.tk2msftngp13.phx.gbl...
> > Nope, did not help if this was the correct hotfix, downloaded from
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;821334
> >
> > Thanks in any case.
> >
> > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > news:Orv6o6SXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > > Hi Bruce,
> > >
> > > I have both SQL Server and RS running on the same 2003 machine,
upgraded
> > > from Win 2000 to 2003.
> > > I am now attempting to locate hotfix 859, if you know the URL drop it
> > here.
> > >
> > > Thanks.
> > >
> > > "Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > > news:OLbvvSSXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > > > I just looked at my notes from my install on Windows 2003. For
Windows
> > > 2003
> > > > only, you need a hotfix for SQL Server. Seems strange that SQL
Server
> > > needs
> > > > it but only on 2003 but there you are. It is in the installation
notes
> > for
> > > > the install. Besides SP3a you need hotfix 859.
> > > >
> > > > Your situation is a bit different. Only RS is on 2003 and your SQL
> > Server
> > > is
> > > > still on 2000 so it seems like you wouldn't need the hotfix but you
> are
> > > > accessing it from Windows 2003 so maybe that is the key point. In my
> > case
> > > > SQL Server and RS are both on Windows 2003.
> > > >
> > > > In any case, it won't hurt anything and it might fix your problem so
I
> > > > suggest installing the hotfix and see if that helps.
> > > >
> > > > Hope that helps.
> > > >
> > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > > news:uETJr%23RXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > > > Hi Brian,
> > > > >
> > > > > I had SP3 and upgraded to SP3a yesterday as well. What is RS
looking
> > at
> > > > when
> > > > > it decides that this is the wrong version?
> > > > > I guess I can backup all databases and re-install SQL Server if
you
> > > think
> > > > > that should do it. I gave that a thought already, but then it came
> to
> > > mind
> > > > > what if it is something else and I went through that exercise for
> > > nothing.
> > > > >
> > > > > Thanks for your ideas,
> > > > >
> > > > > Chris.
> > > > >
> > > > > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in
> > message
> > > > > news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> > > > > > Do you have SP3a installed on your SQL2K enterprise?
> > > > > >
> > > > > > --
> > > > > > Brian Welcker
> > > > > > Group Program Manager
> > > > > > SQL Server Reporting Services
> > > > > >
> > > > > > This posting is provided "AS IS" with no warranties, and confers
> no
> > > > > rights.
> > > > > >
> > > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
> message
> > > > > > news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> > > > > > >I had the evaluation version running, generated beautiful
> reports.
> > > > > > > I upgraded my computer from Windows 2000 to 2003 and after a
day
> > or
> > > > two
> > > > > > > realized RS would not run, but it could have expired.
> > > > > > > I upgraded my RS from the evaluation version to the release
> > version,
> > > > > > > choosing "upgrade". After the upgrade at first it wouldn't
allow
> > > > access
> > > > > to
> > > > > > > the virtual dirs (eventually I hard-coded the Admin
> name/password
> > in
> > > > the
> > > > > > > impersonation line in web.config which fixed it) and after
that
> it
> > > > > > > complained about unable to connect to the database. I tried
the
> > > > rsconfig
> > > > > > > utility, then it complained about unable to decrypt a key pair
> and
> > > it
> > > > > > > suggested restoring the default, which of course I did not
have
> > (it
> > > > > really
> > > > > > > surprised me there).
> > > > > > > I un-installed RS and started a fresh install. Now it says
"The
> > > > edition
> > > > > of
> > > > > > > the Report Server Database is not supported on the edition of
> SQL
> > > > Server
> > > > > > > 2000 you have chosen".
> > > > > > > Both SQL 2000 and RS are Enterprise, and the evaluation was
> quite
> > > > happy
> > > > > > > using my SQL Server version (my machine was still Win 2000
> > though).
> > > > > > > I have been fighting this install for about 7 hours now (on a
> > > Sunday),
> > > > > > > googled, newsgroups, used bad language, etc, etc.
> > > > > > > I am (or was) going to demo some (beautiful) reports to a
client
> > > > > tomorrow.
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||Ah ha. I was wondering about that but you seemed real certain it was
enterprise. Developer has the same features as enterprise so it is easy to
not know, that is why I had you check. I had developer and went to
enterprise but darn if I can remember if I had to unistall/reinstall or if I
could upgrade. Good news is that the problem is solved. Simple once you know
the solution <g>.
Bruce L-C
"Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
news:uFvSAFUXEHA.4000@.TK2MSFTNGP09.phx.gbl...
> DAMN, my @.@.version is exactly the same, word for word, except for one
word,
> where yours says "Enterprise" mine says "Developer". It was installed
close
> to 3 years ago and I could swear by it that it was the Enterprise. The
> evaluation version was happy, what a shame the release is not happy.
> Bruce, thanks for your help.
> Now I am sitting here with the Enterprise Edition CD in my hand, wondering
> what will happen if I install it over the Developers.
> I am going to post this question in the SQL Server newsgroup as well, if
you
> know the answer though, drop it here. Thanks again.
>
> "Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:##mhJXTXEHA.2520@.TK2MSFTNGP12.phx.gbl...
> > OK, just in case any of the following might help you. There were several
> > things I had to do different under 2003 Server.
> > 1. Hotfix 859
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSUIREF/htm/f1_rsc_installation_v1_036u.asp
> > 2. Configure server with application server, asp.net (two distinct
> > activities). Seems if this was an issue you would get a different error
> > message
> > 3. I selected built-in account. Two choices: network and system. It
> defaults
> > to network. I wanted system (which is how my previous configurations
were
> > configured).
> >
> > Other than these my installation went smoothly but then I had a clean
> > install of Windows 2003 Advanced Server and SQL Server Enterprise.
> >
> > What do you get when you do a select @.@.version? I get this:
> > Microsoft SQL Server 2000 - 8.00.859 (Intel X86) Sep 18 2003 12:53:45
> > Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
> Windows
> > NT 5.2 (Build 3790: )
> >
> > Bruce L-C
> >
> > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > news:ePWpOETXEHA.644@.tk2msftngp13.phx.gbl...
> > > Nope, did not help if this was the correct hotfix, downloaded from
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;821334
> > >
> > > Thanks in any case.
> > >
> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > news:Orv6o6SXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > > > Hi Bruce,
> > > >
> > > > I have both SQL Server and RS running on the same 2003 machine,
> upgraded
> > > > from Win 2000 to 2003.
> > > > I am now attempting to locate hotfix 859, if you know the URL drop
it
> > > here.
> > > >
> > > > Thanks.
> > > >
> > > > "Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > > > news:OLbvvSSXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > > > > I just looked at my notes from my install on Windows 2003. For
> Windows
> > > > 2003
> > > > > only, you need a hotfix for SQL Server. Seems strange that SQL
> Server
> > > > needs
> > > > > it but only on 2003 but there you are. It is in the installation
> notes
> > > for
> > > > > the install. Besides SP3a you need hotfix 859.
> > > > >
> > > > > Your situation is a bit different. Only RS is on 2003 and your SQL
> > > Server
> > > > is
> > > > > still on 2000 so it seems like you wouldn't need the hotfix but
you
> > are
> > > > > accessing it from Windows 2003 so maybe that is the key point. In
my
> > > case
> > > > > SQL Server and RS are both on Windows 2003.
> > > > >
> > > > > In any case, it won't hurt anything and it might fix your problem
so
> I
> > > > > suggest installing the hotfix and see if that helps.
> > > > >
> > > > > Hope that helps.
> > > > >
> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
message
> > > > > news:uETJr%23RXEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > > > > Hi Brian,
> > > > > >
> > > > > > I had SP3 and upgraded to SP3a yesterday as well. What is RS
> looking
> > > at
> > > > > when
> > > > > > it decides that this is the wrong version?
> > > > > > I guess I can backup all databases and re-install SQL Server if
> you
> > > > think
> > > > > > that should do it. I gave that a thought already, but then it
came
> > to
> > > > mind
> > > > > > what if it is something else and I went through that exercise
for
> > > > nothing.
> > > > > >
> > > > > > Thanks for your ideas,
> > > > > >
> > > > > > Chris.
> > > > > >
> > > > > > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in
> > > message
> > > > > > news:OZ40yyMXEHA.3512@.TK2MSFTNGP12.phx.gbl...
> > > > > > > Do you have SP3a installed on your SQL2K enterprise?
> > > > > > >
> > > > > > > --
> > > > > > > Brian Welcker
> > > > > > > Group Program Manager
> > > > > > > SQL Server Reporting Services
> > > > > > >
> > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > > > rights.
> > > > > > >
> > > > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
> > message
> > > > > > > news:uG8PvNLXEHA.796@.TK2MSFTNGP10.phx.gbl...
> > > > > > > >I had the evaluation version running, generated beautiful
> > reports.
> > > > > > > > I upgraded my computer from Windows 2000 to 2003 and after a
> day
> > > or
> > > > > two
> > > > > > > > realized RS would not run, but it could have expired.
> > > > > > > > I upgraded my RS from the evaluation version to the release
> > > version,
> > > > > > > > choosing "upgrade". After the upgrade at first it wouldn't
> allow
> > > > > access
> > > > > > to
> > > > > > > > the virtual dirs (eventually I hard-coded the Admin
> > name/password
> > > in
> > > > > the
> > > > > > > > impersonation line in web.config which fixed it) and after
> that
> > it
> > > > > > > > complained about unable to connect to the database. I tried
> the
> > > > > rsconfig
> > > > > > > > utility, then it complained about unable to decrypt a key
pair
> > and
> > > > it
> > > > > > > > suggested restoring the default, which of course I did not
> have
> > > (it
> > > > > > really
> > > > > > > > surprised me there).
> > > > > > > > I un-installed RS and started a fresh install. Now it says
> "The
> > > > > edition
> > > > > > of
> > > > > > > > the Report Server Database is not supported on the edition
of
> > SQL
> > > > > Server
> > > > > > > > 2000 you have chosen".
> > > > > > > > Both SQL 2000 and RS are Enterprise, and the evaluation was
> > quite
> > > > > happy
> > > > > > > > using my SQL Server version (my machine was still Win 2000
> > > though).
> > > > > > > > I have been fighting this install for about 7 hours now (on
a
> > > > Sunday),
> > > > > > > > googled, newsgroups, used bad language, etc, etc.
> > > > > > > > I am (or was) going to demo some (beautiful) reports to a
> client
> > > > > > tomorrow.
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
I need some information regarding Windows Mobile5.0
i am using windows mobile 5.0 .Now iam downloading the total database from remote system using synchronization.but it is a huge database.so i want to download only some part of the databse.i.e in employee table somany employees will be there.from there i want to download only one employees data from that database.
Can we do this using synchronization concept.Here i want to use XML schema.That XML file will be downloaded into the PDA and will be converted to SQLCE.And while uploading the XML file will be uploaded and the data will be stored into the SQLSERVER of the remote system.
Can anyone give me guidance in this issue sothat iam very greatful to them.
If you are using merge replication and you are pulling the entire publication to the mobile device, you might want to simply put some filters in place. you can establish horizontal or vertical filters on your publication so that only certain rows or columns in the publication propagate to the SQL CE or SQL Mobile database.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/replperf_5kx1.asp
If you want to use XML instead, you might review the 4 new Northwind sample apps such as
http://msdn.microsoft.com/library/en-us/dnppcgen/html/nw_pocket_analyze_decision_support_wm2k3_sp.asp?frame=true&_r=1
many of which use XML as a mechanism of data synchronization with SQL CE on device.
-Darren
Friday, February 24, 2012
i need help: SiteBuilder for Windows (sitebuilder-3.0.2_build060426.365_win.exe) installatio
where i can download service pack for windows server 2003
Lameck -
Can you confirm that you are running Windows 2003 Sp1 this is a pre-reg for Sitebuilder - you should confirm the other pre-reqs as well by referencing: http://www.swsoft.com/en/products/sitebuilder/win/reqs/
I would guess that your system does not have Windows 2003 SP1 installed so I would recommend going here downloading it and installing it: http://www.microsoft.com/technet/downloads/winsrvr/servicepacks/sp1/default.mspx - you can confirm its installed by right clicking on My computer on your desktop selecting properties and looking at the system details on the General Tab.
Thanks,
AWAL
|||thanks. unfortunately theyre all not win32 applications.
|||Lameck -
You should only install 1 OS Service Pack - You can't be running Windows 2003, XP and Small Business Service on the same machine - can you go to My Computer and look under General Tab in the System area and determine what OS you are running (and what Service Pack its currently at)?
Also why are you installing Exchange Service pack - is this machine an Exchange Server?
Thanks
AWAL