I've got a problem with Expression Web 3. Just installed Expression Studio trial form official site plus few adds from there. Expression Web SP1 doesn't want to be install on my machine.
When I run Expression Web application it just resets my computer. Every other tools from Expression Studio working fine.
My system is Windows XP Home SP2.
Have a look here:
http://social.expression.microsoft.com/Forums/en-US/web/thread/94e0481b-01a6-4040-a8b3-3a98c24f8509
ServicePack3 helps.
Related
I'm trying to install SQL Server Express with Service Pack 1 on my Win8 Pro (x64) development machine and I'm consistently getting an error 0x84b10001 when trying to install it:
Antivirus is disabled during the installation (done as Administrator) and I tried 2 versions of the SQL Server Express package and I'm getting the same issue with both.
I'm getting the same issue whether I'm trying the x86 or x64 packages.
I suspect that the issue comes from the fact that Visual Studio 2013 has already installed some SQL Server packages but I do not see any way to update and modify these to add the Management Studio for istance.
Well, turns out that this cryptic error is due to an older instance of SQL Server Desktop Engine (MSDE) being present.
After uninstalling MSDE, the SQL Server 2012 setup worked without errors.
Create a new local user with administative rights and try the installation again. In my case it solves the problem with MSSQL 2008R2.
Create new user with administrative privileges and install using that user. It worked.
Remove folder:
C:\Users[USER ID]\AppData\Local\Microsoft_Corporation
It worked for me.
If you try to install SQL Server 2014 and get this error, use this web site:
http://anewdomain.net/2013/10/21/how-to-enable-net-framework-2-0-and-3-5-in-windows-8-1-for-older-programs/
You should install .NET Framework 2.0 and 3.5 first. You should check the framework versions on your PC. If you have only 4.5, you will continue to get the same error code.
Anyway, I fixed my trouble.
I hope it helps you too.
In my case, it was because trying to install an x86 package on an x64 windows, installing x64 package worked for me.
Disclaimer: Yes, I know Windows 8 is a pre-release and things won't necessarily work. I still need to do this.
I'm trying to install SQL Server Express 2008 R2 on Windows 8 32-bit (via Virtual Box). When I run the installer, I get an error:
Database installer returned error code -2147024893 (The system cannot find the path specified.)
The web installer didn't work either. WPI's log file tells me:
DownloadManager Information: 0 : Install exit code for product 'SQL Server Express 2008 R2' is -2068774911
I tried running this in compatibility mode for Windows 7. I can run the installer, click through the setup screen, and finally I get this error:
There was an error generating the XML document.
Error code: 0x84B10001.
How do I get this working, or, how do I debug/triage this? I looked through the logs, but I'm not too sure what they said; it might've been a registry-write error. Running in admin mode just causes the installer to not load, or a nice BSOD:
The answer, ironically, is quite simple -- I was installing 32-bit SQL Server on a 32-bit Windows 8. Instead, I moved to installing a 64-bit SQL Server on a 64-bit Windows 8.
Problem solved.
My company has a VB6 application using Crystal Reports 7 which a client has asked to be installed on Windows 7 32 bit. It is currently installed on Windows XP 32bit SP2 machines at the client. Connection to the DB is done via ODBC to SQL Server 2000 instance on another server.
On Windows 7, the installation works fine, however when you try to open the application, the error is given.
I have looked at the following:
Registering all the dll's and ocx files using regsvr32. Some will not register as they either are registered already or the following message is given "Make sure that "[name].dll" is valid DLL or OCX file and then try again." I read this forum thread regarding this: http://social.msdn.microsoft.com/forums/en-US/vblanguage/thread/0653f685-4526-45d9-89f3-8c479a6b4c62
Monitored the opening of the application using a ProcessMonitor application to try and spot if there is a missing dll or ocx file - this does not seem to be the case.
Reviewed the application according to this list and nothing seems to be against these guidelines
I've noticed two items in the knowledge base that relate to this
http://support.microsoft.com/kb/281848 - the comdlg32.ocx bundled with the application is version 6.0.81.69 and the one in the system32 folder on the dev machine (WinXP 32 bit) is 6.1.97.82. However if this was the issue then surely it would not work currently?
http://support.microsoft.com/kb/184898 - I'm not sure how to confirm that this is the issue
Finally, due to complexities, I am not allowed to make code changes to this application. Even if I was, I'm not a VB6 programmer, just the guy who got the terribly support project! If code changes are required, then I'll have to investigate using WinXP mode.
Update: I get the same error in XP Mode. That's a Win XP with SP3 VM. This runs on a Win XP SP2 VM, is there potentially something in SP3 that would have caused this to occur? Or is it just a fact of it being XP Mode?
I got the same error but I solved by using regsvr32.exe in C:\Windows\SysWOW64.
Because we use x64 system. So if your machine is also x64, the ocx/dll must registered also with regsvr32 x64 version
The file msrdo20.dll is missing from the installation.
According to the Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008 and Windows 7 this file should be distributed with the application.
I'm not sure why it isn't, but my solution is to place the file somewhere on the machine, and register it using regsvr32 in the command line, eg:
regsvr32 c:\windows\system32\msrdo20.dll
In an ideal world you would package this up with the redistributable.
This download fixed my VB6 EXE and Access 2016 (using ACEDAO.DLL) run-time error 429. Took me 2 long days to get it resolved because there are so many causes of 429.
http://www.microsoft.com/en-ca/download/details.aspx?id=13255
QUOTE from link:
"This download will install a set of components that can be used to facilitate transfer of data between 2010 Microsoft Office System files and non-Microsoft Office applications"
You say it works once you install the VB6 IDE so the problem is likely to be that the components you are trying to use depend on the VB6 runtime being installed.
The VB6 runtime isn't installed on Windows by default.
Installing the IDE is one way to get the runtime. For non-developer machines, a "redistributable" installer package from Microsoft should be used instead.
Here is one VB6 runtime installer from Microsoft. I'm not sure if it will be the right version for your components:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7b9ba261-7a9c-43e7-9117-f673077ffb3c
I was trying to install Microsoft SQL Server 2005 on my Windows 7 pc. When I tried to install it, it tells me that I have a newer version installed on my pc. So, I checked that Microsoft Sharepoint 2010 installed some sql server 2008 tools for me.
I decided to uninstall SharePoint 2010(which I wasn't using) and then tried to install MS SQL Server 2005 again. This threw me the following exception:
Error 1603 installing microsoft sql server setup support files
Searching on Google I found this article: http://support.microsoft.com/kb/916760 but it's not my case actually.
Any help will be appreciated. I really need this to continue working.
I hope this might be useful
http://vivekthangaswamy.blogspot.com/2008/05/none-of-selected-features-can-be.html
Turn on all the Windows Features for IIS - this fixed the problem for me.
This is done via Start -> Control Panel -> Programs and Features -> Turn Windows features on or off.
Recently, I've started having a problem with my SQL Server 2005 client running on Windows XP where right-clicking on any job and selecting Properties instead brings me to the New Job window. Also, if I select "View History", I get the history for all jobs, instead of the one I right-clicked on.
This happened to me once before, and I found that I hadn't installed a service pack for SQL 2005. Once I installed it, the problem went away, and I haven't seen it in about a year. I haven't run any updates on it since, and I'm not sure what could have caused this.
As a possibly related note, I've tried installing XP Service Pack 3 on my machine twice, and it just hung on my machine(I started running it on Friday before leaving for the weekend, and it hadn't gone more than5-10% when I got back on Monday). I'm not sure if that fact is related at all, but I thought it possible that the XP update somehow overwrote something that SQL 2005 used before hanging.
Any ideas on what could cause this? I've included the current version info that shows up in SQL 2005.
Microsoft SQL Server Management Studio - 9.00.1399.00
Microsoft Analysis Services Client Tools - 2005.090.1399.00
Microsoft Data Access Components (MDAC) - 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML - 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer - 7.0.5730.13
Microsoft .NET Framework - 2.0.50727.1433
Operating System - 5.1.2600
Update: I reinstalled SQL 2005 service pack 2 on my machine and it fixed the problem. I'll have to see if the problem was caused when I tried installing xp sp3.
I would suggest the following path:
Make sure that you have current backups for the server
Try to get a clean install of the XP service pack
Try reinstalling the client tools on the machine
If that fails, try to install (or reinstall) SP2 for SQL Server