Export (0) Print
Expand All

7 Appendix B: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs:

  • Windows NT operating system

  • Windows 2000 operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

  • Windows Vista operating system

  • Windows Server 2003 R2 operating system

  • Windows Server 2008 operating system

  • Windows 7 operating system

  • Windows Server 2008 R2 operating system

  • Windows 8 operating system

  • Windows Server 2012 operating system

  • Windows 8.1 operating system

  • Windows Server 2012 R2 operating system

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.

<1> Section 2.1.2: Windows uses an authentication level of RPC_C_AUTHN_LEVEL_PKT_PRIVACY only in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.

<2> Section 2.2.21: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<3> Section 2.2.21: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<4> Section 2.2.21: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<5> Section 2.2.21: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<6> Section 2.2.21: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<7> Section 2.2.21: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<8> Section 2.2.21: Available in Windows 7 and Windows Server 2008 R2 operating systems.

<9> Section 2.2.21: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<10> Section 2.2.21: Available in Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<11> Section 2.2.21: Available in Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<12> Section 2.2.22: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<13> Section 2.2.22: Available in Windows 7 and Windows Server 2008 R2.

<14> Section 2.2.22: Available in Windows 7 and Windows Server 2008 R2.

<15> Section 2.2.22: Available in Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<16> Section 2.2.22: Available in Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<17> Section 2.2.23: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<18> Section 2.2.24: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<19> Section 2.2.30: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<20> Section 2.2.31: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<21> Section 2.2.32: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<22> Section 2.2.33: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<23> Section 2.2.41: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<24> Section 2.2.42: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<25> Section 2.2.44: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<26> Section 2.2.45: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<27> Section 2.2.46: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<28> Section 2.2.47: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.

<29> Section 2.2.47: Available in Windows 7 and Windows Server 2008 R2.

<30> Section 2.2.47: Available in Windows 7 and Windows Server 2008 R2.

<31> Section 2.2.47: Windows services indicate service-specific error codes by setting dwWin32ExitCode to ERROR_SERVICE_SPECIFIC_ERROR (1066) and setting the specific error in the dwServiceSpecificExitCode member.

<32> Section 2.2.48: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<33> Section 2.2.49: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<34> Section 2.2.49: Available in Windows 7 and Windows Server 2008 R2.

<35> Section 2.2.49: Available in Windows 7 and Windows Server 2008 R2.

<36> Section 2.2.52: Available in Windows 7 and Windows Server 2008 R2.

<37> Section 2.2.53: Available in Windows 7 and Windows Server 2008 R2.

<38> Section 2.2.54: Available in Windows 7 and Windows Server 2008 R2.

<39> Section 2.2.55: Available in Windows 7 and Windows Server 2008 R2.

<40> Section 3.1.1: In Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2008 R2, localized strings are not supported.

<41> Section 3.1.1: Available in Windows 7 and Windows Server 2008 R2.

<42> Section 3.1.1: Available in Windows 7 and Windows Server 2008 R2.

<43> Section 3.1.4: Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 clients use multiplexed RPC connections for RGetNotifyResults on request if the server supports them, and they fall back to non-multiplexed connections if the server doesn't support multiplexed connections.

<44> Section 3.1.4: Available in Windows 7 and Windows Server 2008 R2.

<45> Section 3.1.4: Gaps in the opnum numbering sequence apply to Windows as follows.

Opnum

Description

10

Only used locally by Windows, never remotely.

22

Only used locally by Windows, never remotely.

34

Only used locally by Windows, never remotely.

43

Only used locally by Windows, never remotely.

46

Only used locally by Windows, never remotely.

52

Only used locally by Windows, never remotely.

53

Only used locally by Windows, never remotely.

54

Only used locally by Windows, never remotely.

55

Only used locally by Windows, never remotely.

<46> Section 3.1.4.2: Windows waits 30 seconds for the service to respond.

<47> Section 3.1.4.4: In Windows NT, Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2, after the database is locked, the server must not allow further client operations on the database until it is unlocked. In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server must ignore the database lock.

