![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
| |
| | #1 (permalink) |
| | WsatConfig and certificates I am trying to configure MSDTC to support the WS-Atomic Transaction specification using the tool WsatConfig.exe, as recommended in the following article: http://windowssdk.msdn.microsoft.com.../ms733943.aspx I'm not familiar enough to know, but it seems like an SSL certificate is required to even make it work. Does anybody know if this is the case? Anyhow, I have generated a temporary certificate and installed it as a trusted certificate on my machine - so all looks ok. Problem is, I cannot seem to get the format of the endpointCert parameter that is sent to WsatConfig.exe right. It should be in the following format: <machine|"Issuer\SubjectName">. My certificate has localhost as the issuer. I have tried: -endpointCert:machine -endpointCert:localhost -endpointCert:"localhost/SubjectName" (where SubjectName is what was generated when I generated the certificate) -endpointCert:<thumb ID> (where thumb ID is fetched by opening the certificate in the MMC console) And variations of this. If anybody could give me an example of how to format the endpointCert parameter, I would be very grateful. My transaction enabled web services are crashing with aborted transactions, and my guess is that this might be the cause. For testing purposes, I have manually modified the registry, adding the key HKLM\Software\Microsoft\MSDTC\TransactionBridge, just to enable the WS-AT support in MSDTC, but it seems like this is not enough. |
My System Specs![]() |
| | #2 (permalink) |
| | Re: WsatConfig and certificates I partly solved the problem by manually enabling WS-AT via the registry. I did this before as well, but it didn't seem to work. Now, for some reason, it does work. (maybe after a reboot?) Cheers / Mikael mikael.rydstrom@gmail.com wrote: > I am trying to configure MSDTC to support the WS-Atomic Transaction > specification using the tool WsatConfig.exe, as recommended in the > following article: > > http://windowssdk.msdn.microsoft.com.../ms733943.aspx > > I'm not familiar enough to know, but it seems like an SSL certificate > is required to even make it work. Does anybody know if this is the > case? Anyhow, I have generated a temporary certificate and installed it > as a trusted certificate on my machine - so all looks ok. Problem is, I > cannot seem to get the format of the endpointCert parameter that is > sent to WsatConfig.exe right. It should be in the following format: > <machine|"Issuer\SubjectName">. My certificate has localhost as the > issuer. I have tried: > > -endpointCert:machine > -endpointCert:localhost > -endpointCert:"localhost/SubjectName" (where SubjectName is what was > generated when I generated the certificate) > -endpointCert:<thumb ID> (where thumb ID is fetched by opening the > certificate in the MMC console) > > And variations of this. If anybody could give me an example of how to > format the endpointCert parameter, I would be very grateful. > > My transaction enabled web services are crashing with aborted > transactions, and my guess is that this might be the cause. For testing > purposes, I have manually modified the registry, adding the key > HKLM\Software\Microsoft\MSDTC\TransactionBridge, just to enable the > WS-AT support in MSDTC, but it seems like this is not enough. |
My System Specs![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Certificates Won't appear | Vista General | |||
| Certificates | Vista General | |||
| SSL Certificates | Vista security | |||
| SSL Certificates | Vista General | |||