Showing posts with label service. Show all posts
Showing posts with label service. Show all posts

Monday, March 19, 2012

another simple question, please help, thx a lot!

I have some issues for remotely connection a sqlexpress server 2005 with a c# desktop app,

in my local network, after I set a port forwarding service for the computer which runs sqlexpress server, I want my c# app connect to the sqlexpress server in another machine under same local network, the connection string is:

"server= 62.31.81.210.\SQLEXPRESS,1921; Database='EvoHealthSQLex'; Integrated Security=True"

however, that one only work in the sqlexpress server machine, if I try to use it in another machine, i got error 'Login failed for user 'BRISTOL-1\Guest', BRISTOL-1 is the full computer name of sqlexpress server machine, I found out the solution is to create a login for 'BRISTOL-1\Guest' (in sever management studio express):

CREATE LOGIN [BRISTOL-1\Guest] FROM WINDOWS; GO

then it fixed the problem I mentioned above, However, what I want to ask is when I change the server authentication from 'windows authentication mode' to 'Sql server and windows authtication mode', then i try to create a user like this:

CREATE LOGIN Ross WITH PASSWORD = 'changeme'; USE EvoHealthSQLex; CREATE USER Ross; GO 
Then I change my connection string to:
"server= 62.31.81.210.\SQLEXPRESS,1921; user id='Ross'; password='changeme'; Database='EvoHealthSQLex';
then I got the following error even when I user 'sa' user:
An unhandled exception of type 'System.Configuration.ConfigurationException' occurred in system.dll
 
I wonder why this happening ? it should be a stupid connectionstring problem just I don't know ..
I wonder can I use 'windows authentication' for remote access (outside local network)? if so, how do i specified the username, all BRISTOL-1\Guest ?
 
thanks a lot for your reading!
Can you post the extire exception stack trace?|||

sorry, it was a syntax program, I was being silly again...

it should be:

"server= 62.31.81.210.\SQLEXPRESS,1921; user id='Ross'; password='changeme'; Database='EvoHealthSQLex' "

I put a extra ';' in the end of the statement :

"server= 62.31.81.210.\SQLEXPRESS,1921; user id='Ross'; password='changeme'; Database='EvoHealthSQLex' ; "

now above error message disappear!

thanks very much for your help, learn a lot for this forum, as a newbie :)

|||

Hi, got a last question of this remote connection problem:

I send my program to my friend and ask him run it (as all my computer is within the same local network, although I use the router Ip address 62.31.81.210 instead of local ip address 168.192.0.3) and he got a error say' SQL server is not exist or access denied', I wonder whatelse can cause that happen ? anything to do with the port forwarding service? he does can browse my test website hosting in the same machine using the same ip address http://62.31.81.210(I also do a port forwarding service with port 80 as well), I wonder why he failed to connect to sqlexpress server...

Many thanks!

|||

You can find lots of troubleshooting info through

http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx

In your case, the errormsg indicates that the client do not have connecitivity to the server. "168.192.0.3" mean host local address, which normally mean the host does not haveconnecitvity to the network. I am surprised that with 168.192.0.3, you can browse the server.

One you made sure you have network connectivity, you can try to "telnet 62.31,81,210 port" to see if TCP connectivity is ok between your client host and remote server. "use ctrl +]" and "quit" to exit the telnet console.

Once you have telnet test passes, you may try your sql connection.

|||

hi, thanks for your reply again, I just ask my another friend to try it and it works! I didn't use the local Ip address '168.192.0.3', I use the '62.31,81,219 1921', and I connect it with tcp/ip with no problem, so probably is my first friend's computer problem.

so far so good, thanks so much for your help, really appreciated !

Saturday, February 25, 2012

Annoying feature - report service rewrite query automatically.

