532462766 код ошибки - Не ошибается лишь тот, кто ничего не делает!

This is the line that gives me the error.

<Exec Command="&quot;$(MonoGameContentBuilderExe)&quot;
/@:&quot;%(ContentReferences.FullPath)&quot; $(Header)"
WorkingDirectory="%(ContentReferences.RootDir)%(ContentReferences.Directory)" />

It is from the MonoGame.Content.Builder.targets file.

The full error is:

The command «»C:Program Files
(x86)MSBuildMonoGamev3.0ToolsMGCB.exe»
/@:»C:UsersJakedocumentsvisual studio
2015ProjectsFirstGameFirstGameContentContent.mgcb»
/platform:Windows /outputDir:»C:UsersJakedocumentsvisual studio
2015ProjectsFirstGameFirstGameContentbinWindows»
/intermediateDir:»C:UsersJakedocumentsvisual studio
2015ProjectsFirstGameFirstGameContentobjWindows» /quiet» exited
with code -532462766.

I have been converting this game from Visual Studio 2010 to Visual Studio 2015, which is when this error started. Does anyone have any insight into what may be causing this?

Mohit S

13.6k5 gold badges33 silver badges68 bronze badges

asked Sep 29, 2015 at 4:16

It turned out that I was attempting to load in an image file made in gimp which has an unsupported file type. I just needed to export it as a png and it worked fine.

answered Sep 30, 2015 at 5:00

JakeJake

3271 gold badge3 silver badges15 bronze badges

In my case, the same error code was being thrown by the roslyn compiler when trying to compile cshtml files.

Turns out that the issue was being caused due to roslyn compiler version mismatch. Let me try and explain the problem:

My csproj had nuget references to roslyn compiler assemblies (Microsoft.Net.Compilers and Microsoft.CodeDom.Providers.DotNetCompilerPlatform).
I use git for source control
I had recently updated to the latest version of roslyn compiler on DEV branch
But my MASTER branch was still referencing the previous version of roslyn compiler and I was not yet ready to merge DEV to MASTER
Switching from dev to master branch from team explorer did not seem to trigger «nuget restore» for the mismatched packages

So manually deleting all the folders in the packages folder and performing a «nuget restore» resolved this error for me.

answered Apr 5, 2017 at 17:34

RaghuRaghu

1,40513 silver badges18 bronze badges

Источник

I am stumped, so I hope someone will have an idea of the fix for this. I have a small Exchange 2010 server setup — it was working for a week, then, it suddenly stopped working — I found out because users reported that their Exchange over HTTP settings suddenly
vanished. After not seeing anything amiss, I used Microsoft’s Remote Connectivity Analyzer and get the following result:

Testing Outlook connectivity.
The Outlook connectivity test failed.

Additional Details

Elapsed Time: 14457 ms.

Test Steps

Testing RPC over HTTP connectivity to server office.nextlevelaviation.net
RPC over HTTP connectivity failed.

Additional Details

HTTP Response Headers:
Content-Type: text/html
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM
X-Powered-By: ASP.NET
Date: Tue, 05 May 2015 01:41:47 GMT
Content-Length: 58

Elapsed Time: 14457 ms.

Test Steps

Attempting to resolve the host name office.nextlevelaviation.net in DNS.
The host name resolved successfully.

Additional Details

IP addresses returned: (IP address displayed)

Elapsed Time: 120 ms.

Testing TCP port 443 on host (domain.net) to ensure it’s listening and open.
The port was opened successfully.

Additional Details

Elapsed Time: 125 ms.

Testing the SSL certificate to make sure it’s valid.
The certificate passed all validation requirements.

Additional Details

Elapsed Time: 283 ms.

Test Steps

The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server (domain.net) on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.

Additional Details

Remote Certificate Subject: (Certificate info shown properly)

Elapsed Time: 190 ms.

Validating the certificate name.
The certificate name was validated successfully.

Additional Details

Host name (domain.net) was found in the Certificate Subject Common name.

Elapsed Time: 0 ms.

Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.

Test Steps

The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate (certificate info shown).
One or more certificate chains were constructed successfully.

Additional Details

A total of 2 chains were built. The highest quality chain ends in root certificate (Root cert info shown).

Elapsed Time: 32 ms.

Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.

Additional Details

The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the «Update Root Certificates» feature isn’t enabled.

Elapsed Time: 5 ms.

Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn’t expired.

Additional Details

The certificate is valid. (Correct dates shown)

Elapsed Time: 0 ms.

Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn’t detected.

Additional Details

Accept/Require Client Certificates isn’t configured.

Elapsed Time: 488 ms.

