![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Does PTS connect to the repository or just look at the datafiles? |
|
I hate to throw an urgent on this, however we already have a call in to PSS and our production system is down. Some general info: It is hp rx8620 64bit server with 8 proc and 32GB memory. It has Windows 2003 DataCenter SP1 as OS. It has SQL Server 2000 and AS 2000 (SP4) as default instance and SQL Server 2005 and AS 2005 as named instance. The OLAP Repository is running on the SQL Server 2000 instance. It was working fine up until yesterday. At this point the server is functional in general. SQL databases are accessible and functional. Cubes can be queried using Proclarity/Excel/Open Rowset. The only thing we can not do is process cubes. We can not connect through Analysis Manager and the VBS/DSO we've written to process the cubes does not work at all, it can't even connect. Attempts made to connect through another box do not work. To make sure it wasn't data file corruption or something to do with the OLAP Repository db, we brought both those back up on another server and they worked fine. Cubes can be accessed through Analysis Manager without having to manually enter the repository connection string each time. The only way we can process is if we go through Analysis Manager in a funky way. We have right click on edit repository connection string and put the value in. However, once Analysis Manager is closed down and reopened we have to go through the same process. DTS Analysis Servers object can not see AS at all. We're at a loss. I think the registry is hosed (but we've tried reininstalling). What doesn't make sense why users can still query the cube. Does PTS connect to the repository or just look at the datafiles? Any ideas guys? |
#3
| |||
| |||
|
|
What service pack are you running? Have you updated or moved the repository recently? I think you are on the right track, my guess would be that there is an issue with your registry, either a security/permissions issue or a corruption of some sort. If you are running SP4 and have recently changed the repository location , the following KB article may be of interest. http://support.microsoft.com/?kbid=903030 On a 32bit machine I would suggest running regmon from sysinternals.com on the server while you are running Analysis Manager, but I don't know if it will work on a 64 bit machine, it might work on an x64, there probably a slightly lower chance of this working if you are running IA64. Does PTS connect to the repository or just look at the datafiles? No, PTS does not access the repository at all. Only DSO needs access to the repository. -- Regards Darren Gosbell [MCSD] Blog: http://www.geekswithblogs.net/darrengosbell In article <Om7K0gniGHA.5036 (AT) TK2MSFTNGP04 (DOT) phx.gbl>, jesperzz (AT) hotmail (DOT) com says... I hate to throw an urgent on this, however we already have a call in to PSS and our production system is down. Some general info: It is hp rx8620 64bit server with 8 proc and 32GB memory. It has Windows 2003 DataCenter SP1 as OS. It has SQL Server 2000 and AS 2000 (SP4) as default instance and SQL Server 2005 and AS 2005 as named instance. The OLAP Repository is running on the SQL Server 2000 instance. It was working fine up until yesterday. At this point the server is functional in general. SQL databases are accessible and functional. Cubes can be queried using Proclarity/Excel/Open Rowset. The only thing we can not do is process cubes. We can not connect through Analysis Manager and the VBS/DSO we've written to process the cubes does not work at all, it can't even connect. Attempts made to connect through another box do not work. To make sure it wasn't data file corruption or something to do with the OLAP Repository db, we brought both those back up on another server and they worked fine. Cubes can be accessed through Analysis Manager without having to manually enter the repository connection string each time. The only way we can process is if we go through Analysis Manager in a funky way. We have right click on edit repository connection string and put the value in. However, once Analysis Manager is closed down and reopened we have to go through the same process. DTS Analysis Servers object can not see AS at all. We're at a loss. I think the registry is hosed (but we've tried reininstalling). What doesn't make sense why users can still query the cube. Does PTS connect to the repository or just look at the datafiles? Any ideas guys? |
![]() |
| Thread Tools | |
| Display Modes | |
| |