This feature is very annoying, report service 2k rewrites my query, even the
format of query is changed too. How to disable this feature?
Thanks really a lot.Use the generic query designer (two pane) instead of the graphical query
designer. The button to switch to it is one of the buttons to the right of
the ...
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"qye2020" <qye2020@.yahoo.com> wrote in message
news:uz0EglpJGHA.2088@.TK2MSFTNGP11.phx.gbl...
> This feature is very annoying, report service 2k rewrites my query, even
> the format of query is changed too. How to disable this feature?
> Thanks really a lot.
>|||Wonderful, problem is gone with your kind answer.
Thanks a lot.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:ewOcV9pJGHA.3176@.TK2MSFTNGP12.phx.gbl...
> Use the generic query designer (two pane) instead of the graphical query
> designer. The button to switch to it is one of the buttons to the right of
> the ...
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "qye2020" <qye2020@.yahoo.com> wrote in message
> news:uz0EglpJGHA.2088@.TK2MSFTNGP11.phx.gbl...
>> This feature is very annoying, report service 2k rewrites my query, even
>> the format of query is changed too. How to disable this feature?
>> Thanks really a lot.
>

Announcing a GUI tool for configuring dialog security and routing

Hi,

I am not

able to get “Service Broker” under my database? Can you tell me what is wrong

with my installation?

Regards,

If you are using SQL Server Management Studio Express, it does not have the functionality to view or create Service Broker objects. The paid version of the same lets you view Service Broker objects but not create them. Unfortunately, the only way to create, alter and use Service Broker objects is via T-SQL commands. Please look at the Service Broker section of Books Online, the SQL Server online documentation on MSDN.

Sunday, February 19, 2012

ANALYZING SQL SERVICE HANGUP

The SQL Service hangs up at peak time once a day. What is the best way to
analyze the problem
Hi
Run sp_who2 from Query Analyser to see if blocking occurs.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Riaz Khan" wrote:

> The SQL Service hangs up at peak time once a day. What is the best way to
> analyze the problem
>
|||Posting twice the same question in 70 minutes does not guarantee a quicker
answer.
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Riaz Khan" wrote:

> The SQL Service hangs up at peak time once a day. What is the best way to
> analyze the problem
>

ANALYZING SQL SERVICE HANGUP

The SQL Service hangs up at peak time once a day. What is the best way to
analyze the problemHi
Run sp_who2 from Query Analyser to see if blocking occurs.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Riaz Khan" wrote:
> The SQL Service hangs up at peak time once a day. What is the best way to
> analyze the problem
>|||Posting twice the same question in 70 minutes does not guarantee a quicker
answer.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Riaz Khan" wrote:
> The SQL Service hangs up at peak time once a day. What is the best way to
> analyze the problem
>

ANALYZING SQL SERVICE HANGUP

The SQL Service hangs up at peak time once a day. What is the best way to
analyze the problemHi
Run sp_who2 from Query Analyser to see if blocking occurs.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Riaz Khan" wrote:

> The SQL Service hangs up at peak time once a day. What is the best way to
> analyze the problem
>|||Posting twice the same question in 70 minutes does not guarantee a quicker
answer.
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Riaz Khan" wrote:

> The SQL Service hangs up at peak time once a day. What is the best way to
> analyze the problem
>

Thursday, February 16, 2012

Analysis Services SP4 problems

Hello I hope someone can help me.

On a SQL server that has had SP4 recently installed on it for both the SQL Server service and OLAP service, I am unable to browse the data of any of the Shared Dimensions or Cubes of any of the databases when I use the Analysis Manager MMC. At the time I am logged onto the server as an administrator using terminal services. Upon attempting to browse a shared dimension the following error is returned "Unable to browse the dimension <dimension name>, Type mismatch" and when attempting to browse a cube the error is "Unable to browse the cube <cube name>. An unexpected internal error has occured. Please restart the application."

The Cubes can be browsed via Excel though and all Reporting Service mdx queries are functioning correctly.

If I register the same server in Analysis Manager MMC on a different server also with SP4 all Cubes and Dimensions data can be browsed.

I tried archiving the database cubes and restoring them on a server with SP3 and all data can be browsed via the servers own Analysis Manager MMC.

