I have a database on a MSSQL Server 7 running on a Windows NT machine. This database works the last 4years with no problem. The database file is now 3 GB with 45 users. The last two months every single day an update error on a specific Table occurs. I cannot update a record in this table, and after this error occurs more than 100 records or more seemed to be locked. While I cannot edit the previous records I can create a new one with no problem. I have this problem once every sigle working day (ant the currious thing is that is occured from 8 to 10 in the morning every singke working day) . The table seems to work again after some hours or after one single day, or after I stop and start again the sql server service. Some times I have to wait some hours in order to manage to edit records in this table again. (I edit the records by using a program created with Microsoft Access and ODBC. When the error occurs I cannot edit the records neither by Access not by SQL Server Query Analyser).
This error doesn't occur when entering a new record, and might occur when only one user works with the specific Table. This table has 75 fields and about 70000 records. This table is the master of a table which has more than 200 fields and more than 750000 records. In the detail table I have no problems.
Similar problems not in this degree exist on a second database installation with about 25 users with the same table but running under a Windows 2000 Server machine.
Well when the problem appearead again I tried to edit the locked records by using Access ODBC, Access (adp project), Delphi with ADO-OLEDB and Delphi with native SQL drivers. The result was the same. A Timeout expired message appear. In the application log file of the MS SQLserver machine every time the the update error appears I get the following message: Could not Set Up Listen on Connection '1433'. Operating system Error 10049.
Any ideas??
Best regards,
Manolis PerrakisCan you supply the wording of the update error?
Also, since it tends to happen from 8-10 most mornings, you can check for blocking problems by running sp_who2 in Query Analyzer. If there are numbers in the "BlkBy" column, you have problems. Hopefully you will be able to figure out the blocker by the program- or host-name in the output of sp_who2.|||I don't have a solution for you. But I have experienced more than my share of timeouts and there's one thing I've learned: it's never what it says it is. But it seems to happen more the larger the number of elements there are in an index, and less on more normal databases. And we suspect it may be related to our use of EIDE drives instead of SCSI.
And I strongly suspect it has something to do with resources. For example: If you execute an update query causing SQL Server to execute a series of subqueries, and one of them hits a resource ceiling, one of the others with time out waiting for a thread to finish. The thread never finishes, because it's waiting for resources to be freed before it can continue. This happens all the time on our 1 GHZ server with 1GB of RAM.
I suggest you check all your indexes and make sure they're not clustered. Also, make sure you're not using too many connections if you can avoid it. And if you have too many tables that aren't normalized, try to fix that as well. Finally, you can do what I'm planning to do: change to MySql server or something else. IMNSHO, Sql Server isn't as robust as it could be.
I hope this helps.|||One other thing...Port 1433 is where SQL Server listens for connection requests. You're not opening the database everytime you do an update, are you?|||Thanks for the suggestions. My server is a Compaq ML350 with 3 SCSII hards disks and a Raid Controller, and about 600 MB RAM. I can see from the task manager that it uses all the resources. I might increase the RAM memory and in the next months I might get a new server.
Please tell me if there is a serious problem the fact that I also store in this server about 10000 photos with sizes about 2 GB, that are displayed as product pictures in the database program I've created.
I also have to mention that I use a lot of subqueries in the MSAccess program I use right now.
As far the connections issues, since I now use MSAccess for the clients, each table that is connected (attached) to the MSSQL Server holds internally its connection properies (datasource name, database name, username etc..), and since that I have about 200 tables attached from the SQL Server, this might create a connection problem.
I'm currently moving to Delphi 7, which has a global connection for all the tables of the same server. In this version the subqueries are replaced with optimised queries, and client datasets will be used in order to decrease the server load.
Best Regards,
Manolis Perrakis|||The data I store in image fields is usually quite a bit less than yours, but I don't think that's a problem. But I'm pretty sure the RAM is. You can improve things somewhat by making sure your logfile is on a different disk drive than the database, if you haven't done so already.
Try to get away from holding tables open where you can. Also, if you have a lot of indices on the master table, or a high number of values in the master index, I know from experience that can cause problems. Those problems can be alleviated by adding more RAM, further normalizing your database to reduce the number of keys (if that's possible), or looking at ways to reduce the amount of index storage--making sure you're not using clustered indexes, making sure that you're not using full-text indexing if you don't need it.
But I'm also wondering whether it's the bound controls that are the problem. At 8:00 is when everyone comes into work and launches the app, right? And by 10:00, app use drops down to a manageable level? Tables linked to app forms are almost always in Dynamic mode and I'm assuming that's the case here. If you were to modify your app so that the most common screens were read (releasing the recordset and holding the data in memory), and perform updates as that data was written (creating a new recordset for writing), you'd probably reduce the load on Sql Server significantly.
Not that any of this presents a panacea. I've spent the majority of my bugchasing over the past couple of years on problems with SQL Server/ADO. If I had any time at all, I would switch like a Tareyton smoker. :) But I think this problem can be solved.
Showing posts with label update. Show all posts
Showing posts with label update. Show all posts
Friday, March 30, 2012
MS SQL Update Error
I have a database on a MSSQL Server 7 running on a Windows NT machine. This database works the last 4years with no problem. The database file is now 3 GB. The last two months every single day an update error on a specific Table occurs. I cannot update a record in this table, and after this error occurs more than 100 records or more seemed to be locked. While I cannot edit the previous records I can create a new one with no problem. I have this problem once every sigle working day (ant the currious thing is that is occured from 8 to 10 in the morning every singke working day) . The table seems to work again after some hours or after one single day, or after I stop and start again the sql server service. Some times I have to wait some hours in order to manage to edit records in this table again. (I edit the records by using a program created with Microsoft Access and ODBC. When the error occurs I cannot edit the records neither by Access not by SQL Server Query Analyser).
This error doesn't occur when entering a new record, and might occur when only one user works with the specific Table. This table has 75 fields and about 70000 records.
Similar problems not in this degree exist on a second database installation with about 25 users with the same table but running under a Windows 2000 Server machine.
Any ideas??
Best Regards,
Manolis Perrakis
manolo_perrakis@.mail.grDoes the error occur when you try to edit the records using ONLY query analyzer?
Are you using an MS Access mdb file to edit the data, or are you using a Microsoft Access Data Project (ADP) file?
blindman|||Does the error occur when you try to edit the records using ONLY query analyzer?
Are you using an MS Access mdb file to edit the data, or are you using a Microsoft Access Data Project (ADP) file?
The error occurs both with Access (I'm using an mdb file connected with ODBC with SQL Server) and with the Query Analyser. When this error occurs I cannot edit this table from any computer in the network.
Therefore I'm trying to edit the table using ODBC. I haven't tried by using an ADP project, or by using another program like Delphi which uses another connection method like OLE DB.|||when you get to the point when "this" error occurrs again, can you switch to query analyzer and write an update query for a specific record?
after you get "that" error in query analyzer, paste it here. i suspect you can also get this error from sql server errorlog by double-clicking on the entry with the error. i suspect the error you're getting is referencing the total record length. if this is the case you'll need to either shrink a couple of fields or split the table into two to allow for all your fields to be updateable. to do that seemlessly for the front-end you'll have to write a view and reference this view in your inserts, updates, deletes, and selects.
This error doesn't occur when entering a new record, and might occur when only one user works with the specific Table. This table has 75 fields and about 70000 records.
Similar problems not in this degree exist on a second database installation with about 25 users with the same table but running under a Windows 2000 Server machine.
Any ideas??
Best Regards,
Manolis Perrakis
manolo_perrakis@.mail.grDoes the error occur when you try to edit the records using ONLY query analyzer?
Are you using an MS Access mdb file to edit the data, or are you using a Microsoft Access Data Project (ADP) file?
blindman|||Does the error occur when you try to edit the records using ONLY query analyzer?
Are you using an MS Access mdb file to edit the data, or are you using a Microsoft Access Data Project (ADP) file?
The error occurs both with Access (I'm using an mdb file connected with ODBC with SQL Server) and with the Query Analyser. When this error occurs I cannot edit this table from any computer in the network.
Therefore I'm trying to edit the table using ODBC. I haven't tried by using an ADP project, or by using another program like Delphi which uses another connection method like OLE DB.|||when you get to the point when "this" error occurrs again, can you switch to query analyzer and write an update query for a specific record?
after you get "that" error in query analyzer, paste it here. i suspect you can also get this error from sql server errorlog by double-clicking on the entry with the error. i suspect the error you're getting is referencing the total record length. if this is the case you'll need to either shrink a couple of fields or split the table into two to allow for all your fields to be updateable. to do that seemlessly for the front-end you'll have to write a view and reference this view in your inserts, updates, deletes, and selects.
Wednesday, March 28, 2012
MS SQL Server View Linked into MSAccess is not updateable recordset
Hi All,
How can I link a view into MS Access from MS Sql Server, that I can update as a tabble.
Thanks
LaszloInclude the columns from a defined UNIQUE INDEX on the table in your view.
-PatP|||And the table in SQL Server MUST have a primary key defined on it, or Access will not allow you to update it.|||But, the tables have primary keys, the relationships are correct, and the view is updateable on the server, but when I link it into Access then its not work anymore. Even single linked tables (including primary key) are updateable in Access just the views not work.
I found that the one solution is making query form the linked tables in Access.
How can I link a view into MS Access from MS Sql Server, that I can update as a tabble.
Thanks
LaszloInclude the columns from a defined UNIQUE INDEX on the table in your view.
-PatP|||And the table in SQL Server MUST have a primary key defined on it, or Access will not allow you to update it.|||But, the tables have primary keys, the relationships are correct, and the view is updateable on the server, but when I link it into Access then its not work anymore. Even single linked tables (including primary key) are updateable in Access just the views not work.
I found that the one solution is making query form the linked tables in Access.
Monday, March 26, 2012
Ms SQL server db options for performance issues after db corruption
Now the odd thing here is that although some of the
options will ultimatly improve performance, quite a few of
them will not.
Fistly the update statistics / create statistics. This
will improve performace but only when you change / create
something i.e. and index. I have this on my server.
Recursive triggers only allow as the wording states
recursive triggers and will not do anything to directly to
improve the performance. This is an application level
thing, personally I hate recursion.
Quoted Identifiers will not improve performance but you
may find some of your SQL will not work if you have not
had it on before.
Torn Page detection ?, important of you don't have
anything in place that can detect it, however it will
effect performance.
OK then cursor options. First rule of thumb. If you can
get away from using cursors then don't use them, they are
really slow. There are a lot of other options but its
probably better if you look it up on the net.
Other things you can try...
As you have just put in a new disk your datafiles are
going to need defragging (look up the DBCC DBREINDEX
command)
Also you may want to re-compile your SP after you perform
the re-index.
Anyway there are a LOT of other things you can try, too
many to put here so I surgest you have a look on the web.
Peter
"Choose a job you love, and you will never have to work a
day in your life."
Confucius
>--Original Message--
>Hello SQL forum readers,
>I have a customer using Ms SQL Server 2000 SP3 installed
on optical RAID-5
>Disk Array (IBM Fast200 SAN).
>After a disk failure his production db was corrupted and
since the failed
>disk was replaced, cust. restored a valid backup
>in order to support his business operations (with one day
transcations
>loss).
>We have dome a lot of troubleshooting and investigation
(traces, logs,
>dumps) in order to identify what caused the corruption.
>But now, cust. faces low performance problems.
>I have already suggested to use additionally the
following options :
>A) Auto Options:
>Auot create statistics
>Auto update statistics
>B) Recovery Options:
>Recursive Triggers
>I would be much appreciated If I could have any advise
regararding any
>additional db option setting that could assist :
>a) What about Quoted Identifiers or other SQL option?
>b) What about Torn Page Detection (recovery option)
>c) Any other cursor options that could assist?
>Is there additional MEM/CPU overhead by enabling those
options?
>I have also advised cust, to execute the command SET
SHOWPLAN_ALL in order
>to gather details abour executed statements
>Anything else I can do?
>Any advise will be much appreciated.
>Thanks in Advance
>Regards, Nick Dakoronias
>IBM Athens/Greece
>
>
>.
>
- Peter,
Thanks for your clarifications and the useful tips
- Narayana,
We try to investigate what caused the SQL performance degradation.
We supsect that the HW failure in disk array caused db corruption. This is
also verified by Ms SQL error logs and dumps.
But on the other hand, Fast optical diak array log as well as, management
console indicate that after the replacement of the
defective disk the whole RAID 5 array is healthy and the log is clear of
errors.
Regarding the Performance Benchamrk, it is just enough to mention a
performance degradation of about 70 % either using the
same array (8 x 36.4GB) or another (5 x 74.8 GB). This percentage could not
be justified by using bad indexes or triggers only.
Don't you agree?
- Curt,
This is actually an ERP oriented -business critical- application using SQL
server instances. It is related to Logistics, Products Shipment, Inventory,
etc.
___________________
My additional comments:
I also think that it is essential to determine the db queries performance by
using the SET statement to enable the SHOWPLAN, STATISTICS IO, STATISTICS
TIME, and
STATISTICS profile options. For Example:
SHOWPLAN describes the method chosen by the SQL Server query optimizer to
retrieve data. (SET SHOWPLAN_ALL).
STATISTICS TIME displays the amount of time (in milliseconds) required to
parse, compile, and execute a query. (SET STATISTICS TIME).
STATISTICS IO reports information about the number of scans, logical reads
(pages accessed in cache), and physical reads (number of times the disk was
accessed) for each table referenced in the statement. (SET STATISTICS IO).
STATISTICS PROFILE displays a result set after each executed query
representing a Profile of the execution of the query (SET STATISTICS
PROFILE)
Use Index Tuning Wizard to obtain a recommendation abour the best mix of
indexes for a database given a workload and analyze the effects of the
proposed changes, including index usage
and performance of queries in workload.
Thanks and Regards,
Nick Dakoronias
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:091601c494e4$fce077c0$a401280a@.phx.gbl...[vbcol=seagreen]
> Now the odd thing here is that although some of the
> options will ultimatly improve performance, quite a few of
> them will not.
> Fistly the update statistics / create statistics. This
> will improve performace but only when you change / create
> something i.e. and index. I have this on my server.
> Recursive triggers only allow as the wording states
> recursive triggers and will not do anything to directly to
> improve the performance. This is an application level
> thing, personally I hate recursion.
> Quoted Identifiers will not improve performance but you
> may find some of your SQL will not work if you have not
> had it on before.
> Torn Page detection ?, important of you don't have
> anything in place that can detect it, however it will
> effect performance.
> OK then cursor options. First rule of thumb. If you can
> get away from using cursors then don't use them, they are
> really slow. There are a lot of other options but its
> probably better if you look it up on the net.
> Other things you can try...
> As you have just put in a new disk your datafiles are
> going to need defragging (look up the DBCC DBREINDEX
> command)
> Also you may want to re-compile your SP after you perform
> the re-index.
> Anyway there are a LOT of other things you can try, too
> many to put here so I surgest you have a look on the web.
> Peter
> "Choose a job you love, and you will never have to work a
> day in your life."
> Confucius
>
> on optical RAID-5
> since the failed
> transcations
> (traces, logs,
> following options :
> regararding any
> options?
> SHOWPLAN_ALL in order
options will ultimatly improve performance, quite a few of
them will not.
Fistly the update statistics / create statistics. This
will improve performace but only when you change / create
something i.e. and index. I have this on my server.
Recursive triggers only allow as the wording states
recursive triggers and will not do anything to directly to
improve the performance. This is an application level
thing, personally I hate recursion.
Quoted Identifiers will not improve performance but you
may find some of your SQL will not work if you have not
had it on before.
Torn Page detection ?, important of you don't have
anything in place that can detect it, however it will
effect performance.
OK then cursor options. First rule of thumb. If you can
get away from using cursors then don't use them, they are
really slow. There are a lot of other options but its
probably better if you look it up on the net.
Other things you can try...
As you have just put in a new disk your datafiles are
going to need defragging (look up the DBCC DBREINDEX
command)
Also you may want to re-compile your SP after you perform
the re-index.
Anyway there are a LOT of other things you can try, too
many to put here so I surgest you have a look on the web.
Peter
"Choose a job you love, and you will never have to work a
day in your life."
Confucius
>--Original Message--
>Hello SQL forum readers,
>I have a customer using Ms SQL Server 2000 SP3 installed
on optical RAID-5
>Disk Array (IBM Fast200 SAN).
>After a disk failure his production db was corrupted and
since the failed
>disk was replaced, cust. restored a valid backup
>in order to support his business operations (with one day
transcations
>loss).
>We have dome a lot of troubleshooting and investigation
(traces, logs,
>dumps) in order to identify what caused the corruption.
>But now, cust. faces low performance problems.
>I have already suggested to use additionally the
following options :
>A) Auto Options:
>Auot create statistics
>Auto update statistics
>B) Recovery Options:
>Recursive Triggers
>I would be much appreciated If I could have any advise
regararding any
>additional db option setting that could assist :
>a) What about Quoted Identifiers or other SQL option?
>b) What about Torn Page Detection (recovery option)
>c) Any other cursor options that could assist?
>Is there additional MEM/CPU overhead by enabling those
options?
>I have also advised cust, to execute the command SET
SHOWPLAN_ALL in order
>to gather details abour executed statements
>Anything else I can do?
>Any advise will be much appreciated.
>Thanks in Advance
>Regards, Nick Dakoronias
>IBM Athens/Greece
>
>
>.
>
- Peter,
Thanks for your clarifications and the useful tips
- Narayana,
We try to investigate what caused the SQL performance degradation.
We supsect that the HW failure in disk array caused db corruption. This is
also verified by Ms SQL error logs and dumps.
But on the other hand, Fast optical diak array log as well as, management
console indicate that after the replacement of the
defective disk the whole RAID 5 array is healthy and the log is clear of
errors.
Regarding the Performance Benchamrk, it is just enough to mention a
performance degradation of about 70 % either using the
same array (8 x 36.4GB) or another (5 x 74.8 GB). This percentage could not
be justified by using bad indexes or triggers only.
Don't you agree?
- Curt,
This is actually an ERP oriented -business critical- application using SQL
server instances. It is related to Logistics, Products Shipment, Inventory,
etc.
___________________
My additional comments:
I also think that it is essential to determine the db queries performance by
using the SET statement to enable the SHOWPLAN, STATISTICS IO, STATISTICS
TIME, and
STATISTICS profile options. For Example:
SHOWPLAN describes the method chosen by the SQL Server query optimizer to
retrieve data. (SET SHOWPLAN_ALL).
STATISTICS TIME displays the amount of time (in milliseconds) required to
parse, compile, and execute a query. (SET STATISTICS TIME).
STATISTICS IO reports information about the number of scans, logical reads
(pages accessed in cache), and physical reads (number of times the disk was
accessed) for each table referenced in the statement. (SET STATISTICS IO).
STATISTICS PROFILE displays a result set after each executed query
representing a Profile of the execution of the query (SET STATISTICS
PROFILE)
Use Index Tuning Wizard to obtain a recommendation abour the best mix of
indexes for a database given a workload and analyze the effects of the
proposed changes, including index usage
and performance of queries in workload.
Thanks and Regards,
Nick Dakoronias
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:091601c494e4$fce077c0$a401280a@.phx.gbl...[vbcol=seagreen]
> Now the odd thing here is that although some of the
> options will ultimatly improve performance, quite a few of
> them will not.
> Fistly the update statistics / create statistics. This
> will improve performace but only when you change / create
> something i.e. and index. I have this on my server.
> Recursive triggers only allow as the wording states
> recursive triggers and will not do anything to directly to
> improve the performance. This is an application level
> thing, personally I hate recursion.
> Quoted Identifiers will not improve performance but you
> may find some of your SQL will not work if you have not
> had it on before.
> Torn Page detection ?, important of you don't have
> anything in place that can detect it, however it will
> effect performance.
> OK then cursor options. First rule of thumb. If you can
> get away from using cursors then don't use them, they are
> really slow. There are a lot of other options but its
> probably better if you look it up on the net.
> Other things you can try...
> As you have just put in a new disk your datafiles are
> going to need defragging (look up the DBCC DBREINDEX
> command)
> Also you may want to re-compile your SP after you perform
> the re-index.
> Anyway there are a LOT of other things you can try, too
> many to put here so I surgest you have a look on the web.
> Peter
> "Choose a job you love, and you will never have to work a
> day in your life."
> Confucius
>
> on optical RAID-5
> since the failed
> transcations
> (traces, logs,
> following options :
> regararding any
> options?
> SHOWPLAN_ALL in order
Friday, March 23, 2012
MS SQL Server 2005 timeout error when using Management Studio
Does anyone know, how to solve "timeout period elapsed prior to the
completion of the operation" problem which occured when I tried to update a
column value using MS SQL Server 2005 Management Studio (SMS).
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
Thanks
Hi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
>
|||Venkat N wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
The simple answer, and the one you're likely to get from this group, is
to not modify your tables using the GUI. It's simply not intended for
that use.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
completion of the operation" problem which occured when I tried to update a
column value using MS SQL Server 2005 Management Studio (SMS).
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
Thanks
Hi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
>
|||Venkat N wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
The simple answer, and the one you're likely to get from this group, is
to not modify your tables using the GUI. It's simply not intended for
that use.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
MS SQL Server 2005 timeout error when using Management Studio
Hi,
When I try to update a column value using MS SQL Server 2005 Management
Studio (SMS), I am getting "timeout period elapsed prior to the completion
of the operation".
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
Thanks
VN
Hi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:
> Hi,
> When I try to update a column value using MS SQL Server 2005 Management
> Studio (SMS), I am getting "timeout period elapsed prior to the completion
> of the operation".
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
> VN
>
>
When I try to update a column value using MS SQL Server 2005 Management
Studio (SMS), I am getting "timeout period elapsed prior to the completion
of the operation".
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
Thanks
VN
Hi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:
> Hi,
> When I try to update a column value using MS SQL Server 2005 Management
> Studio (SMS), I am getting "timeout period elapsed prior to the completion
> of the operation".
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
> VN
>
>
MS SQL Server 2005 timeout error when using Management Studio
Hi,
When I try to update a column value using MS SQL Server 2005 Management
Studio (SMS), I am getting "timeout period elapsed prior to the completion
of the operation".
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
Thanks
VNHi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:
> Hi,
> When I try to update a column value using MS SQL Server 2005 Management
> Studio (SMS), I am getting "timeout period elapsed prior to the completion
> of the operation".
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where eve
r
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having an
y
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
> VN
>
>sql
When I try to update a column value using MS SQL Server 2005 Management
Studio (SMS), I am getting "timeout period elapsed prior to the completion
of the operation".
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
Thanks
VNHi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:
> Hi,
> When I try to update a column value using MS SQL Server 2005 Management
> Studio (SMS), I am getting "timeout period elapsed prior to the completion
> of the operation".
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where eve
r
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having an
y
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
> VN
>
>sql
MS SQL Server 2005 timeout error when using Management Studio
Does anyone know, how to solve "timeout period elapsed prior to the
completion of the operation" problem which occured when I tried to update a
column value using MS SQL Server 2005 Management Studio (SMS).
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
ThanksHi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update
a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where eve
r
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having an
y
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
>|||Venkat N wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update
a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where eve
r
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having an
y
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
The simple answer, and the one you're likely to get from this group, is
to not modify your tables using the GUI. It's simply not intended for
that use.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
completion of the operation" problem which occured when I tried to update a
column value using MS SQL Server 2005 Management Studio (SMS).
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
ThanksHi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update
a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where eve
r
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having an
y
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
>|||Venkat N wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update
a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where eve
r
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having an
y
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
The simple answer, and the one you're likely to get from this group, is
to not modify your tables using the GUI. It's simply not intended for
that use.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
MS SQL Server 2005 timeout error when using Management Studio
Does anyone know, how to solve "timeout period elapsed prior to the
completion of the operation" problem which occured when I tried to update a
column value using MS SQL Server 2005 Management Studio (SMS).
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
ThanksHi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
>|||Venkat N wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
The simple answer, and the one you're likely to get from this group, is
to not modify your tables using the GUI. It's simply not intended for
that use.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
completion of the operation" problem which occured when I tried to update a
column value using MS SQL Server 2005 Management Studio (SMS).
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
ThanksHi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
>|||Venkat N wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
The simple answer, and the one you're likely to get from this group, is
to not modify your tables using the GUI. It's simply not intended for
that use.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
Wednesday, March 21, 2012
MS SQL Server 2000: Can Insert New Rows, but can't Update or Delete!!
I'm facing a strange problem here (SQL Server 2000).
I can Insert new rows from My ASP.NET 2.0 Pages but Can't Update or Delete.
usualy I test and build my web applications offline on my home workstation before I uppload them to my Server (Windows Server 2003 Standard), and I make sure that its error free.
The problem goes as follows:
1- I created a data grid that you can insert, delete and update and it worked fine when I tested it on my home computer.
2- When I updated the application to my server, I've noticed that I can Insert new columns to the database but When I try to update or delete the old columns, it doesn't allow me (so I have to use interprise manager to delete them from under- using same username and password!!!!).
I can Insert new rows from My ASP.NET 2.0 Pages but Can't Update or Delete.
usualy I test and build my web applications offline on my home workstation before I uppload them to my Server (Windows Server 2003 Standard), and I make sure that its error free.
The problem goes as follows:
1- I created a data grid that you can insert, delete and update and it worked fine when I tested it on my home computer.
2- When I updated the application to my server, I've noticed that I can Insert new columns to the database but When I try to update or delete the old columns, it doesn't allow me (so I have to use interprise manager to delete them from under- using same username and password!!!!).
I've never faced anything like this before, so please if anyone can give me any advice...
The problem only happened when I was using ASP.NET 2.0 Beta on my Home computer, and the full version on my server. so it was obvious that i need to install the same thing on both computers. but when I did I had to reconfigure my connection to accomodate the changes with the version. and now its working fine...
MS SQL Server 2000: Can Insert New Rows, but can't Update or Delete!!
I'm facing a strange problem here (SQL Server 2000).
I can Insert new rows from My ASP.NET 2.0 Pages but Can't Update or Delete.
usualy I test and build my web applications offline on my home workstation before I uppload them to my Server (Windows Server 2003 Standard), and I make sure that its error free.
The problem goes as follows:
1- I created a data grid that you can insert, delete and update and it worked fine when I tested it on my home computer.
2- When I updated the application to my server, I've noticed that I can Insert new columns to the database but When I try to update or delete the old columns, it doesn't allow me (so I have to use interprise manager to delete them from under- using same username and password!!!!).
I can Insert new rows from My ASP.NET 2.0 Pages but Can't Update or Delete.
usualy I test and build my web applications offline on my home workstation before I uppload them to my Server (Windows Server 2003 Standard), and I make sure that its error free.
The problem goes as follows:
1- I created a data grid that you can insert, delete and update and it worked fine when I tested it on my home computer.
2- When I updated the application to my server, I've noticed that I can Insert new columns to the database but When I try to update or delete the old columns, it doesn't allow me (so I have to use interprise manager to delete them from under- using same username and password!!!!).
I've never faced anything like this before, so please if anyone can give me any advice...
The problem only happened when I was using ASP.NET 2.0 Beta on my Home computer, and the full version on my server. so it was obvious that i need to install the same thing on both computers. but when I did I had to reconfigure my connection to accomodate the changes with the version. and now its working fine...
sqlFriday, March 9, 2012
MS SQL Analysis Services - Database Role Manager
Good day,
I try to update the OLAP database role at MS SQL Analysia Services and it is
prompt the following error message:
some of the cubes could not be updated.
Errors:
Unable to update role in cube INVENTORY.
Cannot update. Database or object is read-only.
Please find my servers information:
MS SQL Server 2000
- Service Pack 3
MS Windows 2003 Server
- Version 5.2 (Build 3790.srv03_rtm.030324-2048)
And also found that I could not remove "read-only" attribute at MS Windows
2003 Server.
Please help.
Happy day,
Please inform that I found the solution which MS Windows Server 2003 is
require set the permission rights.
Thanks.
"Sam" <cybersam88@.hotmail.com> wrote in message
news:Ozrv$LHaEHA.3112@.TK2MSFTNGP09.phx.gbl...
> Good day,
> I try to update the OLAP database role at MS SQL Analysia Services and it
is
> prompt the following error message:
> some of the cubes could not be updated.
> Errors:
> Unable to update role in cube INVENTORY.
> Cannot update. Database or object is read-only.
> Please find my servers information:
> MS SQL Server 2000
> - Service Pack 3
> MS Windows 2003 Server
> - Version 5.2 (Build 3790.srv03_rtm.030324-2048)
> And also found that I could not remove "read-only" attribute at MS Windows
> 2003 Server.
> Please help.
>
I try to update the OLAP database role at MS SQL Analysia Services and it is
prompt the following error message:
some of the cubes could not be updated.
Errors:
Unable to update role in cube INVENTORY.
Cannot update. Database or object is read-only.
Please find my servers information:
MS SQL Server 2000
- Service Pack 3
MS Windows 2003 Server
- Version 5.2 (Build 3790.srv03_rtm.030324-2048)
And also found that I could not remove "read-only" attribute at MS Windows
2003 Server.
Please help.
Happy day,
Please inform that I found the solution which MS Windows Server 2003 is
require set the permission rights.
Thanks.
"Sam" <cybersam88@.hotmail.com> wrote in message
news:Ozrv$LHaEHA.3112@.TK2MSFTNGP09.phx.gbl...
> Good day,
> I try to update the OLAP database role at MS SQL Analysia Services and it
is
> prompt the following error message:
> some of the cubes could not be updated.
> Errors:
> Unable to update role in cube INVENTORY.
> Cannot update. Database or object is read-only.
> Please find my servers information:
> MS SQL Server 2000
> - Service Pack 3
> MS Windows 2003 Server
> - Version 5.2 (Build 3790.srv03_rtm.030324-2048)
> And also found that I could not remove "read-only" attribute at MS Windows
> 2003 Server.
> Please help.
>
MS SQL Analysis Services - Database Role Manager
Good day,
I try to update the OLAP database role at MS SQL Analysia Services and it is
prompt the following error message:
---
some of the cubes could not be updated.
Errors:
Unable to update role in cube INVENTORY.
Cannot update. Database or object is read-only.
---
Please find my servers information:
MS SQL Server 2000
- Service Pack 3
MS Windows 2003 Server
- Version 5.2 (Build 3790.srv03_rtm.030324-2048)
And also found that I could not remove "read-only" attribute at MS Windows
2003 Server.
Please help.Happy day,
Please inform that I found the solution which MS Windows Server 2003 is
require set the permission rights.
Thanks.
"Sam" <cybersam88@.hotmail.com> wrote in message
news:Ozrv$LHaEHA.3112@.TK2MSFTNGP09.phx.gbl...
> Good day,
> I try to update the OLAP database role at MS SQL Analysia Services and it
is
> prompt the following error message:
> ---
> some of the cubes could not be updated.
> Errors:
> Unable to update role in cube INVENTORY.
> Cannot update. Database or object is read-only.
> ---
> Please find my servers information:
> MS SQL Server 2000
> - Service Pack 3
> MS Windows 2003 Server
> - Version 5.2 (Build 3790.srv03_rtm.030324-2048)
> And also found that I could not remove "read-only" attribute at MS Windows
> 2003 Server.
> Please help.
>
I try to update the OLAP database role at MS SQL Analysia Services and it is
prompt the following error message:
---
some of the cubes could not be updated.
Errors:
Unable to update role in cube INVENTORY.
Cannot update. Database or object is read-only.
---
Please find my servers information:
MS SQL Server 2000
- Service Pack 3
MS Windows 2003 Server
- Version 5.2 (Build 3790.srv03_rtm.030324-2048)
And also found that I could not remove "read-only" attribute at MS Windows
2003 Server.
Please help.Happy day,
Please inform that I found the solution which MS Windows Server 2003 is
require set the permission rights.
Thanks.
"Sam" <cybersam88@.hotmail.com> wrote in message
news:Ozrv$LHaEHA.3112@.TK2MSFTNGP09.phx.gbl...
> Good day,
> I try to update the OLAP database role at MS SQL Analysia Services and it
is
> prompt the following error message:
> ---
> some of the cubes could not be updated.
> Errors:
> Unable to update role in cube INVENTORY.
> Cannot update. Database or object is read-only.
> ---
> Please find my servers information:
> MS SQL Server 2000
> - Service Pack 3
> MS Windows 2003 Server
> - Version 5.2 (Build 3790.srv03_rtm.030324-2048)
> And also found that I could not remove "read-only" attribute at MS Windows
> 2003 Server.
> Please help.
>
MS SQL Analysis Services - Database Role Manager
Good day,
I try to update the OLAP database role at MS SQL Analysia Services and it is
prompt the following error message:
---
some of the cubes could not be updated.
Errors:
Unable to update role in cube INVENTORY.
Cannot update. Database or object is read-only.
---
Please find my servers information:
MS SQL Server 2000
- Service Pack 3
MS Windows 2003 Server
- Version 5.2 (Build 3790.srv03_rtm.030324-2048)
And also found that I could not remove "read-only" attribute at MS Windows
2003 Server.
Please help.Happy day,
Please inform that I found the solution which MS Windows Server 2003 is
require set the permission rights.
Thanks.
"Sam" <cybersam88@.hotmail.com> wrote in message
news:Ozrv$LHaEHA.3112@.TK2MSFTNGP09.phx.gbl...
> Good day,
> I try to update the OLAP database role at MS SQL Analysia Services and it
is
> prompt the following error message:
> ---
> some of the cubes could not be updated.
> Errors:
> Unable to update role in cube INVENTORY.
> Cannot update. Database or object is read-only.
> ---
> Please find my servers information:
> MS SQL Server 2000
> - Service Pack 3
> MS Windows 2003 Server
> - Version 5.2 (Build 3790.srv03_rtm.030324-2048)
> And also found that I could not remove "read-only" attribute at MS Windows
> 2003 Server.
> Please help.
>
I try to update the OLAP database role at MS SQL Analysia Services and it is
prompt the following error message:
---
some of the cubes could not be updated.
Errors:
Unable to update role in cube INVENTORY.
Cannot update. Database or object is read-only.
---
Please find my servers information:
MS SQL Server 2000
- Service Pack 3
MS Windows 2003 Server
- Version 5.2 (Build 3790.srv03_rtm.030324-2048)
And also found that I could not remove "read-only" attribute at MS Windows
2003 Server.
Please help.Happy day,
Please inform that I found the solution which MS Windows Server 2003 is
require set the permission rights.
Thanks.
"Sam" <cybersam88@.hotmail.com> wrote in message
news:Ozrv$LHaEHA.3112@.TK2MSFTNGP09.phx.gbl...
> Good day,
> I try to update the OLAP database role at MS SQL Analysia Services and it
is
> prompt the following error message:
> ---
> some of the cubes could not be updated.
> Errors:
> Unable to update role in cube INVENTORY.
> Cannot update. Database or object is read-only.
> ---
> Please find my servers information:
> MS SQL Server 2000
> - Service Pack 3
> MS Windows 2003 Server
> - Version 5.2 (Build 3790.srv03_rtm.030324-2048)
> And also found that I could not remove "read-only" attribute at MS Windows
> 2003 Server.
> Please help.
>
Saturday, February 25, 2012
MS SQL 2000 Service Pack 4 schedule
Hi,
Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
some notifications about it couple month ago but the link takes me to another
product today.
We would like to be ready for new Service Pack and because of this i would
like to get estimated schedule of it.
Thanks
--
Eduard Timchenko
Business Technology Solutions Group
Verint SystemsHi
It is in beta. Everyone is expecting it in the next few weeks. No firm date
has been announced.
Regards
Mike
"Eduard Timchenko" wrote:
> Hi,
> Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
> some notifications about it couple month ago but the link takes me to another
> product today.
> We would like to be ready for new Service Pack and because of this i would
> like to get estimated schedule of it.
> Thanks
> --
> Eduard Timchenko
> Business Technology Solutions Group
> Verint Systems|||Hi Eduard,
The final release date of SQL2K SP4 has not been determined. But SQL Server
2000 Service Pack 4 Beta has been released. You can view the following page
to find more information about it:
http://support.microsoft.com/?id=290211
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: MS SQL 2000 Service Pack 4 schedule
>thread-index: AcU/MJpPyi/sRnNkRxWK332tUhpWGA==>X-WBNR-Posting-Host: 193.27.93.1
>From: "=?Utf-8?B?RWR1YXJkIFRpbWNoZW5rbw==?=" <etimche@.newsgroup.nospam>
>Subject: MS SQL 2000 Service Pack 4 schedule
>Date: Tue, 12 Apr 2005 00:24:02 -0700
>Lines: 13
>Message-ID: <5E14C38C-74E7-4BDF-B6F6-779C05F1C946@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:52094
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi,
>Could you please update me if the MS SQL 2000 SP 4 still scheduled? I
found
>some notifications about it couple month ago but the link takes me to
another
>product today.
>We would like to be ready for new Service Pack and because of this i would
>like to get estimated schedule of it.
>Thanks
>--
>Eduard Timchenko
>Business Technology Solutions Group
>Verint Systems
>
Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
some notifications about it couple month ago but the link takes me to another
product today.
We would like to be ready for new Service Pack and because of this i would
like to get estimated schedule of it.
Thanks
--
Eduard Timchenko
Business Technology Solutions Group
Verint SystemsHi
It is in beta. Everyone is expecting it in the next few weeks. No firm date
has been announced.
Regards
Mike
"Eduard Timchenko" wrote:
> Hi,
> Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
> some notifications about it couple month ago but the link takes me to another
> product today.
> We would like to be ready for new Service Pack and because of this i would
> like to get estimated schedule of it.
> Thanks
> --
> Eduard Timchenko
> Business Technology Solutions Group
> Verint Systems|||Hi Eduard,
The final release date of SQL2K SP4 has not been determined. But SQL Server
2000 Service Pack 4 Beta has been released. You can view the following page
to find more information about it:
http://support.microsoft.com/?id=290211
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: MS SQL 2000 Service Pack 4 schedule
>thread-index: AcU/MJpPyi/sRnNkRxWK332tUhpWGA==>X-WBNR-Posting-Host: 193.27.93.1
>From: "=?Utf-8?B?RWR1YXJkIFRpbWNoZW5rbw==?=" <etimche@.newsgroup.nospam>
>Subject: MS SQL 2000 Service Pack 4 schedule
>Date: Tue, 12 Apr 2005 00:24:02 -0700
>Lines: 13
>Message-ID: <5E14C38C-74E7-4BDF-B6F6-779C05F1C946@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:52094
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi,
>Could you please update me if the MS SQL 2000 SP 4 still scheduled? I
found
>some notifications about it couple month ago but the link takes me to
another
>product today.
>We would like to be ready for new Service Pack and because of this i would
>like to get estimated schedule of it.
>Thanks
>--
>Eduard Timchenko
>Business Technology Solutions Group
>Verint Systems
>
MS SQL 2000 Service Pack 4 schedule
Hi,
Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
some notifications about it couple month ago but the link takes me to anothe
r
product today.
We would like to be ready for new Service Pack and because of this i would
like to get estimated schedule of it.
Thanks
--
Eduard Timchenko
Business Technology Solutions Group
Verint SystemsHi
It is in beta. Everyone is expecting it in the next few weeks. No firm date
has been announced.
Regards
Mike
"Eduard Timchenko" wrote:
> Hi,
> Could you please update me if the MS SQL 2000 SP 4 still scheduled? I foun
d
> some notifications about it couple month ago but the link takes me to anot
her
> product today.
> We would like to be ready for new Service Pack and because of this i would
> like to get estimated schedule of it.
> Thanks
> --
> Eduard Timchenko
> Business Technology Solutions Group
> Verint Systems|||Hi Eduard,
The final release date of SQL2K SP4 has not been determined. But SQL Server
2000 Service Pack 4 Beta has been released. You can view the following page
to find more information about it:
http://support.microsoft.com/?id=290211
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: MS SQL 2000 Service Pack 4 schedule
>thread-index: AcU/MJpPyi/sRnNkRxWK332tUhpWGA==
>X-WBNR-Posting-Host: 193.27.93.1
>From: "examnotes" <etimche@.newsgroup.nospam>
>Subject: MS SQL 2000 Service Pack 4 schedule
>Date: Tue, 12 Apr 2005 00:24:02 -0700
>Lines: 13
>Message-ID: <5E14C38C-74E7-4BDF-B6F6-779C05F1C946@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:52094
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi,
>Could you please update me if the MS SQL 2000 SP 4 still scheduled? I
found
>some notifications about it couple month ago but the link takes me to
another
>product today.
>We would like to be ready for new Service Pack and because of this i would
>like to get estimated schedule of it.
>Thanks
>--
>Eduard Timchenko
>Business Technology Solutions Group
>Verint Systems
>
Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
some notifications about it couple month ago but the link takes me to anothe
r
product today.
We would like to be ready for new Service Pack and because of this i would
like to get estimated schedule of it.
Thanks
--
Eduard Timchenko
Business Technology Solutions Group
Verint SystemsHi
It is in beta. Everyone is expecting it in the next few weeks. No firm date
has been announced.
Regards
Mike
"Eduard Timchenko" wrote:
> Hi,
> Could you please update me if the MS SQL 2000 SP 4 still scheduled? I foun
d
> some notifications about it couple month ago but the link takes me to anot
her
> product today.
> We would like to be ready for new Service Pack and because of this i would
> like to get estimated schedule of it.
> Thanks
> --
> Eduard Timchenko
> Business Technology Solutions Group
> Verint Systems|||Hi Eduard,
The final release date of SQL2K SP4 has not been determined. But SQL Server
2000 Service Pack 4 Beta has been released. You can view the following page
to find more information about it:
http://support.microsoft.com/?id=290211
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: MS SQL 2000 Service Pack 4 schedule
>thread-index: AcU/MJpPyi/sRnNkRxWK332tUhpWGA==
>X-WBNR-Posting-Host: 193.27.93.1
>From: "examnotes" <etimche@.newsgroup.nospam>
>Subject: MS SQL 2000 Service Pack 4 schedule
>Date: Tue, 12 Apr 2005 00:24:02 -0700
>Lines: 13
>Message-ID: <5E14C38C-74E7-4BDF-B6F6-779C05F1C946@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:52094
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi,
>Could you please update me if the MS SQL 2000 SP 4 still scheduled? I
found
>some notifications about it couple month ago but the link takes me to
another
>product today.
>We would like to be ready for new Service Pack and because of this i would
>like to get estimated schedule of it.
>Thanks
>--
>Eduard Timchenko
>Business Technology Solutions Group
>Verint Systems
>
MS SQL 2000 Service Pack 4 schedule
Hi,
Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
some notifications about it couple month ago but the link takes me to another
product today.
We would like to be ready for new Service Pack and because of this i would
like to get estimated schedule of it.
Thanks
Eduard Timchenko
Business Technology Solutions Group
Verint Systems
Hi
It is in beta. Everyone is expecting it in the next few weeks. No firm date
has been announced.
Regards
Mike
"Eduard Timchenko" wrote:
> Hi,
> Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
> some notifications about it couple month ago but the link takes me to another
> product today.
> We would like to be ready for new Service Pack and because of this i would
> like to get estimated schedule of it.
> Thanks
> --
> Eduard Timchenko
> Business Technology Solutions Group
> Verint Systems
|||Hi Eduard,
The final release date of SQL2K SP4 has not been determined. But SQL Server
2000 Service Pack 4 Beta has been released. You can view the following page
to find more information about it:
http://support.microsoft.com/?id=290211
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: MS SQL 2000 Service Pack 4 schedule
>thread-index: AcU/MJpPyi/sRnNkRxWK332tUhpWGA==
>X-WBNR-Posting-Host: 193.27.93.1
>From: "=?Utf-8?B?RWR1YXJkIFRpbWNoZW5rbw==?=" <etimche@.newsgroup.nospam>
>Subject: MS SQL 2000 Service Pack 4 schedule
>Date: Tue, 12 Apr 2005 00:24:02 -0700
>Lines: 13
>Message-ID: <5E14C38C-74E7-4BDF-B6F6-779C05F1C946@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:52094
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi,
>Could you please update me if the MS SQL 2000 SP 4 still scheduled? I
found
>some notifications about it couple month ago but the link takes me to
another
>product today.
>We would like to be ready for new Service Pack and because of this i would
>like to get estimated schedule of it.
>Thanks
>--
>Eduard Timchenko
>Business Technology Solutions Group
>Verint Systems
>
Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
some notifications about it couple month ago but the link takes me to another
product today.
We would like to be ready for new Service Pack and because of this i would
like to get estimated schedule of it.
Thanks
Eduard Timchenko
Business Technology Solutions Group
Verint Systems
Hi
It is in beta. Everyone is expecting it in the next few weeks. No firm date
has been announced.
Regards
Mike
"Eduard Timchenko" wrote:
> Hi,
> Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
> some notifications about it couple month ago but the link takes me to another
> product today.
> We would like to be ready for new Service Pack and because of this i would
> like to get estimated schedule of it.
> Thanks
> --
> Eduard Timchenko
> Business Technology Solutions Group
> Verint Systems
|||Hi Eduard,
The final release date of SQL2K SP4 has not been determined. But SQL Server
2000 Service Pack 4 Beta has been released. You can view the following page
to find more information about it:
http://support.microsoft.com/?id=290211
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: MS SQL 2000 Service Pack 4 schedule
>thread-index: AcU/MJpPyi/sRnNkRxWK332tUhpWGA==
>X-WBNR-Posting-Host: 193.27.93.1
>From: "=?Utf-8?B?RWR1YXJkIFRpbWNoZW5rbw==?=" <etimche@.newsgroup.nospam>
>Subject: MS SQL 2000 Service Pack 4 schedule
>Date: Tue, 12 Apr 2005 00:24:02 -0700
>Lines: 13
>Message-ID: <5E14C38C-74E7-4BDF-B6F6-779C05F1C946@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:52094
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi,
>Could you please update me if the MS SQL 2000 SP 4 still scheduled? I
found
>some notifications about it couple month ago but the link takes me to
another
>product today.
>We would like to be ready for new Service Pack and because of this i would
>like to get estimated schedule of it.
>Thanks
>--
>Eduard Timchenko
>Business Technology Solutions Group
>Verint Systems
>
Monday, February 20, 2012
MS SBS 2003 and RS
Hi,
I have installed SBS 2003 premium andSQL Server 2000 on my server with
default settings and patched it using Windows Update site. Also, installed
SQL Server reporting services. During setup, it warned me the Sharepoint is
installed (I don't know how Sharepoint got installed) and at the end, it
failed to initialize reporting services. Now, when I enter
"localhost/reports" in address line of IE, I get this error message:
The underlying connection was closed: Unable to connect to the remote
server.
I checked SRM*.log error log and found an error message:
<Func Name='Do_Activate_ReportService'>
<Func Name='CreateProccessAndWait'>
Error reported by child process:
Failure starting the web service:
The Report Server Web service has not generated a public key. The service
may not have started successfully. Check the log files for more
information.
<EndFunc Name='CreateProccessAndWait' Return='1603' GetLastError='0'>
Error 1603 Launching RSActivate.exe:
C:\DOCUME~1\alim\LOCALS~1\Temp\RSActivate.exe
"C:\DOCUME~1\alim\LOCALS~1\Temp\RSActivate.exe" /c "C:\Program
Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\RSReportServer.config"
Do_Activate_ReportService: Activation Failed!
<EndFunc Name='Do_Activate_ReportService' Return='0' GetLastError='0'>
<EndFunc Name='RedirectorCAX' Return='0' GetLastError='0'>
---
When I execute RSActivate on command line, I get the same error (The Report
Server Web service has not generated a public key).
I played with settings of reporting services installation (service account
and SQL Server user) in hope to get it installed successfully but it always
fails.
Do you have any idea about my problem?Alex
I had a similar issue: I had use a domain user account; the service now
starts.
Kic
"Alex" <alim@.rogers.com> wrote in message
news:#mjXxZy$EHA.2032@.tk2msftngp13.phx.gbl...
> Hi,
> I have installed SBS 2003 premium andSQL Server 2000 on my server with
> default settings and patched it using Windows Update site. Also, installed
> SQL Server reporting services. During setup, it warned me the Sharepoint
is
> installed (I don't know how Sharepoint got installed) and at the end, it
> failed to initialize reporting services. Now, when I enter
> "localhost/reports" in address line of IE, I get this error message:
> The underlying connection was closed: Unable to connect to the remote
> server.
> I checked SRM*.log error log and found an error message:
> <Func Name='Do_Activate_ReportService'>
> <Func Name='CreateProccessAndWait'>
> Error reported by child process:
> Failure starting the web service:
> The Report Server Web service has not generated a public key. The service
> may not have started successfully. Check the log files for more
> information.
> <EndFunc Name='CreateProccessAndWait' Return='1603' GetLastError='0'>
> Error 1603 Launching RSActivate.exe:
> C:\DOCUME~1\alim\LOCALS~1\Temp\RSActivate.exe
> "C:\DOCUME~1\alim\LOCALS~1\Temp\RSActivate.exe" /c "C:\Program
> Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\RSReportServer.config"
> Do_Activate_ReportService: Activation Failed!
> <EndFunc Name='Do_Activate_ReportService' Return='0' GetLastError='0'>
> <EndFunc Name='RedirectorCAX' Return='0' GetLastError='0'>
> ---
> When I execute RSActivate on command line, I get the same error (The
Report
> Server Web service has not generated a public key).
> I played with settings of reporting services installation (service account
> and SQL Server user) in hope to get it installed successfully but it
always
> fails.
> Do you have any idea about my problem?
>|||Thanks Kic for the reply.
Domain user account for service account or SQL Server access?
Alex
"kic" <kic1999@.stop.the.damn.spam.hot.mail.com> wrote in message
news:uep9mb1$EHA.4004@.tk2msftngp13.phx.gbl...
> Alex
> I had a similar issue: I had use a domain user account; the service now
> starts.
> Kic
> "Alex" <alim@.rogers.com> wrote in message
> news:#mjXxZy$EHA.2032@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > I have installed SBS 2003 premium andSQL Server 2000 on my server with
> > default settings and patched it using Windows Update site. Also,
installed
> > SQL Server reporting services. During setup, it warned me the Sharepoint
> is
> > installed (I don't know how Sharepoint got installed) and at the end, it
> > failed to initialize reporting services. Now, when I enter
> > "localhost/reports" in address line of IE, I get this error message:
> > The underlying connection was closed: Unable to connect to the remote
> > server.
> >
> > I checked SRM*.log error log and found an error message:
> > <Func Name='Do_Activate_ReportService'>
> > <Func Name='CreateProccessAndWait'>
> > Error reported by child process:
> > Failure starting the web service:
> > The Report Server Web service has not generated a public key. The
service
> > may not have started successfully. Check the log files for more
> > information.
> >
> > <EndFunc Name='CreateProccessAndWait' Return='1603' GetLastError='0'>
> > Error 1603 Launching RSActivate.exe:
> > C:\DOCUME~1\alim\LOCALS~1\Temp\RSActivate.exe
> > "C:\DOCUME~1\alim\LOCALS~1\Temp\RSActivate.exe" /c "C:\Program
> > Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\ReportServer\RSReportServer.config"
> > Do_Activate_ReportService: Activation Failed!
> > <EndFunc Name='Do_Activate_ReportService' Return='0' GetLastError='0'>
> > <EndFunc Name='RedirectorCAX' Return='0' GetLastError='0'>
> > ---
> >
> > When I execute RSActivate on command line, I get the same error (The
> Report
> > Server Web service has not generated a public key).
> > I played with settings of reporting services installation (service
account
> > and SQL Server user) in hope to get it installed successfully but it
> always
> > fails.
> >
> > Do you have any idea about my problem?
> >
> >
>
I have installed SBS 2003 premium andSQL Server 2000 on my server with
default settings and patched it using Windows Update site. Also, installed
SQL Server reporting services. During setup, it warned me the Sharepoint is
installed (I don't know how Sharepoint got installed) and at the end, it
failed to initialize reporting services. Now, when I enter
"localhost/reports" in address line of IE, I get this error message:
The underlying connection was closed: Unable to connect to the remote
server.
I checked SRM*.log error log and found an error message:
<Func Name='Do_Activate_ReportService'>
<Func Name='CreateProccessAndWait'>
Error reported by child process:
Failure starting the web service:
The Report Server Web service has not generated a public key. The service
may not have started successfully. Check the log files for more
information.
<EndFunc Name='CreateProccessAndWait' Return='1603' GetLastError='0'>
Error 1603 Launching RSActivate.exe:
C:\DOCUME~1\alim\LOCALS~1\Temp\RSActivate.exe
"C:\DOCUME~1\alim\LOCALS~1\Temp\RSActivate.exe" /c "C:\Program
Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\RSReportServer.config"
Do_Activate_ReportService: Activation Failed!
<EndFunc Name='Do_Activate_ReportService' Return='0' GetLastError='0'>
<EndFunc Name='RedirectorCAX' Return='0' GetLastError='0'>
---
When I execute RSActivate on command line, I get the same error (The Report
Server Web service has not generated a public key).
I played with settings of reporting services installation (service account
and SQL Server user) in hope to get it installed successfully but it always
fails.
Do you have any idea about my problem?Alex
I had a similar issue: I had use a domain user account; the service now
starts.
Kic
"Alex" <alim@.rogers.com> wrote in message
news:#mjXxZy$EHA.2032@.tk2msftngp13.phx.gbl...
> Hi,
> I have installed SBS 2003 premium andSQL Server 2000 on my server with
> default settings and patched it using Windows Update site. Also, installed
> SQL Server reporting services. During setup, it warned me the Sharepoint
is
> installed (I don't know how Sharepoint got installed) and at the end, it
> failed to initialize reporting services. Now, when I enter
> "localhost/reports" in address line of IE, I get this error message:
> The underlying connection was closed: Unable to connect to the remote
> server.
> I checked SRM*.log error log and found an error message:
> <Func Name='Do_Activate_ReportService'>
> <Func Name='CreateProccessAndWait'>
> Error reported by child process:
> Failure starting the web service:
> The Report Server Web service has not generated a public key. The service
> may not have started successfully. Check the log files for more
> information.
> <EndFunc Name='CreateProccessAndWait' Return='1603' GetLastError='0'>
> Error 1603 Launching RSActivate.exe:
> C:\DOCUME~1\alim\LOCALS~1\Temp\RSActivate.exe
> "C:\DOCUME~1\alim\LOCALS~1\Temp\RSActivate.exe" /c "C:\Program
> Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\RSReportServer.config"
> Do_Activate_ReportService: Activation Failed!
> <EndFunc Name='Do_Activate_ReportService' Return='0' GetLastError='0'>
> <EndFunc Name='RedirectorCAX' Return='0' GetLastError='0'>
> ---
> When I execute RSActivate on command line, I get the same error (The
Report
> Server Web service has not generated a public key).
> I played with settings of reporting services installation (service account
> and SQL Server user) in hope to get it installed successfully but it
always
> fails.
> Do you have any idea about my problem?
>|||Thanks Kic for the reply.
Domain user account for service account or SQL Server access?
Alex
"kic" <kic1999@.stop.the.damn.spam.hot.mail.com> wrote in message
news:uep9mb1$EHA.4004@.tk2msftngp13.phx.gbl...
> Alex
> I had a similar issue: I had use a domain user account; the service now
> starts.
> Kic
> "Alex" <alim@.rogers.com> wrote in message
> news:#mjXxZy$EHA.2032@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > I have installed SBS 2003 premium andSQL Server 2000 on my server with
> > default settings and patched it using Windows Update site. Also,
installed
> > SQL Server reporting services. During setup, it warned me the Sharepoint
> is
> > installed (I don't know how Sharepoint got installed) and at the end, it
> > failed to initialize reporting services. Now, when I enter
> > "localhost/reports" in address line of IE, I get this error message:
> > The underlying connection was closed: Unable to connect to the remote
> > server.
> >
> > I checked SRM*.log error log and found an error message:
> > <Func Name='Do_Activate_ReportService'>
> > <Func Name='CreateProccessAndWait'>
> > Error reported by child process:
> > Failure starting the web service:
> > The Report Server Web service has not generated a public key. The
service
> > may not have started successfully. Check the log files for more
> > information.
> >
> > <EndFunc Name='CreateProccessAndWait' Return='1603' GetLastError='0'>
> > Error 1603 Launching RSActivate.exe:
> > C:\DOCUME~1\alim\LOCALS~1\Temp\RSActivate.exe
> > "C:\DOCUME~1\alim\LOCALS~1\Temp\RSActivate.exe" /c "C:\Program
> > Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\ReportServer\RSReportServer.config"
> > Do_Activate_ReportService: Activation Failed!
> > <EndFunc Name='Do_Activate_ReportService' Return='0' GetLastError='0'>
> > <EndFunc Name='RedirectorCAX' Return='0' GetLastError='0'>
> > ---
> >
> > When I execute RSActivate on command line, I get the same error (The
> Report
> > Server Web service has not generated a public key).
> > I played with settings of reporting services installation (service
account
> > and SQL Server user) in hope to get it installed successfully but it
> always
> > fails.
> >
> > Do you have any idea about my problem?
> >
> >
>
Subscribe to:
Posts (Atom)