Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements


RichardRudek RichardRudek So what do you expect for nothin'... :P
  • MSDE on Win2k not showing up in client listing.

    And this KB Article  explains that it's a firewall/timeout issue Wink

    You may not be able to enumerate all the instances of SQL Server 2000 on your network by using an application or a program

    Article ID    :    885345
    Last Review    :    September 14, 2004
    Revision    :    1.0

    If you try to enumerate the instances of Microsoft SQL Server 2000 that are currently active on your network by using an application or a method in a program, the application or the program may not list all the instances of SQL Server 2000. The application or the program that enumerates the instances of SQL Server 2000 on a network can be your own custom application or a SQL Server tool, such as SQL Server Enterprise Manager, SQL Server Service Manager, or SQL Query Analyzer.

    Note This problem occurs on computers that are running Microsoft Windows XP Service Pack 2 (SP2).

    To determine and enumerate the instances of SQL Server that are running on remote computers, the application or the program uses the APIs, such as SQLBrowseConnect, that send User Datagram Protocol (UDP) packets to all the computers on your network from a network port. The remote computers then send the details of the instances of SQL Server to the application or the program by using the same network port.

    By default, Windows Firewall permits incoming unicast response packets to a port for only 3 seconds after a multicast packet or a broadcast packet is sent from the port. If the remote computers send the details of the instances of SQL Server after 3 seconds, the information is blocked by the Windows Firewall. Therefore, the enumeration may not contain all the instances of SQL Server that are currently active on your network.

    To work around this problem, you must add the application or the program that enumerates the instances of SQL Server 2000 on a network to the Windows Firewall exception list on the computer that is running Windows XP SP2.

    For more information about how to add an application or a program to the Windows Firewall exception list, see the "Allowing exceptions despite the risks" section on the following Microsoft Web site:
    http://www.microsoft.com/windowsxp/using/security/internet/sp2_wfexceptions.mspx (http://www.microsoft.com/windowsxp/using/security/internet/sp2_wfexceptions.mspx)

    This behavior is by design.

    REFERENCES For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
    841771 (http://support.microsoft.com/kb/841771/) All the instances of SQL Server or SQL Server Desktop Engine are not enumerated when you use an application or a method that uses SQLBrowseConnect
    843090 (http://support.microsoft.com/kb/843090/) Description of the Windows Firewall feature in Windows XP Service Pack 2
    875357 (http://support.microsoft.com/kb/875357/) Troubleshooting Windows Firewall settings in Windows XP Service Pack 2

  • Can WScript do this?

    W3bbo wrote:
    I need to write a script to automate this complex task I've been doing a few times, it's very error-prone so I need to script it.

    Look into ADSI. There are providers(^) that support each of these, though with later versions of Exchange (2000+), the doco recommends using CDOEXM (CDO for Exchange Management), instead.

    ^ Each provider is described in the product's documentation, so it's a PITA to find them.

    ADSI Intro

    Exchange doco (root) which can be traversed to these:
      Exchange 5.5 Create Mailbox
      Exchange 2000 Management


    If you have MSDN installed locally, this info is all there. Though the contents trees are different between mine (old-ish) and to the website's (reorganising, I believe)...

  • STOP Errors during W2k3 Server Install

    The Specs on that product lists the Power Supply as being (only) 250 Watt. What sort of graphics (display) card have you got in it ?

    Basically, I think you've got a power problem. Without knowing the power output for each of the voltage rails (not in the specs I've read), it's hard to be specific. But assuming that Shuttle aren't idiots, the basic motherboard stuff should be fine. As there isn't a lot of room in the casing for things like the hard disks, etc, that then leaves the graphics card.

  • MSDE on Win2k not showing up in client listing.

    qwert231 wrote:
    No ideas?

    Search engine ?

    KB article: 841771

  • Windows ​Virtualizat​ion Environment

    I don't believe there has been any significant changes to the way Vista will use the Virtual Memory/Protected Memory systems. These are processor (hardware) based systems, which are described, in all of their gory detail, in the processor manufacturer's (Intel/AMD) programmers guides. eg:
    Intel System Programming Guide Part 1 and Part 2

    In other words, the fundamental parts of Windows NT architecture documents should still apply for Vista:


    In short, the virtualisation technology (Intel Ch19 ?) adds a few instructions which allows OS developers to improve the operation of the Virtualisation. However, all of the memory protection stuff is still in place. If I remember correctly, the show on Virtual Server 2005 (a few months ago ?) talked about how the Virtual Machines (Kernels) were being run from Ring1 - without virtualisation, they would normally be in Ring 0 (zero).

  • .net 1.1 and 2.0 ​compatibili​ty Issue

    manojT wrote:

    Scenario After Installing .Net Framework 2.0

    I have Installed .Net framework 2.0 and then UnInstalled the .net Framework 1.1 now it behaves Strangely
    Application Invoked through JSP, which does not download exe and throws an Ieexec.exe FileNotFound Exception.

    120 people have viewed, but noone answered ?

    I'm not a .NET developer, but a quick search on FileNotFound Exception leads me to believe that the problem is that an assembly is missing.

    So can I ask, why did you uninstall .NET 1.1 AFTER you installed .NET 2.0 ?

    I mean, I believe that the .NET 2.0 install checks for 1.1, beforehand, and installs it, if it's not.

  • How do you convert 8.3 name to long name with wscript?

    Yeah, it's a PITA. I had to iterate through the containing folder's files and compare their shortnames:

    set fso = CreateObject("Scripting.FileSystemObject")

    fname = "D:\TEMP\config~1.doc"

    ' Make a file object from filepath argument.
    set f = fso.GetFile(fname)
    if (not IsObject(f)) or (TypeName(f) <> "File") then WScript.Quit

    ' Get the containing folder object.
    set fld = f.ParentFolder
    if (not IsObject(fld)) or (TypeName(fld) <> "Folder") then WScript.Quit

    ' Iterate through the containg folder's files, comparing the short names.
    s = UCase(f.ShortName)
    for each i in fld.Files
    b = (i.ShortName = s)
    if b then exit for
    if not b then WScript.Quit

    WScript.Echo "Name: " & i.Name & vbCrLf & "ShortName: " & i.ShortName

  • Vista Beta 2 Installed

    shortie wrote:
    Hi there, I grabbed my copy of Beta 2 and having a big problem.... On my Dell Inspiron 9400 it installs perfect but on my selfmade workstation it crashes. So here is what I have and what I'm doing: ASUS A8N-SLI, with 2 GB RAM, 2 * RAID 0 configured, AMD 4600 CPU in it, burned 32 and 64 bit versions of BEta 2, booting up shortly after diplaying "Windows loading files" I get the nice wallpaper and then the maschine crashes into a BSOD MASCHINE_CHECK_EXEPTION STOP:0x0000009c Any idea what the problem might be?? Kind regards, shortie

    My local MSDN Library throws up three items for STOP:0x0000009c
    PSS ID Number: 840551 (2003, 64-bit)
    PSS ID Number: 329284 (XP)
    PSS ID Number: ? (2000) Basically says nothing.

    The 64-bit one basically talks about address wrap-around at the 4GB Boundary. The XP one basically talks about hardware errors, caused by all manner of things, including overclocking.

    You should also check wether there is a later BIOS.

    Another thing you might like to check, though it doesn't look like a disk error, is wether you need to load drivers to support your RAID-0 setup. I've not tested Vista, but in XP, you needed to load the Hard Disk (RAID) drivers during the text-mode setup, pressing F5 (or was it F6?) to choose and load the driver from floppy disk (!!!).