Testing HTTP Authentication Methods for URL URL https ://domain.net/rpc/rpcproxy.dll?server.domain.net:6002.
The HTTP authentication methods are correct.

Additional Details

The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Negotiate, NTLM
HTTP Response Headers:
Content-Type: text/html
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM
X-Powered-By: ASP.NET
Date: Tue, 05 May 2015 01:41:47 GMT
Content-Length: 58

Elapsed Time: 285 ms.

Attempting to ping RPC proxy domain.net.
RPC Proxy was pinged successfully.

Additional Details

Elapsed Time: 465 ms.

Attempting to ping the MAPI Mail Store endpoint with identity: (server.domain.net):6001.
The endpoint was pinged successfully.

Additional Details

The endpoint responded in 218 ms.

Elapsed Time: 3224 ms.

Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.

Additional Details

Elapsed Time: 2411 ms.

Test Steps

Attempting to ping the MAPI Address Book endpoint with identity: (server.domain.net):6004.
The endpoint was pinged successfully.

Additional Details

The endpoint responded in 578 ms.

Elapsed Time: 1596 ms.

Testing the address book «Check Name» operation for user user@domain.net against server server.domain.net.
Check Name succeeded.

Additional Details

DisplayName: (User’s AD information properly displayed)

Elapsed Time: 814 ms.

Testing the MAPI Referral service on the Exchange Server.
The Referral service was tested successfully.

Additional Details

Elapsed Time: 5589 ms.

Test Steps

Attempting to ping the MAPI Referral Service endpoint with identity: (server.domain.net):6002.
The endpoint was pinged successfully.

Additional Details

The endpoint responded in 890 ms.

Elapsed Time: 3893 ms.

Attempting to perform referral for user (user’s info shown) on server (server.domain.net).
The test passed with some warnings encountered. Please expand the additional details.
Tell me more about this issue and how to resolve it

Additional Details

The Referral service returned generic error 0x80004005. This may mean that encryption is required. The Microsoft Connectivity Analyzer is trying again with encryption.
RFR Status: 2147500037

Elapsed Time: 1399 ms.

Attempting to perform referral for user (user’s AD info shown) on server (server.domain.net).
We got the address book server successfully.

Additional Details

The server returned by the Referral service: (server.domain.net)

Elapsed Time: 296 ms.

Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.

Additional Details

Elapsed Time: 1049 ms.

Test Steps

Attempting to ping the MAPI Address Book endpoint with identity: (server.domain.net):6004.
The endpoint was pinged successfully.

Additional Details

The endpoint responded in 218 ms.

Elapsed Time: 224 ms.

Testing the address book «Check Name» operation for user user@domain.net against server server.domain.net.
Check Name succeeded.

Additional Details

DisplayName: User Full Name, LegDN: (User’s AD information is displayed properly)

Elapsed Time: 824 ms.

Testing the MAPI Mail Store endpoint on the Exchange server.
An error occurred while testing the Mail Store.

Additional Details

Elapsed Time: 413 ms.

Test Steps

Attempting to ping the MAPI Mail Store endpoint with identity: server.domain.net:6001.
The endpoint was pinged successfully.

Additional Details

The endpoint responded in 312 ms.

Elapsed Time: 305 ms.

Attempting to log on to the Mailbox.
An error occurred while logging on to the Mailbox.

Additional Details

An RPC error was thrown by the RPC Runtime process. Error -532462766 -532462766

Elapsed Time: 108 ms.

Any assistance is GREATLY appreciated!!

Источник

I recently added Azure Caching to my web role, and on redeploy the instance hang in the following status for about 30 minutes: Busy (Waiting for role to start… System startup tasks are running. [2013-01-25T17:12:53Z])

and then get System startup task failed with exit code -532462766, before the instances retry start up.

I have not found anything on this error code, and in dire need on more information.

Alex Blokha

1,1412 gold badges17 silver badges30 bronze badges

asked Jan 25, 2013 at 17:22

Problem resolved. I needed to set my Web Role storage credentials to use a real storage account instead of development storage. I also selected the check box on the Configurations tab to update the connection string for Diagnostics and Caching with Azure when publishing. Once this was corrected the re-deploy was successful.

answered Feb 4, 2013 at 14:01

