MSDE
Hi All,
Working on MSDE. I've added a Property key BLANKSAPWD=1 to disable the required password but the proble is towards the end of installation it stops and Roll back.
Any idea why this is happening?
Giz
Working on MSDE. I've added a Property key BLANKSAPWD=1 to disable the required password but the proble is towards the end of installation it stops and Roll back.
Any idea why this is happening?
Giz
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
WayneB
17 years ago
Hey Giz,
Are you using any of the SQL merge modules. They could be the problem. What does the log file say?
From this article:
http://support.microsoft.com/kb/810826
If you specify both SAPWD and BLANKSAPWD, SAPWD takes precedence and BLANKSAPWD is ignored.
I had to use a moded SQL merge module for a recent package I did.
Regards
Wayne
Are you using any of the SQL merge modules. They could be the problem. What does the log file say?
From this article:
http://support.microsoft.com/kb/810826
If you specify both SAPWD and BLANKSAPWD, SAPWD takes precedence and BLANKSAPWD is ignored.
I had to use a moded SQL merge module for a recent package I did.
Regards
Wayne
Posted by:
gizmolala
17 years ago
TNX FOR UR HELP. BUT THE MSDE IS STILL NOT INSTALLING. JUST KEEPS ROLLING BACK WHEN THE INSTALLATION IS ALMOST COMPLETE.
HELP URGENTLY NEEDED
GIZ
HELP URGENTLY NEEDED
GIZ
Posted by:
turbokitty
17 years ago
As WayneB said, when you're installing the MSI log it verbosely. The log will tell you why it's rolling back.
Posted by:
gizmolala
17 years ago
Just found out that i've got to install file and print services before MSDE can actually install. The problem is all our machines don't have them enabled. Is there a way to automate the start of File and Print services?
Giz
Giz
Posted by:
mazessj
17 years ago
Giz,
I'm guessing that when you say "File and Print services" that you are actually referring to the Server service. I am also assuming that you are working in an environment that consists of Windows 2000 and above. This service should never be disabled on a Windows workstation as it provides support for other things besides File and Print services. You should probably check your event logs to see if anything else has been complaining about this disabled service. But I digress. I have worked for an organization that disabled the Server service and I had to deal with it. I wrote a procedure that checked the service state, enabled and started it if it needed to be, then disabled it after the MSDE installation if it was disabled originally.
Before you can start the service, you need to make sure that it is enabled. Windows XP comes with a command line utility called sc.exe (SC stands for Service Control). As I recall, it is compatible with Windows 2000. Run sc.exe config lanmanserver start=auto (note that you have to use the internal name for the Server service, lanmanserver). This sets the startup mode for the Server service to Automatic. Once you've done that, you can then initiate a start control. NET.EXE START Server is one way to do this. This can also be done from some scripting tools. You should pause for about 5-10 seconds after initiating the START control to make sure that the service has enough time to start up before you move on to installing MSDE. In fact, it would be a good idea to make sure the service status changes to "Running."
When I did this, I found WiseScript to be a pretty useful tool, but you can accomplish this in a number of different scripting environments.
--Josh
I'm guessing that when you say "File and Print services" that you are actually referring to the Server service. I am also assuming that you are working in an environment that consists of Windows 2000 and above. This service should never be disabled on a Windows workstation as it provides support for other things besides File and Print services. You should probably check your event logs to see if anything else has been complaining about this disabled service. But I digress. I have worked for an organization that disabled the Server service and I had to deal with it. I wrote a procedure that checked the service state, enabled and started it if it needed to be, then disabled it after the MSDE installation if it was disabled originally.
Before you can start the service, you need to make sure that it is enabled. Windows XP comes with a command line utility called sc.exe (SC stands for Service Control). As I recall, it is compatible with Windows 2000. Run sc.exe config lanmanserver start=auto (note that you have to use the internal name for the Server service, lanmanserver). This sets the startup mode for the Server service to Automatic. Once you've done that, you can then initiate a start control. NET.EXE START Server is one way to do this. This can also be done from some scripting tools. You should pause for about 5-10 seconds after initiating the START control to make sure that the service has enough time to start up before you move on to installing MSDE. In fact, it would be a good idea to make sure the service status changes to "Running."
When I did this, I found WiseScript to be a pretty useful tool, but you can accomplish this in a number of different scripting environments.
--Josh
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.