This Is Why I Never Seem To Make Much Progress With Programming
-
So I had an idea for a database project in the last few days, and I sat down last night to try it out. Just a sample, mind you, to test a technique that ought to work. It took me 10 minutes to create the sample project and code the statements I needed. In essence, I'm contacting a SQL Server hosted on my SBS 2003 server to duplicate conditions at work. I ran the code and got an error - #26, in case you're interested. For the next 2 hours I searched for possible causes on the server, noting in the meantime that it had been automatically rebooted because of a Microsoft Update. No luck there, as the SQL Server installation is configured for remote access and TCP is enabled. I spent a bunch of time researching on the web, but it all came down to having those two items set up correctly. Back to the client... On a hunch I loaded and tried two other apps I've written that worked fine a couple of months ago. They're not finished, but they had no trouble connecting before; now they emit the same error! It's got to be on the server somewhere!!! So I spent some more time there, researching and trying stuff, and I discovered that the SQL Browser Service shuts down immediately on starting, and leaves a helpful message in the Event log: "incorrect parameters." What the hell does that mean??? There are no settable parameters for the SQL Browser service. My next bright idea was that something is screwed up in the SQL Express installation and I should try fixing that. Since I have R2 lying about on another drive but not yet installed, I figured this would be a good time to upgrade and maybe fix the problem. I selected a clean installation (rather than updating a broken installation) and to my surprise it proceeded to install a new instance, rather than overwriting the old version! Eons later it bailed out of that installation with an error - the SQL Browser service could not be started. Grrrrr....:mad: By this time it was 1 AM and long past my bedtime - gotta work at 5. All creative thoughts are now crashed and burned, and what started out a relaxing evening of programming and learning was long gone to hell. All I can think of now is to rebuild the server again from scratch, at least a week's project, if it works at all - Small Business Server is a touchy heap of trash and rarely works correctly. No, I'm not looking for answers, and there's no programming question here. Just ranting on a dull night since there are few members posting tonight, and some nightowls might like some easy reading. When I get the se
-
So I had an idea for a database project in the last few days, and I sat down last night to try it out. Just a sample, mind you, to test a technique that ought to work. It took me 10 minutes to create the sample project and code the statements I needed. In essence, I'm contacting a SQL Server hosted on my SBS 2003 server to duplicate conditions at work. I ran the code and got an error - #26, in case you're interested. For the next 2 hours I searched for possible causes on the server, noting in the meantime that it had been automatically rebooted because of a Microsoft Update. No luck there, as the SQL Server installation is configured for remote access and TCP is enabled. I spent a bunch of time researching on the web, but it all came down to having those two items set up correctly. Back to the client... On a hunch I loaded and tried two other apps I've written that worked fine a couple of months ago. They're not finished, but they had no trouble connecting before; now they emit the same error! It's got to be on the server somewhere!!! So I spent some more time there, researching and trying stuff, and I discovered that the SQL Browser Service shuts down immediately on starting, and leaves a helpful message in the Event log: "incorrect parameters." What the hell does that mean??? There are no settable parameters for the SQL Browser service. My next bright idea was that something is screwed up in the SQL Express installation and I should try fixing that. Since I have R2 lying about on another drive but not yet installed, I figured this would be a good time to upgrade and maybe fix the problem. I selected a clean installation (rather than updating a broken installation) and to my surprise it proceeded to install a new instance, rather than overwriting the old version! Eons later it bailed out of that installation with an error - the SQL Browser service could not be started. Grrrrr....:mad: By this time it was 1 AM and long past my bedtime - gotta work at 5. All creative thoughts are now crashed and burned, and what started out a relaxing evening of programming and learning was long gone to hell. All I can think of now is to rebuild the server again from scratch, at least a week's project, if it works at all - Small Business Server is a touchy heap of trash and rarely works correctly. No, I'm not looking for answers, and there's no programming question here. Just ranting on a dull night since there are few members posting tonight, and some nightowls might like some easy reading. When I get the se
-
So I had an idea for a database project in the last few days, and I sat down last night to try it out. Just a sample, mind you, to test a technique that ought to work. It took me 10 minutes to create the sample project and code the statements I needed. In essence, I'm contacting a SQL Server hosted on my SBS 2003 server to duplicate conditions at work. I ran the code and got an error - #26, in case you're interested. For the next 2 hours I searched for possible causes on the server, noting in the meantime that it had been automatically rebooted because of a Microsoft Update. No luck there, as the SQL Server installation is configured for remote access and TCP is enabled. I spent a bunch of time researching on the web, but it all came down to having those two items set up correctly. Back to the client... On a hunch I loaded and tried two other apps I've written that worked fine a couple of months ago. They're not finished, but they had no trouble connecting before; now they emit the same error! It's got to be on the server somewhere!!! So I spent some more time there, researching and trying stuff, and I discovered that the SQL Browser Service shuts down immediately on starting, and leaves a helpful message in the Event log: "incorrect parameters." What the hell does that mean??? There are no settable parameters for the SQL Browser service. My next bright idea was that something is screwed up in the SQL Express installation and I should try fixing that. Since I have R2 lying about on another drive but not yet installed, I figured this would be a good time to upgrade and maybe fix the problem. I selected a clean installation (rather than updating a broken installation) and to my surprise it proceeded to install a new instance, rather than overwriting the old version! Eons later it bailed out of that installation with an error - the SQL Browser service could not be started. Grrrrr....:mad: By this time it was 1 AM and long past my bedtime - gotta work at 5. All creative thoughts are now crashed and burned, and what started out a relaxing evening of programming and learning was long gone to hell. All I can think of now is to rebuild the server again from scratch, at least a week's project, if it works at all - Small Business Server is a touchy heap of trash and rarely works correctly. No, I'm not looking for answers, and there's no programming question here. Just ranting on a dull night since there are few members posting tonight, and some nightowls might like some easy reading. When I get the se
Make sure you don't have compression turned on for the drive. That screwed me before (SQL Server doesn't like to install on compressed drives, but it's a little shy and doesn't mention that when it fails to install).
-
So I had an idea for a database project in the last few days, and I sat down last night to try it out. Just a sample, mind you, to test a technique that ought to work. It took me 10 minutes to create the sample project and code the statements I needed. In essence, I'm contacting a SQL Server hosted on my SBS 2003 server to duplicate conditions at work. I ran the code and got an error - #26, in case you're interested. For the next 2 hours I searched for possible causes on the server, noting in the meantime that it had been automatically rebooted because of a Microsoft Update. No luck there, as the SQL Server installation is configured for remote access and TCP is enabled. I spent a bunch of time researching on the web, but it all came down to having those two items set up correctly. Back to the client... On a hunch I loaded and tried two other apps I've written that worked fine a couple of months ago. They're not finished, but they had no trouble connecting before; now they emit the same error! It's got to be on the server somewhere!!! So I spent some more time there, researching and trying stuff, and I discovered that the SQL Browser Service shuts down immediately on starting, and leaves a helpful message in the Event log: "incorrect parameters." What the hell does that mean??? There are no settable parameters for the SQL Browser service. My next bright idea was that something is screwed up in the SQL Express installation and I should try fixing that. Since I have R2 lying about on another drive but not yet installed, I figured this would be a good time to upgrade and maybe fix the problem. I selected a clean installation (rather than updating a broken installation) and to my surprise it proceeded to install a new instance, rather than overwriting the old version! Eons later it bailed out of that installation with an error - the SQL Browser service could not be started. Grrrrr....:mad: By this time it was 1 AM and long past my bedtime - gotta work at 5. All creative thoughts are now crashed and burned, and what started out a relaxing evening of programming and learning was long gone to hell. All I can think of now is to rebuild the server again from scratch, at least a week's project, if it works at all - Small Business Server is a touchy heap of trash and rarely works correctly. No, I'm not looking for answers, and there's no programming question here. Just ranting on a dull night since there are few members posting tonight, and some nightowls might like some easy reading. When I get the se
I think you missed an important step. Whenever I plan to code till 1 AM, I have my first beer at 8 PM - that way I can concentrate till early morning.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it. My latest tip/trick - Silverlight *.XCP files. Visit the Hindi forum here.
-
Make sure you don't have compression turned on for the drive. That screwed me before (SQL Server doesn't like to install on compressed drives, but it's a little shy and doesn't mention that when it fails to install).
I've never tried compressing a drive - I just buy bigger ones, or add more. I've always feared that if I did, Windows would crash and I'd never be able to unlock the compression with a new installation. :-O
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
I know what you mean, whenever you need to try something "quick", something else critical breaks! PS: It's 8:40 AM where I am - I'm sure there's other people accross the world in the lounge, so please keep posting :)
I wish I could say that this is unusual, but it's not. It seems that every few weeks or months, usually when I'm feeling really creative and motivated, Windows does something like this and it turns into a multi-week exercise in futility to make something fundamental work again. Curiously, it usually happens after a recent update from Microsoft...
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
I think you missed an important step. Whenever I plan to code till 1 AM, I have my first beer at 8 PM - that way I can concentrate till early morning.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it. My latest tip/trick - Silverlight *.XCP files. Visit the Hindi forum here.
I usually start about the same time, but I sip gently until something like this happens. Then I break out the scotch for some really serious concentration. Tonight I was able to find some articles at Microsoft Support that provide instructions for removing Exchange and Sharepoint Servers from my machine when I reinstall - those are two dogs I don't need bogging down my server. My only concern is that doing so will make my server different from what we use at work, and all of my programming is to build stuff for me to use there. It's best to make them match as closely as possible, else I'm likely to see unexpected mysteries crop up when I deploy my tools in the office.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
So I had an idea for a database project in the last few days, and I sat down last night to try it out. Just a sample, mind you, to test a technique that ought to work. It took me 10 minutes to create the sample project and code the statements I needed. In essence, I'm contacting a SQL Server hosted on my SBS 2003 server to duplicate conditions at work. I ran the code and got an error - #26, in case you're interested. For the next 2 hours I searched for possible causes on the server, noting in the meantime that it had been automatically rebooted because of a Microsoft Update. No luck there, as the SQL Server installation is configured for remote access and TCP is enabled. I spent a bunch of time researching on the web, but it all came down to having those two items set up correctly. Back to the client... On a hunch I loaded and tried two other apps I've written that worked fine a couple of months ago. They're not finished, but they had no trouble connecting before; now they emit the same error! It's got to be on the server somewhere!!! So I spent some more time there, researching and trying stuff, and I discovered that the SQL Browser Service shuts down immediately on starting, and leaves a helpful message in the Event log: "incorrect parameters." What the hell does that mean??? There are no settable parameters for the SQL Browser service. My next bright idea was that something is screwed up in the SQL Express installation and I should try fixing that. Since I have R2 lying about on another drive but not yet installed, I figured this would be a good time to upgrade and maybe fix the problem. I selected a clean installation (rather than updating a broken installation) and to my surprise it proceeded to install a new instance, rather than overwriting the old version! Eons later it bailed out of that installation with an error - the SQL Browser service could not be started. Grrrrr....:mad: By this time it was 1 AM and long past my bedtime - gotta work at 5. All creative thoughts are now crashed and burned, and what started out a relaxing evening of programming and learning was long gone to hell. All I can think of now is to rebuild the server again from scratch, at least a week's project, if it works at all - Small Business Server is a touchy heap of trash and rarely works correctly. No, I'm not looking for answers, and there's no programming question here. Just ranting on a dull night since there are few members posting tonight, and some nightowls might like some easy reading. When I get the se
You can also get this if the firewall is turned on and the exception hasn't been put in, did you have the firewall turned off previously? If the firewall is enabled on the server, you need to put sqlbrowser.exe and/or UDP port 1434 into exception.
People are more violently opposed to fur than leather because it's safer to harass rich women than motorcycle gangs
-
So I had an idea for a database project in the last few days, and I sat down last night to try it out. Just a sample, mind you, to test a technique that ought to work. It took me 10 minutes to create the sample project and code the statements I needed. In essence, I'm contacting a SQL Server hosted on my SBS 2003 server to duplicate conditions at work. I ran the code and got an error - #26, in case you're interested. For the next 2 hours I searched for possible causes on the server, noting in the meantime that it had been automatically rebooted because of a Microsoft Update. No luck there, as the SQL Server installation is configured for remote access and TCP is enabled. I spent a bunch of time researching on the web, but it all came down to having those two items set up correctly. Back to the client... On a hunch I loaded and tried two other apps I've written that worked fine a couple of months ago. They're not finished, but they had no trouble connecting before; now they emit the same error! It's got to be on the server somewhere!!! So I spent some more time there, researching and trying stuff, and I discovered that the SQL Browser Service shuts down immediately on starting, and leaves a helpful message in the Event log: "incorrect parameters." What the hell does that mean??? There are no settable parameters for the SQL Browser service. My next bright idea was that something is screwed up in the SQL Express installation and I should try fixing that. Since I have R2 lying about on another drive but not yet installed, I figured this would be a good time to upgrade and maybe fix the problem. I selected a clean installation (rather than updating a broken installation) and to my surprise it proceeded to install a new instance, rather than overwriting the old version! Eons later it bailed out of that installation with an error - the SQL Browser service could not be started. Grrrrr....:mad: By this time it was 1 AM and long past my bedtime - gotta work at 5. All creative thoughts are now crashed and burned, and what started out a relaxing evening of programming and learning was long gone to hell. All I can think of now is to rebuild the server again from scratch, at least a week's project, if it works at all - Small Business Server is a touchy heap of trash and rarely works correctly. No, I'm not looking for answers, and there's no programming question here. Just ranting on a dull night since there are few members posting tonight, and some nightowls might like some easy reading. When I get the se
Roger Wright wrote:
a relaxing evening of programming
Bwahahahaaaa!
-
You can also get this if the firewall is turned on and the exception hasn't been put in, did you have the firewall turned off previously? If the firewall is enabled on the server, you need to put sqlbrowser.exe and/or UDP port 1434 into exception.
People are more violently opposed to fur than leather because it's safer to harass rich women than motorcycle gangs
I've never used the firewall, but that's no guarantee that Microsoft Update didn't turn it on without telling me. I'll check that. Thanks! :-D
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
I've never tried compressing a drive - I just buy bigger ones, or add more. I've always feared that if I did, Windows would crash and I'd never be able to unlock the compression with a new installation. :-O
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
Keep thinking that way, compressing is a last resort.
"When did ignorance become a point of view" - Dilbert
-
So I had an idea for a database project in the last few days, and I sat down last night to try it out. Just a sample, mind you, to test a technique that ought to work. It took me 10 minutes to create the sample project and code the statements I needed. In essence, I'm contacting a SQL Server hosted on my SBS 2003 server to duplicate conditions at work. I ran the code and got an error - #26, in case you're interested. For the next 2 hours I searched for possible causes on the server, noting in the meantime that it had been automatically rebooted because of a Microsoft Update. No luck there, as the SQL Server installation is configured for remote access and TCP is enabled. I spent a bunch of time researching on the web, but it all came down to having those two items set up correctly. Back to the client... On a hunch I loaded and tried two other apps I've written that worked fine a couple of months ago. They're not finished, but they had no trouble connecting before; now they emit the same error! It's got to be on the server somewhere!!! So I spent some more time there, researching and trying stuff, and I discovered that the SQL Browser Service shuts down immediately on starting, and leaves a helpful message in the Event log: "incorrect parameters." What the hell does that mean??? There are no settable parameters for the SQL Browser service. My next bright idea was that something is screwed up in the SQL Express installation and I should try fixing that. Since I have R2 lying about on another drive but not yet installed, I figured this would be a good time to upgrade and maybe fix the problem. I selected a clean installation (rather than updating a broken installation) and to my surprise it proceeded to install a new instance, rather than overwriting the old version! Eons later it bailed out of that installation with an error - the SQL Browser service could not be started. Grrrrr....:mad: By this time it was 1 AM and long past my bedtime - gotta work at 5. All creative thoughts are now crashed and burned, and what started out a relaxing evening of programming and learning was long gone to hell. All I can think of now is to rebuild the server again from scratch, at least a week's project, if it works at all - Small Business Server is a touchy heap of trash and rarely works correctly. No, I'm not looking for answers, and there's no programming question here. Just ranting on a dull night since there are few members posting tonight, and some nightowls might like some easy reading. When I get the se
Maybe Christian can come round and help you 'fix' things, next time he's in the US of A. :)
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.”
-
I usually start about the same time, but I sip gently until something like this happens. Then I break out the scotch for some really serious concentration. Tonight I was able to find some articles at Microsoft Support that provide instructions for removing Exchange and Sharepoint Servers from my machine when I reinstall - those are two dogs I don't need bogging down my server. My only concern is that doing so will make my server different from what we use at work, and all of my programming is to build stuff for me to use there. It's best to make them match as closely as possible, else I'm likely to see unexpected mysteries crop up when I deploy my tools in the office.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
Roger Wright wrote:
Then I break out the scotch for some really serious concentration.
Have you tried this[^]? When you do there is no need for concentration, the problems will sovle themselves.
My .NET Business Application Framework My Younger Son & His "PET"
-
So I had an idea for a database project in the last few days, and I sat down last night to try it out. Just a sample, mind you, to test a technique that ought to work. It took me 10 minutes to create the sample project and code the statements I needed. In essence, I'm contacting a SQL Server hosted on my SBS 2003 server to duplicate conditions at work. I ran the code and got an error - #26, in case you're interested. For the next 2 hours I searched for possible causes on the server, noting in the meantime that it had been automatically rebooted because of a Microsoft Update. No luck there, as the SQL Server installation is configured for remote access and TCP is enabled. I spent a bunch of time researching on the web, but it all came down to having those two items set up correctly. Back to the client... On a hunch I loaded and tried two other apps I've written that worked fine a couple of months ago. They're not finished, but they had no trouble connecting before; now they emit the same error! It's got to be on the server somewhere!!! So I spent some more time there, researching and trying stuff, and I discovered that the SQL Browser Service shuts down immediately on starting, and leaves a helpful message in the Event log: "incorrect parameters." What the hell does that mean??? There are no settable parameters for the SQL Browser service. My next bright idea was that something is screwed up in the SQL Express installation and I should try fixing that. Since I have R2 lying about on another drive but not yet installed, I figured this would be a good time to upgrade and maybe fix the problem. I selected a clean installation (rather than updating a broken installation) and to my surprise it proceeded to install a new instance, rather than overwriting the old version! Eons later it bailed out of that installation with an error - the SQL Browser service could not be started. Grrrrr....:mad: By this time it was 1 AM and long past my bedtime - gotta work at 5. All creative thoughts are now crashed and burned, and what started out a relaxing evening of programming and learning was long gone to hell. All I can think of now is to rebuild the server again from scratch, at least a week's project, if it works at all - Small Business Server is a touchy heap of trash and rarely works correctly. No, I'm not looking for answers, and there's no programming question here. Just ranting on a dull night since there are few members posting tonight, and some nightowls might like some easy reading. When I get the se
Roger Wright wrote:
Microsoft Update
Given how many times I've read how M.U. has screwed people, it still amazes me that people, especially developers, on development environments, keep this thing turned on. Why??? Marc
-
So I had an idea for a database project in the last few days, and I sat down last night to try it out. Just a sample, mind you, to test a technique that ought to work. It took me 10 minutes to create the sample project and code the statements I needed. In essence, I'm contacting a SQL Server hosted on my SBS 2003 server to duplicate conditions at work. I ran the code and got an error - #26, in case you're interested. For the next 2 hours I searched for possible causes on the server, noting in the meantime that it had been automatically rebooted because of a Microsoft Update. No luck there, as the SQL Server installation is configured for remote access and TCP is enabled. I spent a bunch of time researching on the web, but it all came down to having those two items set up correctly. Back to the client... On a hunch I loaded and tried two other apps I've written that worked fine a couple of months ago. They're not finished, but they had no trouble connecting before; now they emit the same error! It's got to be on the server somewhere!!! So I spent some more time there, researching and trying stuff, and I discovered that the SQL Browser Service shuts down immediately on starting, and leaves a helpful message in the Event log: "incorrect parameters." What the hell does that mean??? There are no settable parameters for the SQL Browser service. My next bright idea was that something is screwed up in the SQL Express installation and I should try fixing that. Since I have R2 lying about on another drive but not yet installed, I figured this would be a good time to upgrade and maybe fix the problem. I selected a clean installation (rather than updating a broken installation) and to my surprise it proceeded to install a new instance, rather than overwriting the old version! Eons later it bailed out of that installation with an error - the SQL Browser service could not be started. Grrrrr....:mad: By this time it was 1 AM and long past my bedtime - gotta work at 5. All creative thoughts are now crashed and burned, and what started out a relaxing evening of programming and learning was long gone to hell. All I can think of now is to rebuild the server again from scratch, at least a week's project, if it works at all - Small Business Server is a touchy heap of trash and rarely works correctly. No, I'm not looking for answers, and there's no programming question here. Just ranting on a dull night since there are few members posting tonight, and some nightowls might like some easy reading. When I get the se
LOL yeah - same sort of thing here usually!
-
So I had an idea for a database project in the last few days, and I sat down last night to try it out. Just a sample, mind you, to test a technique that ought to work. It took me 10 minutes to create the sample project and code the statements I needed. In essence, I'm contacting a SQL Server hosted on my SBS 2003 server to duplicate conditions at work. I ran the code and got an error - #26, in case you're interested. For the next 2 hours I searched for possible causes on the server, noting in the meantime that it had been automatically rebooted because of a Microsoft Update. No luck there, as the SQL Server installation is configured for remote access and TCP is enabled. I spent a bunch of time researching on the web, but it all came down to having those two items set up correctly. Back to the client... On a hunch I loaded and tried two other apps I've written that worked fine a couple of months ago. They're not finished, but they had no trouble connecting before; now they emit the same error! It's got to be on the server somewhere!!! So I spent some more time there, researching and trying stuff, and I discovered that the SQL Browser Service shuts down immediately on starting, and leaves a helpful message in the Event log: "incorrect parameters." What the hell does that mean??? There are no settable parameters for the SQL Browser service. My next bright idea was that something is screwed up in the SQL Express installation and I should try fixing that. Since I have R2 lying about on another drive but not yet installed, I figured this would be a good time to upgrade and maybe fix the problem. I selected a clean installation (rather than updating a broken installation) and to my surprise it proceeded to install a new instance, rather than overwriting the old version! Eons later it bailed out of that installation with an error - the SQL Browser service could not be started. Grrrrr....:mad: By this time it was 1 AM and long past my bedtime - gotta work at 5. All creative thoughts are now crashed and burned, and what started out a relaxing evening of programming and learning was long gone to hell. All I can think of now is to rebuild the server again from scratch, at least a week's project, if it works at all - Small Business Server is a touchy heap of trash and rarely works correctly. No, I'm not looking for answers, and there's no programming question here. Just ranting on a dull night since there are few members posting tonight, and some nightowls might like some easy reading. When I get the se
What a waste of a Thursday night.
-
Roger Wright wrote:
Then I break out the scotch for some really serious concentration.
Have you tried this[^]? When you do there is no need for concentration, the problems will sovle themselves.
My .NET Business Application Framework My Younger Son & His "PET"
I don't see the "in case of emergency break glass" notation.
-
Roger Wright wrote:
Then I break out the scotch for some really serious concentration.
Have you tried this[^]? When you do there is no need for concentration, the problems will sovle themselves.
My .NET Business Application Framework My Younger Son & His "PET"
No, but I have a rather large bottle of sake a friend brought me from Japan. It's tasty, but it gives me odd cravings for Japanese women, and an urge to swing a sword.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
No, but I have a rather large bottle of sake a friend brought me from Japan. It's tasty, but it gives me odd cravings for Japanese women, and an urge to swing a sword.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
Roger Wright wrote:
odd cravings for Japanese women, and an urge to swing a sword.
Now I see the problem with concentration.
My .NET Business Application Framework My Younger Son & His "PET"