Any ideas?

This can be related to an MDAC version issue if this post is correct: http://www.dbforums.com/archive/index.php/t-357508.html

Regards

Thomas Ivarsson

|||

I suspect you are right. Thank you for the help Thomas.

On the servers that have "MDAC 2.8 on Windows XP SP2" seem to have the same problem. Servers that are using "MDAC 2.8 RTM" are all functioning correctly, (as determined by "Component Checker").

Do you happen to know the link of a webpage that gives a walkthrough on how to perform a MDAC Rollback?

I have not found any information on how to do this correctly.

|||

Sorry, I have no link, except that I think there is a newsgroup for this(http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=87&SiteID=1).

Kind Regards

Thomas Ivarsson

|||

I have encountered the same situation aftr installing SP4. Please let me know how to fix this apparently MDAC related problem

Thanks

Attila

|||

I am currently administrating the production Analysis Server with Analysis Manager MMC via a remote connection that also uses "MDAC 2.8 on Windows XP SP2". This permits browsing of dimension and cube data as well as virtual cube editing. (An annoying work around).

I have discovered that "MDAC 2.8 RTM" seems to function correctly but I have not yet found the correct procedure for performing a MDAC rollback, which is quite probably quite complicated considering all the dll's and registry settings involved. All I can suggest is to browse the relevant forum as per Thomas's rely above.

Best of luck.

Analysis Services SP4 problems

Hello I hope someone can help me.

On a SQL server that has had SP4 recently installed on it for both the SQL Server service and OLAP service, I am unable to browse the data of any of the Shared Dimensions or Cubes of any of the databases when I use the Analysis Manager MMC. At the time I am logged onto the server as an administrator using terminal services. Upon attempting to browse a shared dimension the following error is returned "Unable to browse the dimension <dimension name>, Type mismatch" and when attempting to browse a cube the error is "Unable to browse the cube <cube name>. An unexpected internal error has occured. Please restart the application."

The Cubes can be browsed via Excel though and all Reporting Service mdx queries are functioning correctly.

If I register the same server in Analysis Manager MMC on a different server also with SP4 all Cubes and Dimensions data can be browsed.

I tried archiving the database cubes and restoring them on a server with SP3 and all data can be browsed via the servers own Analysis Manager MMC.

Any ideas?

This can be related to an MDAC version issue if this post is correct: http://www.dbforums.com/archive/index.php/t-357508.html

Regards

Thomas Ivarsson

|||

I suspect you are right. Thank you for the help Thomas.

On the servers that have "MDAC 2.8 on Windows XP SP2" seem to have the same problem. Servers that are using "MDAC 2.8 RTM" are all functioning correctly, (as determined by "Component Checker").

Do you happen to know the link of a webpage that gives a walkthrough on how to perform a MDAC Rollback?

I have not found any information on how to do this correctly.

|||

Sorry, I have no link, except that I think there is a newsgroup for this(http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=87&SiteID=1).

Kind Regards

Thomas Ivarsson

|||

I have encountered the same situation aftr installing SP4. Please let me know how to fix this apparently MDAC related problem

Thanks

Attila

|||

I am currently administrating the production Analysis Server with Analysis Manager MMC via a remote connection that also uses "MDAC 2.8 on Windows XP SP2". This permits browsing of dimension and cube data as well as virtual cube editing. (An annoying work around).

I have discovered that "MDAC 2.8 RTM" seems to function correctly but I have not yet found the correct procedure for performing a MDAC rollback, which is quite probably quite complicated considering all the dll's and registry settings involved. All I can suggest is to browse the relevant forum as per Thomas's rely above.

Best of luck.

Analysis Services SP4 problems

Hello I hope someone can help me.

On a SQL server that has had SP4 recently installed on it for both the SQL Server service and OLAP service, I am unable to browse the data of any of the Shared Dimensions or Cubes of any of the databases when I use the Analysis Manager MMC. At the time I am logged onto the server as an administrator using terminal services. Upon attempting to browse a shared dimension the following error is returned "Unable to browse the dimension <dimension name>, Type mismatch" and when attempting to browse a cube the error is "Unable to browse the cube <cube name>. An unexpected internal error has occured. Please restart the application."