In Windows NT 3.51, Windows NT 4.0, Windows 2000, Windows 2000 Server, Windows Server 2003, Windows Server 2003 R2, and Windows XP, the server responds with the error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs if the database has been locked using RLockServiceDatabase (section 3.1.4.4).

In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server does not respond with error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs after the database is locked using RLockServiceDatabase (section 3.1.4.4).

<48> Section 3.1.4.4: In Windows NT, Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2, after the database is locked, the server must not allow further client operations on the database until it is unlocked. In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server must ignore the database lock.

In Windows NT 3.51, Windows NT 4.0, Windows 2000, Windows 2000 Server, Windows Server 2003, Windows Server 2003 R2, and Windows XP, the server responds with the error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs if the database has been locked using RLockServiceDatabase (section 3.1.4.4).

In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server does not respond with error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs after the database is locked using RLockServiceDatabase (section 3.1.4.4).

<49> Section 3.1.4.9: In Windows NT, Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2, after the database is locked, the server must not allow further client operations on the database until it is unlocked. In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server must ignore the database lock.

In Windows NT 3.51, Windows NT 4.0, Windows 2000, Windows 2000 Server, Windows Server 2003, Windows Server 2003 R2, and Windows XP, the server responds with the error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs if the database has been locked using RLockServiceDatabase (section 3.1.4.4).

In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server does not respond with error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs after the database is locked using RLockServiceDatabase (section 3.1.4.4).

<50> Section 3.1.4.11: Windows fails the request with ERROR_INVALID_PARAMETER (87) if the client tries to change the dwServiceType to SERVICE_FILE_SYSTEM_DRIVER or SERVICE_KERNEL_DRIVER.

<51> Section 3.1.4.15: Windows fails the request with ERROR_ACCESS_DENIED (5) if the client does not have sufficient access rights or for operations that do not match the granted access right.

<52> Section 3.1.4.19: In Windows NT, Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2, after the database is locked, the server must not allow further client operations on the database until it is unlocked. In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server must ignore the database lock.

In Windows NT 3.51, Windows NT 4.0, Windows 2000, Windows 2000 Server, Windows XP, Windows Server 2003, and Windows Server 2003 R2, the server responds with the error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs if the database has been locked using RLockServiceDatabase (section 3.1.4.4).

In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server does not respond with error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs after the database is locked using RLockServiceDatabase (section 3.1.4.4).

<53> Section 3.1.4.19: Windows waits 30 seconds for the service to respond.

<54> Section 3.1.4.19: In Windows NT, Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2, after the database is locked, the server must not allow further client operations on the database until it is unlocked. In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server must ignore the database lock.

In Windows NT 3.51, Windows NT 4.0, Windows 2000, Windows 2000 Server, Windows XP, Windows Server 2003, and Windows Server 2003 R2, the server responds with the error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs if the database has been locked using RLockServiceDatabase (section 3.1.4.4).

In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server does not respond with error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs after the database is locked using RLockServiceDatabase (section 3.1.4.4).

<55> Section 3.1.4.22: Windows fails the request with ERROR_INVALID_PARAMETER (87) if the client tries to change dwServiceType to SERVICE_FILE_SYSTEM_DRIVER or SERVICE_KERNEL_DRIVER.

<56> Section 3.1.4.26: Windows fails the request with ERROR_ACCESS_DENIED (5) if the client does not have sufficient access rights or for operations that do not match the granted access right.

<57> Section 3.1.4.30: In Windows NT, Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2, after the database is locked, the server must not allow further client operations on the database until it is unlocked. In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server must ignore the database lock.

In Windows NT 3.51, Windows NT 4.0, Windows 2000, Windows 2000 Server, Windows XP, Windows Server 2003, and Windows Server 2003 R2, the server responds with error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs if the database has been locked using RLockServiceDatabase (section 3.1.4.4).

In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server does not respond with error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs after the database is locked using RLockServiceDatabase (section 3.1.4.4).

<58> Section 3.1.4.30: Windows waits 30 seconds for the service to respond.

<59> Section 3.1.4.30: In Windows NT, Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2, after the database is locked, the server must not allow further client operations on the database until it is unlocked. In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server must ignore the database lock.

