It seems that on Windows XP SP2, if you already have .NET Framework 3.0 installed, you will get an error while trying to install the pre-release .NET 3.5 beta 1.
The installed will complain about dependencies, one of such is:
Microsoft .NET Framework 3.0SP1 WCF
You will not find this to download anywhere!
The fix!
Uninstall .NET Framework 3.0, then start the 3.5 installation process. The 3.5 installer will grab the bits of 3.0 that it needs. This will fail again BUT it will have installed the necessary prerequisites. You'll get similar DepCheck errors again.
Then, install the: Visual Studio 2005 extensions for .NET Framework 3.0 (Windows Workflow Foundation)
Now, start the 3.5 installation one more time. This time it should complete.
Restart the PC and you're done.
If you're tearing your hair out with the SSIS 'Failed to acquire connection...' error...
.. try setting the TransactionOption property on the package to NotSupported.
Your problem could be that MSDTC is either not running, incorrectly configured, or being blocked by a firewall.
This problem is common when migrating a package, which you've been working on a local dev machine, to a staging or production server. Servers commonly have tighter security restrictions than desktops or perhaps the admin hasn't even enabled MSDTC.
If you really need transactions then you'll have to delve into this issue deeper!
Here's some links to help you:
http://blogs.conchango.com/jamiethomson/archive/2005/11/02/2339.aspx
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=146&messageid=266032
etc..
Your problem could be that MSDTC is either not running, incorrectly configured, or being blocked by a firewall.
This problem is common when migrating a package, which you've been working on a local dev machine, to a staging or production server. Servers commonly have tighter security restrictions than desktops or perhaps the admin hasn't even enabled MSDTC.
If you really need transactions then you'll have to delve into this issue deeper!
Here's some links to help you:
http://blogs.conchango.com/jamiethomson/archive/2005/11/02/2339.aspx
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=146&messageid=266032
etc..
SqlException Number Reference
You can find these in System.Data.SqlClient.TdsEnums using Reflector.
DISCLAIMER: These could be out of date or wrong! I've just listed them here because I couldn't find them on Google.
18456: Logon Failed
18488: Password Expired
DISCLAIMER: These could be out of date or wrong! I've just listed them here because I couldn't find them on Google.
18456: Logon Failed
18488: Password Expired
HTTP 404 error in IIS 6 on new ASP.NET application install
If you're putting together an IIS 6 box and you're getting 404 errors on all your ASP.NET applications, do the following:
1. Open IIS Manager on the IIS box
2. Expand the computer_name node
3. Click on Web Service Extensions
4. Ensure the Status for ASP.NET v2.0.50727 is Allowed
1. Open IIS Manager on the IIS box
2. Expand the computer_name node
3. Click on Web Service Extensions
4. Ensure the Status for ASP.NET v2.0.50727 is Allowed
Repair of a corrupt Microsoft Access ADP file
1. Open a brand new ADP file.
2. Enter the connection details when prompted.
3. File->Get External Data->Import
4. Select the corrupted ADP file
5. Select all Forms, Reports, Macros, Modules that you need. Click OK
6. If all goes well, you'll have a working ADP file again. If it doesn't go well, try being more selective with the imported data. You might have a badly corrupted Report that you'll have to skip.
This may give you some more ideas.
2. Enter the connection details when prompted.
3. File->Get External Data->Import
4. Select the corrupted ADP file
5. Select all Forms, Reports, Macros, Modules that you need. Click OK
6. If all goes well, you'll have a working ADP file again. If it doesn't go well, try being more selective with the imported data. You might have a badly corrupted Report that you'll have to skip.
This may give you some more ideas.
Subscribe to:
Posts (Atom)