The Cubes can be browsed via Excel though and all Reporting Service mdx queries are functioning correctly.

If I register the same server in Analysis Manager MMC on a different server also with SP4 all Cubes and Dimensions data can be browsed.

I tried archiving the database cubes and restoring them on a server with SP3 and all data can be browsed via the servers own Analysis Manager MMC.

Any ideas?

This can be related to an MDAC version issue if this post is correct: http://www.dbforums.com/archive/index.php/t-357508.html

Regards

Thomas Ivarsson

|||

I suspect you are right. Thank you for the help Thomas.

On the servers that have "MDAC 2.8 on Windows XP SP2" seem to have the same problem. Servers that are using "MDAC 2.8 RTM" are all functioning correctly, (as determined by "Component Checker").

Do you happen to know the link of a webpage that gives a walkthrough on how to perform a MDAC Rollback?

I have not found any information on how to do this correctly.

|||

Sorry, I have no link, except that I think there is a newsgroup for this(http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=87&SiteID=1).

Kind Regards

Thomas Ivarsson

|||

I have encountered the same situation aftr installing SP4. Please let me know how to fix this apparently MDAC related problem

Thanks

Attila

|||

I am currently administrating the production Analysis Server with Analysis Manager MMC via a remote connection that also uses "MDAC 2.8 on Windows XP SP2". This permits browsing of dimension and cube data as well as virtual cube editing. (An annoying work around).

I have discovered that "MDAC 2.8 RTM" seems to function correctly but I have not yet found the correct procedure for performing a MDAC rollback, which is quite probably quite complicated considering all the dll's and registry settings involved. All I can suggest is to browse the relevant forum as per Thomas's rely above.

Best of luck.

Analysis Services service won't start

Can anyone point me in the right direction?

I haven't used SSAS in a few months and I went to start the service in SQL Server Configuration Manager and I get an error pop-up message:

The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details.

However the event log has no useful info - just says the service started, then it stopped - no error related info. There are no logs generated in ..\MSSQL.1\. Every other service starts - database, SSIS, SSRS, Agent, Browser and FullText.

I'm running Sql Server 2005 (with SP1) on Win XP Pro (SP2). Any help appreciated!

Do you see anything in the System Event log?

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

There were a few Information type events that said that Analysis Services started and it stopped, but no error or warning events.

I got impatient and uninstalled SSAS and re-installed and everything works now.

Analysis Services service hangs cube build / timeout on process cu