In Windows NT 3.51, Windows NT 4.0, Windows 2000, Windows 2000 Server, Windows XP, Windows Server 2003, and Windows Server 2003 R2, the server responds with the error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs if the database has been locked using RLockServiceDatabase (section 3.1.4.4).

In Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, the server does not respond with error code ERROR_SERVICE_DATABASE_LOCKED (1055) for RStartServiceA (section 3.1.4.30) and RStartServiceW (section 3.1.4.19)RPCs after the database is locked using RLockServiceDatabase (section 3.1.4.4).

<60> Section 3.1.4.31: If the lpDisplayName buffer is insufficient to hold the complete display name of the service, Windows fails the call and sets double of the size in chars of the display name excluding the terminating null character in lpcchBuffer.

<61> Section 3.1.4.32: If the lpKeyName buffer is insufficient to hold the complete service name of the service, Windows fails the call and sets double of the size in chars of the service name excluding the terminating null character in lpcchBuffer.

<62> Section 3.1.4.34: Windows returns ERROR_CALL_NOT_IMPLEMENTED (120) for Windows NT.

<63> Section 3.1.4.34: Windows 2000, Windows XP, Windows Server 2003, Windows Server 2003 R2, and Windows Vista return ERROR_INVALID_LEVEL if psti or pspn (see section 2.2.21) is specified in the Info parameter.

<64> Section 3.1.4.35: Windows returns ERROR_CALL_NOT_IMPLEMENTED (120) for Windows NT.

<65> Section 3.1.4.35: Windows 2000, Windows XP, Windows Server 2003, Windows Server 2003 R2, and Windows Vista return ERROR_INVALID_LEVEL if psti or pspn (section 2.2.21) is specified in the Info parameter.

<66> Section 3.1.4.36: Windows returns ERROR_CALL_NOT_IMPLEMENTED (120) for Windows NT.

<67> Section 3.1.4.36: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<68> Section 3.1.4.36: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<69> Section 3.1.4.36: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<70> Section 3.1.4.36: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<71> Section 3.1.4.36: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<72> Section 3.1.4.36: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<73> Section 3.1.4.36: Available in Windows 7 and Windows Server 2008 R2.

<74> Section 3.1.4.36: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<75> Section 3.1.4.36: Note When the server is passing an invalid value for these parameters, behavior can change based on the RPC runtime check. See RPC Runtime Check Notes (section 3.2).

<76> Section 3.1.4.37: Windows returns ERROR_CALL_NOT_IMPLEMENTED (120) for Windows NT.

<77> Section 3.1.4.37: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<78> Section 3.1.4.37: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<79> Section 3.1.4.37: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<80> Section 3.1.4.37: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<81> Section 3.1.4.37: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<82> Section 3.1.4.37: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<83> Section 3.1.4.37: Available in Windows 7 and Windows Server 2008 R2.

<84> Section 3.1.4.37: Windows returns ERROR_INVALID_PARAMETER (87) for Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2003 R2.

<85> Section 3.1.4.37: Note When the server is passing an invalid value for these parameters, behavior can change based on the RPC runtime check. See RPC Runtime Check Notes (section 3.2).

<86> Section 3.1.4.41: If the lpBinaryPathName has the "%windir%\System32" folder specified within the path, which is the 64-bit location on 64-bit Windows, Windows automatically replaces that folder with "%windir%\SysWow64", which is the 32-bit location on 64-bit Windows.

<87> Section 3.1.4.43: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<88> Section 3.1.4.44: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<89> Section 3.1.4.44: Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 clients use multiplexed RPC connections for RGetNotifyResults on request if the server supports them, and they fall back to non-multiplexed connections if the server doesn't support multiplexed connections.

<90> Section 3.1.4.45: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<91> Section 3.1.4.46: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<92> Section 3.1.4.46: Windows waits 30 seconds for the service to respond.

<93> Section 3.1.4.47: Available in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems.

<94> Section 3.1.4.47: Windows waits 30 seconds for the service to respond.

<95> Section 3.1.4.48: This method exists only in Windows 7.

<96> Section 6: Windows XP does not support [range] on strings.

 
Show:
© 2014 Microsoft