Errors While deploying SSAS 2005 Cube on Server - sql-server

I am stuck with something really nasty here. I have a SSAS Cube that was working fine till day before yesterday. Had some performance issues on the server and got cummulative patch 938077 on top of Service Pack2.
Since then I have not been able to deploy the cube - with a strange error -
File System Error: The following error occurred during a file operation: Access is denied.
I am administrator on the machine, have possibly checked the whole of file system for permissions. Have deleted the existing cube, stopped services, server, tried redeployment - nothing works.
Unfortunately I forgot to take a snapshot of pre-patch image, so cann't restore back. Only option I am currently left with is to rebuild the server, if I cann't fix this.
Strange but I cann't find anything on any forums about this.
Yes, one more strange thing related to this - I had SSIS package, to load DW (datasource for above cube), and strangely I have lost all my Data flow tasks. Something wierd is really going on and I cann't trace it.
Any suggestions or help would be great. I just cann't think of anything right now.
Cheers!!
Vineet

Figured it out, its more of a permission issue on the server than with the cube itself. Ran the SQL services under Local System account (after new security patches applied without us knowing it) and it worked fine.

Related

Why does my SSIS project not deploy from SSDT 2017?

recently, when I try to deploy my SSIS project from SSDT 2017 I get the following error:
Failed to deploy project. For more information, query the operation_messages view for the operation identifier '2'. (Microsoft SQL Server, Error: 27203)
Moreover, SSIS does not write any message to "operation_messages" - the table is empty. All I get is a non-descriptive entry in the "operations" view.
I have recently recreated the SSIS DB in order to fix the error (did not work), hence the low count in the "operation_messages" view. We have also restarted the database server.
Has anyone had a similar problem and can point me in the right direction.
Cheers!
Edit: I can run the project from SSDT with no problems.
Edit 2:
If I copy the package to my local machine, it deploys without any
issues. On the server, I get the deployment error, even if I try to deploy a newly created empty package.
We have resolved the problem. The final clue came from the Windwos event log, where we found out that SSDT was trying to deploy to a wrong database ("Database..." instead of "DB..."). The wrong information seems to have been retrieved from the sys.servers table. We updated the wrong information by using
EXEC sp_dropserver 'Database...';
GO
EXEC sp_addserver 'DB...', local;
GO
Now I can deploy the project again. I have no idea how the incorrect information ended up in sys.servers, but this has done the trick. Thanks to everyone who tried to help out!

SSIS deployment yields Error 27123

An attempted deployment from (localhost) to (remote server) yielded the Error 27123 which, appears to be a credentials-related issue. After spending several hours the resolution appears to be one of assigning local-to-the-remote server Windows credentials that are used to launch DTEexec.exe. I am using VS2012 Ultimate locally with SQL Server 2014 Developer version and remote SQL version 2012 SP1. However, my attempts have failed so far.
I would VERY much like to be able to deploy to the remote server inside of VS2012, including creating folders, etc but am still at a loss as to the missing piece needed.
We do not have Active Directory set up as the remote is on the Amazon S3 cloud bit other than that is pretty much a plain vanilla setup. I also noted some folks suggested a Kerberos-based response but before I ask our network guru to proceed I'd like at least to get confirmation.
I AM able to manually FTP, install and run packages when remoted in but that stinks for my contractor who I would also like to be able to have me out of his way. s
All found online materials have not yet yielded the one last piece. I suspect my ignorance rather than the lack of a real solution and would appreciate any guidance.
Thanks in advance.

Why aren't my charts in SSRS 2012 displaying?