We have two apparent issues with Analysis Services (AS) as outlined below:
1.We have a rebuild of the nightly cube build and quite often the first
step would hang (just run without processing). We would have to stop the
job, restart Analysis Services and then start the job again, resulting in
loss of processing time and an impact to our Production Reporting. As a
workaround for this intermittent problem, we have adjusted the nightly job to
include a stop and start of AS before the cube build begins. An outline of
the current steps:
?net stop MSSQLServerOLAPService
?net start MSSQLServerOLAPService
?dtexec /DTS "\MSDB\SSAS_Petra_Full_Dim_Load_Prod" /SERVER vbmsp19
/MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V
?process cub files
?backup cube
We need to know why AS does not process cubes as it should from time to
time. Do we have a configuration problem? Is our Production Server not
sufficient enough for AS and the size of the cube? We have more than the
minimum requirements but possibly we need more due to our expectation of the
cubes and data.
Server Specifications -->
Production
CPU = Quad 2.8 GHz Intel Xeon (Hyper-Threaded)
Memory = 20476 MB
OS – Windows 2003. SP1
SQL Server 2005
64 bit based on the x64 platform
2.We have been unable to deploy a copy of the Production cubes to a new
server. We even tried deploying a smaller cube, to include a large
dimension (ex: Account). We continually experience time outs with the larger
dimensions.
a.Tried deploying from Visual Studio 2005
b.Attempted to Process the cube through SQL Server Management Studio
c.Attempted to Process the larger dimension only from SQL Server Management
Studio
d.Attempted Parallel processing, Sequential – One Transaction, and
Sequential – Separate Transaction.
e.Also tried changing the default timeout for the AS server.
ForceCommitTimeout property was 30000, increased to 40000 and then again to
50000
f.Attempted to change the ExternalCommandTimeout property from 3600 to
7200. This was successful in the Deisaster Recovery server which has nothing
running (no users reporting). Although it did take over 5 hours to process.
At that rate, it might take 2 days to rebuild the large cube that we have,
with several partitions.
Disaster Recovery -->
CPU = Dual 3.00 GHz Intel Xeon MP (Hyper-Threaded)
Memory = 9728 MB
OS – Windows 2003 SP 1
SQL Server 2005
32bit
Errors:
OLE DB error: OLE DB or ODBC error: Operation canceled; HY008.
OLE DB error: OLE DB or ODBC error: Query timeout expired; HYT00.
do you have any proactive caching partitions?
I see this error when I'm using the proactive caching feature.
"Shari" <Shari@.discussions.microsoft.com> wrote in message
news:4D39C9AF-58CF-4639-BA8B-DF4E936D62F1@.microsoft.com...
> We have two apparent issues with Analysis Services (AS) as outlined below:
> 1. We have a rebuild of the nightly cube build and quite often the first
> step would hang (just run without processing). We would have to stop the
> job, restart Analysis Services and then start the job again, resulting in
> loss of processing time and an impact to our Production Reporting. As a
> workaround for this intermittent problem, we have adjusted the nightly job
> to
> include a stop and start of AS before the cube build begins. An outline
> of
> the current steps:
> ? net stop MSSQLServerOLAPService
> ? net start MSSQLServerOLAPService
> ? dtexec /DTS "\MSDB\SSAS_Petra_Full_Dim_Load_Prod" /SERVER vbmsp19
> /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V
> ? process cub files
> ? backup cube
> We need to know why AS does not process cubes as it should from time to
> time. Do we have a configuration problem? Is our Production Server not
> sufficient enough for AS and the size of the cube? We have more than the
> minimum requirements but possibly we need more due to our expectation of
> the
> cubes and data.
> Server Specifications -->
> Production
> CPU = Quad 2.8 GHz Intel Xeon (Hyper-Threaded)
> Memory = 20476 MB
> OS – Windows 2003. SP1
> SQL Server 2005
> 64 bit based on the x64 platform
>
> 2. We have been unable to deploy a copy of the Production cubes to a new
> server. We even tried deploying a smaller cube, to include a large
> dimension (ex: Account). We continually experience time outs with the
> larger
> dimensions.
> a. Tried deploying from Visual Studio 2005
> b. Attempted to Process the cube through SQL Server Management Studio
> c. Attempted to Process the larger dimension only from SQL Server
> Management
> Studio
> d. Attempted Parallel processing, Sequential – One Transaction, and
> Sequential – Separate Transaction.
> e. Also tried changing the default timeout for the AS server.
> ForceCommitTimeout property was 30000, increased to 40000 and then again
> to
> 50000
> f. Attempted to change the ExternalCommandTimeout property from 3600 to
> 7200. This was successful in the Deisaster Recovery server which has
> nothing
> running (no users reporting). Although it did take over 5 hours to
> process.
> At that rate, it might take 2 days to rebuild the large cube that we
> have,
> with several partitions.
>
> Disaster Recovery -->
> CPU = Dual 3.00 GHz Intel Xeon MP (Hyper-Threaded)
> Memory = 9728 MB
> OS – Windows 2003 SP 1
> SQL Server 2005
> 32bit
> Errors:
> OLE DB error: OLE DB or ODBC error: Operation canceled; HY008.
> OLE DB error: OLE DB or ODBC error: Query timeout expired; HYT00.
>
|||Thanks Jeje for your quick response.
I browsed the setting of the partitions and proactive caching is not
enabled. Any other ideas?
Thanks,
Shari
"Jeje" wrote:
[vbcol=seagreen]
> do you have any proactive caching partitions?
> I see this error when I'm using the proactive caching feature.
>
> "Shari" <Shari@.discussions.microsoft.com> wrote in message
> news:4D39C9AF-58CF-4639-BA8B-DF4E936D62F1@.microsoft.com...