Источник

       Fatal error in IL Linker
         Unhandled exception. Mono.Cecil.ResolutionException: Failed to resolve Microsoft.WindowsAzure.Storage.Blob.BlobListingDetails
            at Mono.Cecil.Mixin.CheckedResolve(TypeReference self)
            at Mono.Cecil.MetadataBuilder.GetConstantType(TypeReference constant_type, Object constant)
            at Mono.Cecil.MetadataBuilder.AddConstant(IConstantProvider owner, TypeReference type)
            at Mono.Cecil.MetadataBuilder.AddParameter(UInt16 sequence, ParameterDefinition parameter, ParamTable table)
            at Mono.Cecil.MetadataBuilder.AddParameters(MethodDefinition method)
            at Mono.Cecil.MetadataBuilder.AddMethod(MethodDefinition method)
            at Mono.Cecil.MetadataBuilder.AddMethods(TypeDefinition type)
            at Mono.Cecil.MetadataBuilder.AddType(TypeDefinition type)
            at Mono.Cecil.MetadataBuilder.AddTypes()
            at Mono.Cecil.MetadataBuilder.BuildTypes()
            at Mono.Cecil.MetadataBuilder.BuildModule()
            at Mono.Cecil.MetadataBuilder.BuildMetadata()
            at Mono.Cecil.ModuleWriter.<>c.<BuildMetadata>b__2_0(MetadataBuilder builder, MetadataReader _)
            at Mono.Cecil.ModuleDefinition.Read[TItem,TRet](TItem item, Func`3 read)
            at Mono.Cecil.ModuleWriter.BuildMetadata(ModuleDefinition module, MetadataBuilder metadata)
            at Mono.Cecil.ModuleWriter.Write(ModuleDefinition module, Disposable`1 stream, WriterParameters parameters)
            at Mono.Cecil.ModuleWriter.WriteModule(ModuleDefinition module, Disposable`1 stream, WriterParameters parameters)
            at Mono.Cecil.ModuleDefinition.Write(String fileName, WriterParameters parameters)
            at Mono.Linker.Steps.OutputStep.WriteAssembly(AssemblyDefinition assembly, String directory, WriterParameters writerParameters)
            at Mono.Linker.Steps.OutputStep.OutputAssembly(AssemblyDefinition assembly)
            at Mono.Linker.Steps.BaseStep.Process(LinkContext context)
            at Mono.Linker.Pipeline.ProcessStep(LinkContext context, IStep step)
            at Mono.Linker.Pipeline.Process(LinkContext context)
            at Mono.Linker.Driver.Run(ILogger customLogger)
            at Mono.Linker.Driver.Execute(String[] args, ILogger customLogger)
            at Mono.Linker.Driver.Main(String[] args)

Источник

Это строка, которая дает мне ошибку.

<Exec Command="&quot;$(MonoGameContentBuilderExe)&quot;
/@:&quot;%(ContentReferences.FullPath)&quot; $(Header)"
WorkingDirectory="%(ContentReferences.RootDir)%(ContentReferences.Directory)" />

Это из файла MonoGame.Content.Builder.targets.

Полная ошибка:

Команда «» C: Program Files (x86) MSBuild MonoGame v3.0 Tools MGCB.exe «/ @:» C: Users Jake documents visual studio 2015 Projects FirstGame FirstGame Content Content.mgcb «/ платформа: Windows / outputDir:» C: Users Jake documents visual studio 2015 Projects FirstGame FirstGame Content bin Windows «/ intermediateDir:» C: Users Jake Documents Visual Studio 2015 Projects FirstGame FirstGame Content obj Windows «/ quiet» завершился с кодом -532462766.

Я конвертировал эту игру из Visual Studio 2010 в Visual Studio 2015, когда и началась эта ошибка. Кто-нибудь знает, что может быть причиной этого?

2 ответа

Лучший ответ

Оказалось, что я пытался загрузить файл изображения, созданный в gimp, который имеет неподдерживаемый тип файла. Мне просто нужно было экспортировать его как png, и он работал нормально.

Jake
30 Сен 2015 в 05:00

В моем случае такой же код ошибки выдавался компилятором roslyn при попытке скомпилировать файлы cshtml.

Оказывается, проблема возникла из-за несоответствия версии компилятора roslyn. Позвольте мне попытаться объяснить проблему:

В моем csproj были ссылки nuget на сборки компилятора roslyn (Microsoft.Net.Compilers и Microsoft.CodeDom.Providers.DotNetCompilerPlatform).
Я использую git для управления версиями
Недавно я обновился до последней версии компилятора roslyn в ветке DEV
Но моя ветка MASTER все еще ссылалась на предыдущую версию компилятора roslyn, и я еще не был готов объединить DEV с MASTER
Переключение с dev на master ветку из team explorer, похоже, не запускало «восстановление nuget» для несоответствующих пакетов

Таким образом, удаление всех папок в папке пакетов вручную и выполнение «восстановления nuget» разрешили эту ошибку для меня.

Raghu
5 Апр 2017 в 17:34

Источник