I recently moved several reports over to a new server. Everything works fine displaying tables and data, but charts are not displaying properly. It looks like the image is not rendering properly. My initial thought was that this was a permissions issue, specifically that the service account used to run SSRS needed permissions to a certain folder on the server that is used to generated chart images, but I can not find anything about this in searching for a solution.
This happens with old reports that display fine on the original server and new reports I try making on the new server.
EDIT: SSRS logs are showing a generic error in GDI+. Looks like this may be the issue, especially since this is running on a virtual server:
http://social.technet.microsoft.com/Forums/en-US/37ed20b2-99bc-4e36-a14b-c9f8cc297be3/ssrs-2012-reports-with-charts-generic-error-in-gdi-?forum=sqlreportingservices
I am curious about a point made in this question:
2) Ensure write permissions on the "folder to which SSRS caches the charts"
Well, firstly, I have not found a single article on the net as to
where this folder is; however, I tested this locally on the server
while logged in as Administrator with full privileges. This doesn't
seem to apply to my situation either.
Does anyone know about this folder? I would imagine that running while logged in as an admin would not mean anything since the service account running SSRS would need the correct privileges.
Someone had a similar problem and the solution was to repair the SQL Server installation. I know it is quite long to run but it might be worth a try.
Equivalent topic in SO
You can try restarting the report server. That worked in my case with Sharepoint and SQL Server 2012. Or repair the SQL server installation on the server as some posts suggest.
SSRS 2012 Charts Not Rendering
I had the same issue when deploying a new report locally.
I restarted my Report Server service and the reports rendered fine.

Deployment error with SSIS 2012 while deploying project to catalogue DB

I encountered a rather strange error earlier while deploying an SSIS project to our SSIS Catalogue DB:
"The project or operation records do not exist or you have not been
granted the appropriate permissions to view them."
Now, I'm an administrator on the server and have never had any trouble deploying to it before. I tried again just afterwards, and it worked fine. I checked to make sure that there were no other packages running at the same time.
I did find this recent post on MSDN, which has the same error but no explanation as of yet.
Anybody know what the cause of this error could be?
try open solution "Run as Administrator" it can help.
Perhaps your project did not exist at the time of the deployment but was created so the next time you deployed you did not get the error because it actually passed that validation. Double Check the deployment information, the name and path of the deployment destination and confirm that those existed.

SqlServer is in script upgrade mode

Vista just finished one of its many updates. After restarting my computer I try connecting to SqlServer2008 instance with Sql Server Management Studio and I get this error:
Error connecting to '...\MSSQLSERVER2008'.
Additional information:
Login failed for user '...'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. (Microsoft SQL Server, Error: 18401).
Pressing help gets me to an internet page saying there's no additional information.
Thx Vista & Updates. Anyone an idea because on the internet I can't find anything about this issue.
It appears This Guy was having the same problems as you and his only suggestion was to wait a few minutes before trying to log in again.
I have yet to see any type of Microsoft documentation about this, nor have I seen any forum posts which came to any sort of resolution concerning the same problem.
Check your event viewer. I had the same problem and found that (in my case) it was looking for a directory that didn't exist to perform an upgrade script. NO hint that there was any sort of problem in the dialog, but the event viewer showed clearly what the problem was.
jim
I had the same problem. Waiting until update was done did not help. Solution was, (after checking Windows eventlog) to set the folder rights. SQL-Express had no rights on the database folder, why ever. Something has mixed up the rights during the upgrade from WinXP to Win 7. That was it.
Adding a comment to this page since this is the top Google result for "script upgrade mode". It seems that a number of things can cause a SQL Server DB to go into this mode. In our shop we've run into these two cases in the past months:
Log shipping - Can't recall at what point of the process exactly the DB went into this mode, iirc it was when bringing it back up. The solution was just to wait it out.
Hard drive full - The DB went into this mode when it ran out of space. We're currently clearing up the drive, will come back with an update if waking it up turns out to be challenging.
Update: After freeing up disk space, it was a simple matter of setting the DB "Offline" and then "Online" to bring it back up.
We had the same issue, but needed to know what was going on in the background.
The db's were put into recovery mode, hence they had to recover. To assist we went to the SQL Server error log located where the system files (normally master, model, msdb...) are located, but under the log folder. In the ERRORLOG, we did a find on the word recovery and could watch the db's percentage recovered. Everything recovered normally, but it was much longer than expected.
The Reason for this is that the system reboot happens with important\necesssary softwares loaded and does all other operation later so that the booting happens faster.
Here in your case, the sql booting is happening as the start of SQL is not needed for system to start. I hope you are aware of DAC account(Dedicated Administrator Connection, Link) who has seperate connectivity and has ability to resolve issues even the whole SQL server is not responing. The SQL server is asking you either to wait or open the SQL with DAC account and stop the SQL update.
Solutions:
1) Wait until backround update completes
2) Open SQL using DAC account and kill all running processes

Resources