Analysis Services service hangs cube build / timeout on process cu

We have two apparent issues with Analysis Services (AS) as outlined below:
1. We have a rebuild of the nightly cube build and quite often the first
step would hang (just run without processing). We would have to stop the
job, restart Analysis Services and then start the job again, resulting in
loss of processing time and an impact to our Production Reporting. As a
workaround for this intermittent problem, we have adjusted the nightly job t
o
include a stop and start of AS before the cube build begins. An outline of
the current steps:
? net stop MSSQLServerOLAPService
? net start MSSQLServerOLAPService
? dtexec /DTS "\MSDB\SSAS_Petra_Full_Dim_Load_Prod" /SERVER vbmsp19
/MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V
? process cub files
? backup cube
We need to know why AS does not process cubes as it should from time to
time. Do we have a configuration problem? Is our Production Server not
sufficient enough for AS and the size of the cube? We have more than the
minimum requirements but possibly we need more due to our expectation of the
cubes and data.
Server Specifications -->
Production
CPU = Quad 2.8 GHz Intel Xeon (Hyper-Threaded)
Memory = 20476 MB
OS – Windows 2003. SP1
SQL Server 2005
64 bit based on the x64 platform
2. We have been unable to deploy a copy of the Production cubes to a new
server. We even tried deploying a smaller cube, to include a large
dimension (ex: Account). We continually experience time outs with the larger
dimensions.
a. Tried deploying from Visual Studio 2005
b. Attempted to Process the cube through SQL Server Management Studio
c. Attempted to Process the larger dimension only from SQL Server Management
Studio
d. Attempted Parallel processing, Sequential – One Transaction, and
Sequential – Separate Transaction.
e. Also tried changing the default timeout for the AS server.
ForceCommitTimeout property was 30000, increased to 40000 and then again to
50000
f. Attempted to change the ExternalCommandTimeout property from 3600 to
7200. This was successful in the Deisaster Recovery server which has nothin
g
running (no users reporting). Although it did take over 5 hours to process.
At that rate, it might take 2 days to rebuild the large cube that we have,
with several partitions.
Disaster Recovery -->
CPU = Dual 3.00 GHz Intel Xeon MP (Hyper-Threaded)
Memory = 9728 MB
OS – Windows 2003 SP 1
SQL Server 2005
32bit
Errors:
OLE DB error: OLE DB or ODBC error: Operation canceled; HY008.
OLE DB error: OLE DB or ODBC error: Query timeout expired; HYT00.do you have any proactive caching partitions?
I see this error when I'm using the proactive caching feature.
"Shari" <Shari@.discussions.microsoft.com> wrote in message
news:4D39C9AF-58CF-4639-BA8B-DF4E936D62F1@.microsoft.com...
> We have two apparent issues with Analysis Services (AS) as outlined below:
> 1. We have a rebuild of the nightly cube build and quite often the first
> step would hang (just run without processing). We would have to stop the
> job, restart Analysis Services and then start the job again, resulting in
> loss of processing time and an impact to our Production Reporting. As a
> workaround for this intermittent problem, we have adjusted the nightly job
> to
> include a stop and start of AS before the cube build begins. An outline
> of
> the current steps:
> ? net stop MSSQLServerOLAPService
> ? net start MSSQLServerOLAPService
> ? dtexec /DTS "\MSDB\SSAS_Petra_Full_Dim_Load_Prod" /SERVER vbmsp19
> /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V
> ? process cub files
> ? backup cube
> We need to know why AS does not process cubes as it should from time to
> time. Do we have a configuration problem? Is our Production Server not
> sufficient enough for AS and the size of the cube? We have more than the
> minimum requirements but possibly we need more due to our expectation of
> the
> cubes and data.
> Server Specifications -->
> Production
> CPU = Quad 2.8 GHz Intel Xeon (Hyper-Threaded)
> Memory = 20476 MB
> OS – Windows 2003. SP1
> SQL Server 2005
> 64 bit based on the x64 platform
>
> 2. We have been unable to deploy a copy of the Production cubes to a new
> server. We even tried deploying a smaller cube, to include a large
> dimension (ex: Account). We continually experience time outs with the
> larger
> dimensions.
> a. Tried deploying from Visual Studio 2005
> b. Attempted to Process the cube through SQL Server Management Studio
> c. Attempted to Process the larger dimension only from SQL Server
> Management
> Studio
> d. Attempted Parallel processing, Sequential – One Transaction, and
> Sequential – Separate Transaction.
> e. Also tried changing the default timeout for the AS server.
> ForceCommitTimeout property was 30000, increased to 40000 and then again
> to
> 50000
> f. Attempted to change the ExternalCommandTimeout property from 3600 to
> 7200. This was successful in the Deisaster Recovery server which has
> nothing
> running (no users reporting). Although it did take over 5 hours to
> process.
> At that rate, it might take 2 days to rebuild the large cube that we
> have,
> with several partitions.
>
> Disaster Recovery -->
> CPU = Dual 3.00 GHz Intel Xeon MP (Hyper-Threaded)
> Memory = 9728 MB
> OS – Windows 2003 SP 1
> SQL Server 2005
> 32bit
> Errors:
> OLE DB error: OLE DB or ODBC error: Operation canceled; HY008.
> OLE DB error: OLE DB or ODBC error: Query timeout expired; HYT00.
>

