CopyPastor

Detecting plagiarism made easy.

Score: 1; Reported for: Exact paragraph match Open both answers

Possible Plagiarism

Reposted on 2020-07-16
by Bowman Zhu

Original Post

Original - Posted on 2019-11-25
by Bowman Zhu



            

            

                
            

        

        

            Present in both answers;
            Present only in the new answer;
            Present only in the old answer;
        

    

    

    

        

            

                

                    
                        The most common problem is Storage Emulator not start.
                        
                        

                        
                        Try typing 
                        
                        

                        
                            "%programfiles(x86)%\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe" status
                        
                        

                        
                        in cmd to check the status.
                        
                        

                        
                        If it returns false, enter the following command to start the Storage Emulator:
                        
                        

                        
                            "%programfiles(x86)%\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe" init
                        
                            "%programfiles(x86)%\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe" start
                        
                        

                        
                        Let me know whether this can solved your problem.:)
                        
                        

                        
                

            

            

                

                    
                        ***Update:***

Since you use a locally virtualized Storage Emulator, then your Connecting String is correct.

If your firewall restricts func from accessing the Storage Account, then this error may be reported. The firewall is one of the reasons that the listener cannot access the virtual Storage Emulator.

When running the function locally, all triggers except httptrigger need to use the Storage Emulator. If the firewall restricts the listener's access to virtual storage, problems can occur when performing functions. That's why you don't get errors with httptrigger, because it doesn't use a virtual Storage Emulator.

Try disabling the firewall and see if that resolves the issue.

**Of course, it is also possible that the Storage Emulator service is not open.** Try typing 

    "%programfiles(x86)%\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe" status

in cmd to check the status.

If it returns false, enter the following command to start the Storage Emulator:

    "%programfiles(x86)%\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe" init
    "%programfiles(x86)%\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe" start




***To sum up:***

This type of problem is generally for three reasons. 

1.Connection string error prevents connection, 

2.firewall is set

3.some services are not turned on.

Hope it helps.


----------


***Original Answer:***


Same code works fine on my side,


**Solution:**

Try to copying the same code to a different location.

Maybe [this][1] can help you.

  [1]: https://github.com/Azure/azure-functions-core-tools/issues/357
                        
                

            

        

    

    

        

        

            Present in both answers;
            Present only in the new answer;
            Present only in the old answer;
        

    



    











    

         Made by the SOBotics team.
            Published on StackApps.
            Source code on GitHub.
            Content provided by Stack Exchange API
            under the  CC BY-SA 3.0 license.