Whenever i try to instal sql2005..and proceeds to the selection..in next step where we have to check the workstation option..is disabled..in details it shows upgrade block coz already have later version installed. Even i tried by uninstalling each and every sql file and even deleted from registry still gives same problem. And when i go to start menu and select sql2005 it only show sql server configuration manager and surface manager..please help me i really need to get rid of this.
I just wanted to install Oracle 9.2 for my academic purposes. It doesn't even complete the setup wizard even later I tried with changed compatibility settings, and 'RUN AS ADMIN'. Neither of them worked for me.. It actually crashes while installing sometimes, and sometimes it doesn't set up services properly. This must be a problem in Windows Vista.
But when I used Oracle Express edition it worked, but in there no much functionality to study Oracle well.
Just can manage with single database+ some commands. Better someone can suggest something to do in order to get Oracle up and running in Vista.
this may not fall into the relm of Vista, but I have a question/comment on MS Outlook 2007.
When I get some e-mail that is considered junk and automatically placed in the Junk E-mail folder for Outlook 2007, if I open the Junk E-mail folder and open a message (that I consider safe), it creates a new window of the Outlook GUI in addition to opening the message.
My question would be:
how do I report any bugs or annoyances to the Microsoft developers (haha) so that this annoyance could be rectified in future updates?
I wrote a transport Sink of SMTP service, which works pretty fine in Windows server 2003. Now the server is upgraded to Windows server 2008 and I am suffering two issues:
1. The SMTP service is totally not accessible either through Outlook clinets (outlook express and outlook 2003) or telnet.
While using outlook client, I created a account connecting to the server which hosts SMTP service, and I got the error "4.3.1 Out of memorry" each time I try to send a mail.
While doing the telnet test, I can connect to the SMTP server successfully. "EHLO", "MAIL FROM" and "RCPT TO" commands works fine. However, when it comes to the next command "DATA", the SMTP server returns the same error as what the Outlook client got.
It is said that the insufficient permisson of the "System" account in the machine where the SMTP server is hosted could cause this issue, however, I did checked that the "System" account does have the full permission against the "mailroot" folder.
Anyone could help this issue, I do appreciate.
2. The SMTP sink was found no longer be able to be registered by smtpreg.vbs. I am getting the error "type mismatch". This definitely works fine in windows server 2003. Someone who knows what is going on. I do hope I can gain some help here. Appreciate any kind of help.
i got a problem in vista, and i just don't get it..
the problem is the following, if i publish a new application (an empty form, just a plain new windows forms application) from a windows 2000 pc from Visual studio 2005, and i try to run it on a vista pc, i get an error "cannot launch application. please contact vendor". When checking the error log it says i need elevated rights to run the application. (errorcode 0x800702E4) I googled this a bunch of times, but no results which can help me.
The weird part is:
Every application published, lets say a week ago or earlier, works on vista, and launches without problems (also published from a win2000 pc in vs2005)
If i publish a new version of an older application, then this application will also launch succesfully in vista.
So its only new applications that i cant get working in vista???
I tried publishing a new windows forms application on my vista pc in vs2005, this application also launches succesfully
I tried publishing a new version of a new application (which didnt work) from my vista pc in vs2005, this application won't work either.
I guess it has to do something with the policies in Vista, but its strange that it only affects newly published applications published from Win2000, or existing non-working applications published from vista...
It's a long shot, but does anyone here has any experience with problems like this? The only thing i can do as a workaround is making a new project on my vista pc, copying all the code in there, and publish it from there. *sigh*, got to love vista...
After 3 weeks i finally stumbled upon the cause of the problem.
All my non working applications had the string "update" in their filename/assemblyname...
And of course everyone (except for me) knows that the UAC recognizes the program as an installer
when the string "update" is found in the filename/assemblyname.
Installer Detection Technology
Installation programs are applications designed to deploy software, and most write to system directories
and registry keys. These protected system locations are typically writeable only by an administrator
user, which means that standard users donot have sufficient access to install programs. Windows Vista
heuristically detects installation programs and requests administrator credentials or approval from the
administrator user in order to run with access privileges. Windows Vista also heuristically detects
updater and uninstallation programs. Note that a design goal of UAC is to prevent installations from
being executed without the user's knowledge and consent since they write to protected areas of the file system and registry.
Installer Detection only applies to:
1. 32 bit executables
2. Applications without a requestedExecutionLevel
3. Interactive processes running as a Standard User with LUA enabled
Before a 32 bit process is created, the following attributes are checked to determine whether
it is an installer:
Filename includes keywords like "install," "setup," "update," etc.
Keywords in the following Versioning Resource fields: Vendor, Company Name, Product Name, File
Description, Original Filename, Internal Name, and Export Name.
Keywords in the side-by-side manifest embedded in the executable.
Keywords in specific StringTable entries linked in the executable.
Key attributes in the RC data linked in the executable.
Targeted sequences of bytes within the executable.
Last Visit: 31-Dec-99 19:00 Last Update: 26-Nov-15 15:27