analysis services service doesn't start

Hi,

well, you all know that story... "Suddenly, without changing anything, ...". Now it happened to me... Suddenly, without changing anything, my Analysis Services service doesn't start anymore. I the event log I see that it starts and it ends. When I try to start it from SQL Server Management studio it says that it started and stopped again. It's configured to use the local system account. I tried to run the service from a command line but it just quits without any message.

Any idea what I can do?

Thanks,

…fixed… There was a change… I started with Microsoft e-Learning trainings and got some XML problems with the viewer they use… They gave me some instructions to fix that (which didn’t help) but that seams to screw up my XML config… I ran a MSXML 6 repair install, that fixed the problem… I'm just wondering why there was not even one really helpful error message at all...

Monday, February 13, 2012

Analysis Services not Started!

Good Day!

I have installed SQL Server 2005

In services.msc SQL Server Analysis Services (MSSQLSERVER) can't be started.

Message: Service Started and then Stopped and

The service cannot be started: The following system error occurred: Only one usage of each socket address (protocol/network address/port) is normally permitted.

What is this?

Thanks...

Some application occupied AS TCP port. In case of default instance it would be 2383. Please run netstat or (even better) tcpmon to find out what this application is.|||

Wow.

It seems like SQL Analysis Services can't live with started SAP on the Machine.

What ports use Analysis Services?

|||

Default instance uses port 2383.

The redirector for named instances uses port 2382.

Ports for named instances can be manually overriden.

|||

Ok

Where can I change instance port for Analysis?

|||Server -> Properties -> Show All (advanced) properties -> Port|||

Mosha Pasumansky wrote:

Server -> Properties -> Show All (advanced) properties -> Port

Sorry for borring, I'm a novice.

Where is it? I'm going in Computer Managment -> SQL Server Configuration Manager -> SQL Server 2005 Services -> SQL Server Analysis Services ->Properties

But there nothing...

|||

You need to go to SQL Server Mgmt Studio> Connect to Analysis Services>Right Click on the server-> Hit Properties> Scroll down and check the box "Show Advanced(All) properties" and then you will see the property "Port"