I'm getting an error whenever I load Management Studio or open a folder in the server explorer, etc. Additionally, If I try to create a new database it constantly is updating and does not finish. I have attached a screenshot of the error. Please let me know what I can do to fix this because it's really aggravating.
Error Screen http://frickinsweet.com/databaseError.gif
From MSDN forum http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=120476&SiteID=1
My first guess would be Client Tool corruption.
I've occasionally had to uninstall my client tools and reinstall them. Boot after uninstall.
I had to add the registry file AND re-run "regsvr32 actxprxy.dll" This was a really odd and painful error. It only seemed to come into existence after installing VS SP1 but I really don't see why that would have happened.
Related
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!
SQL Server Setup has encountered the following error:
MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{DF167CE3-60E7-44EA-99EC-2507C51F37AE}'. Error code: 1605..
What I've done so far:
Had to re-install Windows 7 because I kept getting a pop up that said my windows was unregistered, which it wasn't (known bug) so I re-installed as per MS recommendation.
Un-installed SQL Server 2008 + ran Microsoft Fix It tool.
Tried to re-install.
After I got the error I deleted all the registry entries per instructions available where others have posted this same problem.
When I continued to get the error I renamed the registry directory UpgradeCodes to UpgradeCodes.old.
I've rebooted after every step and I've repeated this many times...
In all cases when I try to re-install it fails with Error code: 1605. At this point when I search the registry for the reversed key it is not found. It's gone.
Not sure what to do next.
Any suggestions would be appreciated. Thanks
I have the same problem and following method which I got it from http://www.thewindowsclub.com/ worked for me:
Method 2
This method is a little risky but should work at the first attempt. Make sure you don’t reboot the system until we complete the process. In this method we will just make the UpgradeCodes unusable until we finish the SQL install.
First setup is exit the install and shutdown all the applications
Then go toregistry and create a backup of the registry.
Now go to HKEY_Classes_Root\Installer\UpgradeCodes.
Right click on UpgradeCodes and click on Export and type in UC.reg and save it somewhere (Maybe Desktop)
Then right click again and click on rename and rename to UpgradeCodes.old
Now attempt to install SQL again. This time it should work in first try. Make sure you don’t reboot the system because sometime other application like MS Office might stop working. Once the installation is complete, close the installer and find the file you saved UC.reg and double click on it and click OK.
Now we have up the UpgradeCodes back again.
I am getting a very strange error message at one of our client sites and I am having very little luck trying to figure out what is going on.
Hr=80040154 ERR:OpenDB failed getting
pub version 28627
That is the error message that is from the Merge Agent (IIS) logs. From what I can tell, it is a COM error not being able to load a specific COM object, but I don't know which one. From that, I think this client might not have something installed, but I don't know what that something.
Does any one have any thoughts about what might not be installed? Any other ideas on how to troubleshoot this?
Thanks.
This error could be related to permissions: Did you configure a snapshot share and give the IUSER_Machine name rights to Read and List Files and Folders?
You could restart the synchronization with verbose history logging as described here: How to enable replication agents for logging to output files in SQL Server.
Check these:
Ensure your subscription database is not timing out on auto-grow.
Make sure there is enough space to apply the snapshot on the subscriber
It turns out that there was a DLL that wasn't registered. It was sqloledb.dll (C:\Program Files\Common Files\System\Ole DB). I found this by using the ?diag on the merge agent.
http:////sqlcesa35.dll?diag
That page shows a nice summary of the versions of DLLs that it is using and such. When I did that at the client's site, it showed "unknown" for the version of that DLL. Running regsvr32 on the DLL allowed sqlcesa35.dll to see it and the diag page showed a version number.
I am not able to remove sql server 2008 from my machine.
I installed it in the past as a part of the installation of an application, this installed the runtime of sql server 2008 SP0. But now I cannot uninstall.
I tried to use the setup of SP0 and even of SP2 but it was not able to uninstall, by giving fatal errors when it does the preliminary checks.
This means that the only option I have is format my machine?
I cannot even intall a new instance, something is really corrupted.
Is it a way to remove it manually?
I fixed a similar issue by using Microsoft fixit tool
http://support.microsoft.com/mats/Program_Install_and_Uninstall/
I tried to uninstall 3 times and the third time it was succesful, anyway I was not able to install due to fatal errors in the installer.
By trial and error I found that the problem was a list of non existing files in the following registry key (Windows Vista):
HKLM\SYSTEM\CurrentControlSet\Control\SessionManager\PendingFileRenameOperations
So i simply deleted The key PendingFileRenameOperations and tried to install, it installed succesfully.
Anyway thinkinf of automatizing this is crazy, the best way to reinstall is to isntall on a new machine (I mean for customers).
This is part of my job which I've been doing for a few years now. I've probably uninstalled it about 200 / 300 times and find it difficult sometimes.
What errors are you getting?
Have you manually deleted it from
C:\Program Files\Microsoft SQL Server
If you can, do so (or just rename) and then try to add-remove. You most likely won't be able to so the next course of action will be to manually strip it from the registry or use CC Cleaner to strip it out.
Let me know if that doesn't work and i'll offer another suggestion. I believe MS has a tool to force removing programs from the list if the MSI isn't available.
Good Luck it's not the nicest thing to do!
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.